Subject: Re: 24.4; Eshell eshell/which uses eshell-path-env but error with (getenv "PATH"), and these 2 sometimes get out of sync (not remote directory)

From: Jim Porter <[email-masked]>
Date: Mon, 17 Oct 2022 18:54:32 -0700

On 3/5/2015 1:30 AM, Hua Wei wrote:
> 
> 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")

I've fixed this in fd4992d356a9c4225cb518a6a5309aaa1d0f640b over in 
bug#57556. Closing.