diff options
| author | neon4272 <50256318+neon4272@users.noreply.github.com> | 2020-06-11 08:46:13 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-06-10 23:46:13 +0100 |
| commit | 97ddc7ea18fc5438b18b86caa742642eca2224fb (patch) | |
| tree | 51487b5c668d4c9bb74a18f1470fbb5ea0b9cd6a | |
| parent | 3afd2d81b8e48378dbb468a35bd6f06bd442a6f9 (diff) | |
| download | qmk_firmware-97ddc7ea18fc5438b18b86caa742642eca2224fb.tar.gz qmk_firmware-97ddc7ea18fc5438b18b86caa742642eca2224fb.zip | |
Fix Ubuntu/Debian setup when $PATH contains spaces (#9307)
* Change `echo` to `export`
* Add `export` as a note under the `echo` command
* Remove note from last commit
Co-authored-by: Ryan <fauxpark@gmail.com>
* Update docs/newbs_getting_started.md
Co-authored-by: Ryan <fauxpark@gmail.com>
* Update docs/newbs_getting_started.md
Add 1 line of whitespace under note
Co-authored-by: Ryan <fauxpark@gmail.com>
Co-authored-by: Ryan <fauxpark@gmail.com>
| -rw-r--r-- | docs/newbs_getting_started.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/newbs_getting_started.md b/docs/newbs_getting_started.md index 1367d1b409..e374a8f8e5 100644 --- a/docs/newbs_getting_started.md +++ b/docs/newbs_getting_started.md @@ -97,7 +97,7 @@ In most situations you will want to answer Yes to all of the prompts. 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). -Luckily, the fix is easy. Run this as your user: `echo "PATH=$HOME/.local/bin:$PATH" >> $HOME/.bashrc && source $HOME/.bashrc` +Luckily, the fix is easy. Run this as your user: `echo "PATH=$HOME/.local/bin:\"$PATH\"" >> $HOME/.bashrc && source $HOME/.bashrc` ?>**Note on FreeBSD**: It is suggested to run `qmk setup` as a non-`root` user to start with, but this will likely identify packages that need to be installed to your |