From: znx <znxster@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] bash wizardry needed: PATH and MANPATH grow and grow and grow
Date: Sat, 3 Jun 2006 22:11:29 +0100 [thread overview]
Message-ID: <169ffc030606031411x5ad27411qf6620f2c7f739462@mail.gmail.com> (raw)
In-Reply-To: <9acccfe50605261952o7b548a6ah9710d3f8fff42f0d@mail.gmail.com>
Hi,
First .. arrgghh .. I forgot, I am deeply sorry..
On 27/05/06, Kevin O'Gorman <kogorman@gmail.com> wrote:
> Open to debate. I'd think it's not very dangerous at the *end* of the
> PATH.
True, I have modified the script so that a . may enter the PATH (etc)
only as the final entry. Also good point about ~/bin .. it is just as
dangerous.
> Thanks...
Check out this:
http://kutzooi.co.uk/cleanpath.sh.txt
All dups will be stripped, all "." entries (bar the last) will be stripped also.
Hope this is what you needed.
Mark
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-03 21:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 22:56 [gentoo-user] bash wizardry needed: PATH and MANPATH grow and grow and grow Kevin O'Gorman
2006-05-23 20:06 ` znx
2006-05-24 14:58 ` Kevin O'Gorman
2006-05-26 1:27 ` znx
2006-05-27 2:52 ` Kevin O'Gorman
2006-06-03 21:11 ` znx [this message]
2006-07-05 19:33 ` Boyd Stephen Smith Jr.
2006-07-07 18:31 ` Kevin O'Gorman
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=169ffc030606031411x5ad27411qf6620f2c7f739462@mail.gmail.com \
--to=znxster@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox