summaryrefslogtreecommitdiff
path: root/tmk_core
diff options
context:
space:
mode:
authorSergey Vlasov <sigprof@gmail.com>2020-06-11 14:26:10 +0300
committerGitHub <noreply@github.com>2020-06-11 12:26:10 +0100
commit0cb4da2c74f126016c8a0597341db441ef16265a (patch)
treed98ffc061093f1bad094190e56e5a0445dd7ba6b /tmk_core
parent9b0c7347333967df1e3e3611c0ef85c57f7f0ad7 (diff)
Really fix Ubuntu/Debian setup when $PATH contains spaces (#9370)
PR #9307 fixed the immediately visible problem (the command that was added to $HOME/.bashrc was incorrect because of missing quotes around paths with spaces). However, the modified command is still wrong - it captures the value of $PATH at the setup time, and the resulting command written out to $HOME/.bashrc will overwrite $PATH with that captured value, ignoring any changes in the environment. This may be especially important for WSL, where the initial value of $PATH in Linux includes everything which has been added to %PATH% on the Windows side; after adding that command to $HOME/.bashrc the WSL environment will no longer pick up any changes made by newly installed Windows software. Instead of that, use single quotes around the command, so that the environment variables are not expanded at the setup time, and the command that is added to $HOME/.bashrc becomes exactly this: PATH="$HOME/.local/bin:$PATH" This command will use the $HOME and $PATH environment variable values at the time the command is executed, not at the time the QMK setup is performed, so any further updates to $PATH are taken into account. Double quotes also ensure that the command is safe even if the values of those environment variables contain spaces.
Diffstat (limited to 'tmk_core')
0 files changed, 0 insertions, 0 deletions