Two simple questions

Two simple questions

[Tero Niemela]

Hi, I'd like to ask two questions that should be easy
to answer although with google I could not find
anything.

0) I'm seeing dirs like /bin /bin/ and even /bin// in
my PATH. What would be the best way to clean up the
trailing slashes? "typeset -U path" won't clean up
paths if they have different number of trailing
slashes (I mean all those mentioned paths are left but
other instances of, e.g., /bin are of course cleaned).

1) I use cygwin+zsh and it works great. I have in my
windows explorer "Command prompt here" option that
starts cmd.exe in the selected directory (with
"cmd.exe /k 'cd %1'" or something). How could I define
a command in command line that gets executed after all
zsh configuration files? zsh && cd /some/path of
course doesn't work.

Thanks for your help.


		
_______________________________
Do you Yahoo!?
Shop for Back-to-School deals on Yahoo! Shopping.
http://shopping.yahoo.com/backtoschool

Re: Two simple questions

[Björn Lindström]

Tero Niemela <tero_niemela@yahoo.com> writes:

> I'm seeing dirs like /bin /bin/ and even /bin// in my PATH. What would
> be the best way to clean up the trailing slashes? "typeset -U path"
> won't clean up paths if they have different number of trailing slashes
> (I mean all those mentioned paths are left but other instances of,
> e.g., /bin are of course cleaned).

AFAIK, zsh never adds stuff to the path by itself with a trailing path -
so just stopping to do that yourself in your own config files, should
do the trick.

If this doesn't help you, you'll just have to write your own function
that normalises the paths - stripping the trailing slashes should be
easy enough - typeset wont do that for you.

Re: Two simple questions

[DervishD]

    Hi Tero :)

 * Tero Niemela <tero_niemela@yahoo.com> dixit:
> 0) I'm seeing dirs like /bin /bin/ and even /bin// in
> my PATH. What would be the best way to clean up the
> trailing slashes? "typeset -U path" won't clean up
> paths if they have different number of trailing
> slashes (I mean all those mentioned paths are left but
> other instances of, e.g., /bin are of course cleaned).

    'typeset -U' just 'uniqize', it doesn't normalize. You're looking
for something like (EXTENDED_GLOB must be set, for the '#'):

    path=(${(qq)${path//\/##/\/}%/})

    This converts multiple slashes to just one, and then removes the
last one. The '(qq)' part is needed just in case 'path' has elements
with spaces in it.

> 1) I use cygwin+zsh and it works great. I have in my
> windows explorer "Command prompt here" option that
> starts cmd.exe in the selected directory (with
> "cmd.exe /k 'cd %1'" or something). How could I define
> a command in command line that gets executed after all
> zsh configuration files? zsh && cd /some/path of
> course doesn't work.

    Just add that command at the end of the last config file read. If
the shell is interactive, try /etc/zshrc (well, I don't know which
name it has under cygwin, sorry).

    Hope that helps :)

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/

Re: Two simple questions

[Tero Niemela]

Hi!

> > 0) I'm seeing dirs like /bin /bin/ and even /bin//
> in
> > my PATH.
> 
> You're looking
> for something like (EXTENDED_GLOB must be set, for
> the '#'):
> 
>     path=(${(qq)${path//\/##/\/}%/})
> 
>     This converts multiple slashes to just one, and
> then removes the
> last one. The '(qq)' part is needed just in case
> 'path' has elements with spaces in it.

In some cases (Cygwin) it indeed does have spaces.
However, your solution seems not to be optiomal:

~> export PATH=/bin:/usr/bin:/bin//:/bin/
~> which ls                              
/bin/ls
~> path=(${(qq)${path//\/##/\/}%/})
~> echo $PATH
'/bin':'/usr/bin':'/bin/'
~> which ls
ls not found
zsh: exit 1
~> 

> > 1) I use cygwin+zsh and it works great. I have in
> my
> > windows explorer "Command prompt here" option that
> > starts cmd.exe in the selected directory (with
> > "cmd.exe /k 'cd %1'" or something). How could I
> define
> > a command in command line that gets executed after
> all
> > zsh configuration files? zsh && cd /some/path of
> > course doesn't work.
> 
>     Just add that command at the end of the last
> config file read.

I did the following, works perfectly for me:

Last line of ~/.zlogin is:

[[ "$OSTYPE" = *cygwin* && $ARGC -eq 1 ]] && cd "$@"

And this registry settings was added to Windows
registry:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Folder\shell\command]
@="Cygwin Here"

[HKEY_CLASSES_ROOT\Folder\shell\command\command]
@="\"C:\\cygwin\\bin\\zsh.exe\" -l -s \"%1\""

Thanks!


		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail 

Re: Two simple questions

[DervishD]

    Hi Tero :)

 * Tero Niemela <tero_niemela@yahoo.com> dixit:
> > > 0) I'm seeing dirs like /bin /bin/ and even /bin//
> > in
> > > my PATH.
> > You're looking
> > for something like (EXTENDED_GLOB must be set, for
> > the '#'):
> >     path=(${(qq)${path//\/##/\/}%/})
> > 
> >     This converts multiple slashes to just one, and
> > then removes the
> > last one. The '(qq)' part is needed just in case
> > 'path' has elements with spaces in it.
> In some cases (Cygwin) it indeed does have spaces.
> However, your solution seems not to be optiomal:
> ~> export PATH=/bin:/usr/bin:/bin//:/bin/
> ~> which ls                              
> /bin/ls
> ~> path=(${(qq)${path//\/##/\/}%/})
> ~> echo $PATH
> '/bin':'/usr/bin':'/bin/'
> ~> which ls
> ls not found
> zsh: exit 1
> ~> 

    The slash removing works here. It seems you don't have
'EXTENDED_GLOB' set. You must in order the recipe to work ;)

    And yes, the quoting completely screws the functioning of the
PATH, and the worst thing is that... it is not needed O:) Array
elements are separate words, so you just need to do this:

    setopt EXTENDED_GLOB
    path=(${${path//\/##/\/}%/})
    unsetopt EXTENDED_GLOB

    The setopt is only needed, obviously, if you don't have
EXTENDED_GLOB set, which you don't seem to have.

    Hope this helps :) At least it works for me with your example
above (and adding a directory with spaces in it.

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/

Re: Two simple questions

[Tero Niemela]

Hi!

> so you just need to do this:
> 
>     setopt EXTENDED_GLOB
>     path=(${${path//\/##/\/}%/})
>     unsetopt EXTENDED_GLOB

Thanks! This works all ok here, too. For reference, my
ultimate path cleaning now contains:

# Clean up paths 
path=($^path(N))
manpath=($^manpath(N)) 
setopt EXTENDED_GLOB
path=(${${path//\/##/\/}%/})
manpath=(${${manpath//\/##/\/}%/})
unsetopt EXTENDED_GLOB  
typeset -U path manpath



		
__________________________________
Do you Yahoo!?
Y! Messenger - Communicate in real time. Download now. 
http://messenger.yahoo.com

Re: Two simple questions

[DervishD]

    Hi Tero :)

> Thanks! This works all ok here, too. For reference, my
> ultimate path cleaning now contains:
> 
> # Clean up paths 
> path=($^path(N))
> manpath=($^manpath(N)) 

    I don't get that two. The 'N' sets nullglob for that expansion,
right but, why the '^'? AFAIK that only turns on 'RC_EXPAND_PARAM'
for that expansion :? I'm curious :)

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/

Re: Two simple questions

[Tero Niemela]

Hi!

> > # Clean up paths 
> > path=($^path(N))
> > manpath=($^manpath(N)) 
> 
>     I don't get that two. The 'N' sets nullglob for
> that expansion,
> right but, why the '^'? AFAIK that only turns on
> 'RC_EXPAND_PARAM'
> for that expansion :? I'm curious :)

Those removes non-existing dirs from paths. It was
suggested on this list just a couple of months ago.
See for the explanation at:

http://www.zsh.org/mla/users/2004/msg00608.html


		
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com

Re: Two simple questions

[DervishD]

    Hi Tero :)

 * Tero Niemela <tero_niemela@yahoo.com> dixit:
> > > # Clean up paths 
> > > path=($^path(N))
> > > manpath=($^manpath(N)) 
> >     I don't get that two. The 'N' sets nullglob for
> > that expansion,
> > right but, why the '^'? AFAIK that only turns on
> > 'RC_EXPAND_PARAM'
> > for that expansion :? I'm curious :)
> Those removes non-existing dirs from paths. It was
> suggested on this list just a couple of months ago.

    Very clever! :) The '^' makes the '(N)' glob qualifier to be
added to each element of the array :)) Thanks a lot for the
explanation, is a very clever way of removing non-existent dirs from
a list (well, an array in this case).

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/

Re: Two simple questions

[Stephane Chazelas]

On Wed, Sep 15, 2004 at 10:36:56AM +0200, DervishD wrote:
[...]
> > > > path=($^path(N))
> > > > manpath=($^manpath(N)) 
[...]
>     Very clever! :) The '^' makes the '(N)' glob qualifier to be
> added to each element of the array :)) Thanks a lot for the
> explanation, is a very clever way of removing non-existent dirs from
> a list (well, an array in this case).
[...]

All the given solutions seem to forget about one thing about
$PATH. An empty element in it means "current directory".

$path instead of "$path[@]" removes the empty components in it.
That doesn't apply to $^path, though, but to the other
solutions.

$ echo $PATH
/usr/xpg4/bin:/usr/bin:/usr/local/bin:
$ print -rl $path
/usr/xpg4/bin
/usr/bin
/usr/local/bin
$ print -rl "$path[@]"
/usr/xpg4/bin
/usr/bin
/usr/local/bin

$ print -rl ${^path}(N)
/usr/xpg4/bin
/usr/bin
/usr/local/bin
$ 

You can change "" to "." with ${path/(#s)(#e)/.}
but that's slightly different.

$ PATH=/::/bin://bin/
$ print -rl ${(u)${${path/(#s)(#e)/.}//\/##/\/}/(#b)(?)\/(#e)/$match}
/
.
/bin
$ 

(note that ${path/%\//} changes "/" into "".

-- 
Stephane