From: "Michael Barnes" <mibarnes@vt.edu>
To: zsh users mailing list <zsh-users@sunsite.auc.dk>
Subject: Re: Remove a PATH component
Date: Tue, 9 Mar 1999 10:57:09 -0500 [thread overview]
Message-ID: <19990309105709.A30810@vt.edu> (raw)
In-Reply-To: <19990309163323.A36932@physik.uni-dortmund.de>; from Klaus Wacker on Tue, Mar 09, 1999 at 04:33:23PM +0100
Try testing for ZSH_VERSION.
On Tue, Mar 09, 1999 at 04:33:23PM +0100, Klaus Wacker wrote:
> Dear zsh, I am trying to write a script to be sourced which removes
> PATH components matching a given pattern and which is supposed to be
> usable from zsh as well as ksh, bash etc. The best I have come up with
> so far is the following:
>
> ----------cut-here----------------------------------------
> oldifs="$IFS"
> IFS=:
> if [[ $SHELL = *zsh ]]
> then
> set ${=PATH}
> else
> set $PATH
> fi
> IFS="$oldifs"
> PATH=
> for i
> do
> case $i in
> *tetex*)
> ;;
> *)
> PATH=$PATH:$i
> ;;
> esac
> done
> PATH=${PATH#:}
> ----------cut-here----------------------------------------
>
> This works for people who stick with their login shell, but not for
> someone who calls ksh from zsh because then SHELL remains set to zsh.
> My first try was to test $0 instead of $SHELL, but that gets set to
> the name of the file being sourced by zsh (with some option settings).
>
> Does anybody have a better idea either for a reliable test on whether
> zsh is running or for a way which avoids the test?
>
> (I know that the above fragment breaks with 10 or more PATH components
> - I should use a while loop with shift instead of the for loop).
>
> --
> Klaus Wacker wacker@Physik.Uni-Dortmund.DE
> Experimentelle Physik V http://www.physik.uni-dortmund.de/~wacker
> Universitaet Dortmund Tel.: +49 (231) 755 3587
> D-44221 Dortmund Fax: +49 (231) 755 3569
prev parent reply other threads:[~1999-03-09 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-09 15:33 Klaus Wacker
1999-03-09 15:57 ` Michael Barnes [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=19990309105709.A30810@vt.edu \
--to=mibarnes@vt.edu \
--cc=zsh-users@sunsite.auc.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).