New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
20220327 Home Assistant documentation #528
20220327 Home Assistant documentation #528
Conversation
Repairs broken internal hyperlinks by restoring internal anchors. Restored anchors converted to null-anchor form. Fixes some spacing and alignment errors (apparent in MacDown authoring tool). Prefers multi-line command syntax over `&&` form which can be confusing to new users (quasi standard followed in other IOTstack documentation). Prefers `$ ` prompt form for commands users should execute. This is another quasi-standard. Explicitly sets `cd ~/IOTstack` where its omission might produce unexpected results. Adds code-fence rendering hints where appropriate. Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>
…tack Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>
Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>
Not strictly part of your changes, but wouldn't this be better if changed to "sudo hciconfig" (and of course to use the console highlighter):
|
Can't really say. I didn't write that bit. Something about Bluetooth, isn't it? History has it added by Tzaphkiel. |
I'm suggesting this change as I can make it a new pull-request, or could you just add the change here to your pull-request? Both are fine to me, just feels like it would better fit here as part of all the other changes. (And also change |
No, I'll do it. I suppose the point I was trying to make (in my own incredibly clumsy manner) was that I didn't actually understand what that documentation snippet was trying to communicate and, as a rule, I'm not a fan of jumping in and rewriting stuff I don't understand. I should've said that rather than leaving it implied in the "I didn't write it". My bad. After a bit more digging, it (root) turns out not to be necessary. The issue being addressed is if
and looking for the "UP". It's probably a bit back-to-front. I'll rewrite it as check then, if necessary: fix, reboot, recheck. Funny thing, though, I've never yet found a single use for the Bluetooth interface on any Pi. What about you? |
Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>
Done. |
Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>
Repairs broken internal hyperlinks by restoring internal anchors.
Restored anchors converted to null-anchor form.
Fixes some spacing and alignment errors (apparent in MacDown authoring
tool).
Prefers multi-line command syntax over
&&
form which can be confusingto new users (quasi standard followed in other IOTstack documentation).
Prefers
$
prompt form for commands users should execute. This isanother quasi-standard.
Explicitly sets
cd ~/IOTstack
where its omission might produceunexpected results.
Adds code-fence rendering hints where appropriate.
Signed-off-by: Phill Kelley 34226495+Paraphraser@users.noreply.github.com