Commit bffed36
fix: always prepend separator when appending noConfigScripts to PATH
EnvironmentVariableCollection.append() performs a literal string concatenation
and does not insert a path separator. The previous heuristic checked
process.env.PATH on the extension host and skipped the separator when that PATH
already ended with one. However, the PATH used by the integrated terminal can
differ from the extension host's PATH, so this check could incorrectly drop the
separator and glue the noConfigScripts directory onto the last entry of the
user's PATH (e.g. C:\Program Files\jreleaser\c:\Users\...\noConfigScripts).
Always prepend the separator. A trailing empty PATH entry (if the user's PATH
already ended with one) is harmless on both Windows and POSIX shells.
Fixes #1637
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>1 parent 0db5f15 commit bffed36
1 file changed
Lines changed: 6 additions & 6 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
93 | 93 | | |
94 | 94 | | |
95 | 95 | | |
96 | | - | |
97 | | - | |
98 | | - | |
99 | | - | |
100 | | - | |
101 | | - | |
| 96 | + | |
| 97 | + | |
| 98 | + | |
| 99 | + | |
| 100 | + | |
| 101 | + | |
102 | 102 | | |
103 | 103 | | |
104 | 104 | | |
| |||
0 commit comments