From: Paul Lew <paullew@cisco.com>
To: Jarkko Maja <jarkko1982@yahoo.com>
Cc: zsh-users@sunsite.dk
Subject: RE: How to clean up path most efficiently?
Date: Thu, 17 Jun 2004 09:50:11 -0700 [thread overview]
Message-ID: <16593.52163.379761.15160@cns-build4.cisco.com> (raw)
In-Reply-To: <20040617161149.80189.qmail@web60310.mail.yahoo.com>
>>>>> "Jarkko" == Jarkko Maja <jarkko1982@yahoo.com> writes:
Jarkko> Hi, I have tons of directories in my $PATH, but only a
Jarkko> handful of them are needed in each my machine; other
Jarkko> directories simply do not exist. How could I clean up the
Jarkko> non-existing dirs from my $PATH most efficiently? Doing a
Jarkko> for loop in ~/.zshrc just for that sounds a bit overkill,
Jarkko> but at least I couldn't spot anything like this on man
Jarkko> page.
This is what I do:
* put all paths together in one list
* walk thru the list and check the existence of each directory and
create a path consists of only the working one
* save this in a host specific file, e.g., zpath.$(hostname)
* upon zsh startup, if .zshenv is newer than this cached file, then
run thru the loop creating the list again. If the cache is newer,
just source it to setup the path.
This works pretty good except if I update the .zshrc first, then login
to update the cache, later I create the missing directory. In this
case, the cache is newer than the .zshenv so it will be used without
recognizing that the directory is updated. I will have to manually
removed the cache file and exec zsh again. Of course, this is because
I dont want the burden of access the filesystem with every login.
Dont know if anyone has better method.
prev parent reply other threads:[~2004-06-17 17:21 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
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 [this message]
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.52163.379761.15160@cns-build4.cisco.com \
--to=paullew@cisco.com \
--cc=jarkko1982@yahoo.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).