From: Paul Lew <paullew@cisco.com>
To: Peter Stephenson <pws@csr.com>
Cc: zsh-users@sunsite.dk
Subject: Re: How to clean up path most efficiently?
Date: Thu, 17 Jun 2004 10:21:03 -0700 [thread overview]
Message-ID: <16593.54015.756728.550098@cns-build4.cisco.com> (raw)
In-Reply-To: <200406171634.i5HGYAmE011684@news01.csr.com>
>>>>> "Peter" == Peter Stephenson <pws@csr.com> writes:
>> I have tons of directories in my $PATH, but only a handful of
>> them are needed in each my machine; other directories simply do
>> not exist. How could I clean up the non-existing dirs from my
>> $PATH most efficiently? Doing a for loop in ~/.zshrc just for
>> that sounds a bit overkill, but at least I couldn't spot
>> anything like this on man page.
Peter> It should be as simple as:
Peter> path=($^path(N))
This is cool. Few questions for efficiency here:
(1) which one is more efficient? The parameter expansion with
NULL_GLOB or read in the ready list from disk? Originally I setup
the path with a loop that will check for [[ -d $dir ]] but the
speed is greatly improved with the cached file. Since most
of the dir in our path are auto mounted, caching seems the
better way.
(2) when is zsh rehash the path? vared path? path=(...) ? If
path is rehased everytime path is updated, then will it be
bad practice to do:
PATH=a:b:c
PATH=$PATH:d:e
PATH=$PATH:f:g
This is to make the script fit on terminal width but will it
be costly?
TIA.
next prev parent reply other threads:[~2004-06-17 17:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 16:11 Jarkko Maja
2004-06-17 16:34 ` Peter Stephenson
2004-06-17 17:21 ` Paul Lew [this message]
2004-06-22 19:46 ` Timothy Luoma
2004-06-23 2:23 ` Sami Samhuri
2004-06-23 7:09 ` Bart Schaefer
2004-06-23 8:56 ` Peter Stephenson
2004-06-23 16:55 ` Sami Samhuri
2004-06-17 16:50 ` Paul Lew
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16593.54015.756728.550098@cns-build4.cisco.com \
--to=paullew@cisco.com \
--cc=pws@csr.com \
--cc=zsh-users@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).