M-x eshell
switch to other buffer
use (setenv "PATH" "some path") to set new PATH env var
enter eshell with C-u 2 eshell (there is already one eshell buffer running)
a new eshell buffer opens
type command "which <new cmd under new path>"
output "not found in 'path'" (in this message, the 'path' is from (getenv
"PATH"))
this is confusing, because the function uses 'eshell-path-env' for search and use
(getenv "PATH") for error messaging
the bug:
eshell-path-env gets out of sync with (getenv "PATH")