On 6/4/15 1:51 PM, Stephen Dowdy wrote:
> $ PATH=/usr/sbin:/sbin:/usr/bin:/bin command -p env | grep ^PATH
> PATH=/bin:/usr/bin
> $ env | grep ^PATH
>
> PATH=/usr/sbin:/sbin:/opt/bin:/opt/sbin:/usr/local/jdk:/home/sdowdy/bin:/sbin:/usr/sbin:/usr/local/sbin:/usr/local/bin:/bin:/usr/
Chet,
Ha, yeah, i just repeated the bug you mention where PATH=... command -p ...
leaves the PATH set that way in the caller context. (oops!). Actually, in
case it's relevant, i found a strange side-effect of that bug when a
pipeline is involved (forgive my normal chaotic PATH)
$ env | grep
> Thanks for the response! It's always fun trying to figure out what POSIX
> means. I'm sure there's people who probably rely on the consequences of an
> altered PATH, too, so i don't expect you can make anyone happy whatever
> happens here. (I would guess that a "reasonable" compromise might be
