'serviceman' is not recognized as an internal or external command,
operable program or batch file.
Windows 10 v1903.
What I did:
```
mkdir %userprofile%\bin
move serviceman.exe %userprofile%\bin\serviceman.exe
reg add HKEY_CURRENT_USER\Environment /v PATH /d "%PATH%;%userprofile%\bin"
```
Opened new command prompt, ran `serviceman`, got:
```
'serviceman' is not recognized as an internal or external command,
operable program or batch file.
```
reg updates the registry, it DOES NOT update the PATH in the current environment.
Getting Windows to re-read the PATH from the registry into the environment requires a restart, or a program to issue a special low-level syscall function that causes PATH to be re-read.
P.S. The built-in setx command will cause PATH to be re-read, but it has a long-standing bug that causes the PATH to be set in the wrong place, and potentially truncated... welcome to Windows :)
I should update the README.
`reg` updates the registry, it DOES NOT update the `PATH` in the current environment.
Getting Windows to re-read the PATH from the registry into the environment requires a restart, or a program to issue a special low-level `syscall` function that causes `PATH` to be re-read.
And that is why I created `pathman`, which does use that low-level syscall:
https://git.rootprojects.org/root/pathman
P.S. The built-in `setx` command will cause PATH to be re-read, but it has a long-standing bug that causes the PATH to be set in the wrong place, and potentially truncated... welcome to Windows :)
Windows 10 v1903.
What I did:
Opened new command prompt, ran
serviceman, got:I should update the README.
regupdates the registry, it DOES NOT update thePATHin the current environment.Getting Windows to re-read the PATH from the registry into the environment requires a restart, or a program to issue a special low-level
syscallfunction that causesPATHto be re-read.And that is why I created
pathman, which does use that low-level syscall:https://git.rootprojects.org/root/pathman
P.S. The built-in
setxcommand will cause PATH to be re-read, but it has a long-standing bug that causes the PATH to be set in the wrong place, and potentially truncated... welcome to Windows :)Ok. Yeah. Windows is weird :)