summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorQMK Bot <hello@qmk.fm>2022-03-03 09:54:22 +0000
committerQMK Bot <hello@qmk.fm>2022-03-03 09:54:22 +0000
commit9f95844cad8215f5cc5a90844e4b99fb1518286f (patch)
tree442cf42226335a8b8ac92eda0f55a61f625755ff
parentd75ce4862b4fac0605a3757c8e03be8278219cd3 (diff)
parent96b6ddf4bf79f22f850504d205a57e2730578b3b (diff)
downloadqmk_firmware-9f95844cad8215f5cc5a90844e4b99fb1518286f.tar.gz
qmk_firmware-9f95844cad8215f5cc5a90844e4b99fb1518286f.zip
Merge remote-tracking branch 'origin/master' into develop
-rw-r--r--docs/newbs_getting_started.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/newbs_getting_started.md b/docs/newbs_getting_started.md
index d6c080173c..c03e6acdb4 100644
--- a/docs/newbs_getting_started.md
+++ b/docs/newbs_getting_started.md
@@ -145,7 +145,7 @@ In most situations you will want to answer `y` to all of the prompts.
?>**Note on Debian, Ubuntu and their derivatives**:
It's possible, that you will get an error saying something like: `bash: qmk: command not found`.
This is due to a [bug](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839155) Debian introduced with their Bash 4.4 release, which removed `$HOME/.local/bin` from the PATH. This bug was later fixed on Debian and Ubuntu.
-Sadly, Ubuntu reitroduced this bug and is [yet to fix it](https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1588562).
+Sadly, Ubuntu reintroduced this bug and is [yet to fix it](https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1588562).
Luckily, the fix is easy. Run this as your user: `echo 'PATH="$HOME/.local/bin:$PATH"' >> $HOME/.bashrc && source $HOME/.bashrc`
### ** FreeBSD **