[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: env -u behavior
From: |
Andreas Schwab |
Subject: |
Re: env -u behavior |
Date: |
Sat, 24 Oct 2009 17:40:46 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) |
Eric Blake <address@hidden> writes:
> $ echo 'echo one' > ./c=d
> $ echo 'echo two' > ./--
[...]
> $ env a=b -- c=d echo three
> one
>
> Huh? ./-- is not on my PATH, why was it executed?
This executed c=d.
>
> $ PATH=:$PATH env a=b -- c=d echo three
> two
>
> Huh? This should have executed ./--, not ./c=d.
This executed --.
I'm getting "env: --: No such file or directory" in the first case and
in the second case "/bin/sh -- c=d echo three" is executed, which
executes c=d eventually.
Andreas.
--
Andreas Schwab, address@hidden
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
- env -u behavior, Eric Blake, 2009/10/23
- Re: env -u behavior, Mike Frysinger, 2009/10/24
- Re: env -u behavior, Eric Blake, 2009/10/24
- Re: env -u behavior, Mike Frysinger, 2009/10/25
- Re: env -u behavior, Eric Blake, 2009/10/26
- Re: env -u behavior, Mike Frysinger, 2009/10/26
- Re: env -u behavior, Eric Blake, 2009/10/26
- Re: env -u behavior, Jim Meyering, 2009/10/26