PATH handling broken in zsh 3.1.4

PATH handling broken in zsh 3.1.4

[C. v. Stuckrad]

Hi!

I just noticed, that zsh *ignores* empty fields in
'path' (created via 'PATH') instead of implying a 'dot'.

'csh' does: setenv PATH bla:
            echo $path
            bla .

'zsh' ignores the trailing colon, and even drops colons when using
'vared PATH' on a Path containig empty fields. Like:
'export PATH=bla::bla'; vared path
bla  bla
   ^^         there _was_ the 'implied dot' :-)

Your's   Stucki


Christoph von Stuckrad       * *  | talk to  | <stucki@math.fu-berlin.de> \
Freie Universitaet Berlin    |/_* | nickname | ...!unido!fub!leibniz!stucki|
Fachbereich Mathematik, EDV  |\ * | 'stucki' | Tel:+49 30 838-75459        |
Arnimallee 2-6/14195 Berlin  * *  |  on IRC  | Fax:+49 30 838-75454       /

Re: PATH handling broken in zsh 3.1.4

[Zefram]

C. v. Stuckrad wrote:
>I just noticed, that zsh *ignores* empty fields in
>'path' (created via 'PATH') instead of implying a 'dot'.

No it doesn't.  It treats the entries as meaning the current directory.

>'csh' does: setenv PATH bla:
>            echo $path
>            bla .

zsh doesn't actually translate "" -> "." when setting the path, however.

>'zsh' ignores the trailing colon, and even drops colons when using
>'vared PATH' on a Path containig empty fields. Like:
>'export PATH=bla::bla'; vared path

vared on an array variable is a lossy process.  Try "vared PATH" instead.

-zefram

Re: PATH handling broken in zsh 3.1.4

[Stucki]

Quoting Zefram (zefram@tao.co.uk):
> >'zsh' ignores the trailing colon, and even drops colons when using
> >'vared PATH' on a Path containig empty fields. Like:
> >'export PATH=bla::bla'; vared path
> 
> vared on an array variable is a lossy process.  Try "vared PATH" instead.

OK, that works as supposed, but the 'csh'(ells) do 'really' imply
(meaning create) the dot, so you can work with it!
Shouldn't 'zsh' do the same in 'path' then ? I'd prefer to have
the same behavior!

Stucki

-- 
Christoph von Stuckrad       * *  | talk to  | <stucki@math.fu-berlin.de> \
Freie Universitaet Berlin    |/_* | nickname | ...!unido!fub!leibniz!stucki|
Fachbereich Mathematik, EDV  |\ * | 'stucki' | Tel:+49 30 838-75459        |
Arnimallee 2-6/14195 Berlin  * *  |  on IRC  | Fax:+49 30 838-75454       /

Re: PATH handling broken in zsh 3.1.4

[Zefram]

Stucki wrote:
>OK, that works as supposed, but the 'csh'(ells) do 'really' imply
>(meaning create) the dot, so you can work with it!
>Shouldn't 'zsh' do the same in 'path' then ? I'd prefer to have
>the same behavior!

I'd rather have zsh leave $path exactly as it was set.  POSIX, of course,
requires that $PATH remain exactly as it was set, as is historical
practice.  I'd rather remain compatible with the Bourne shell in this
respect, too.

-zefram