zsh-users
 help / color / mirror / code / Atom feed
From: TjL <tjlists@bigfoot.com>
To: Zsh Users <zsh-users@sunsite.auc.dk>
Subject: huh?  where did the . come from in my $PATH????
Date: Wed, 14 Apr 1999 09:24:43 -0400 (EDT)	[thread overview]
Message-ID: <9904140918410.2711-100000@localhost> (raw)


I have this automatic $PATH maker in .zshenv:

unset PATH

for i in \
          /etc                     \
          /usr                     \
          /bin                     \
          /sbin                    \
          /usr/etc                 \
          /usr/ucb                 \
          /usr/bin                 \
          /usr/gnu/bin             \
          /usr/local/etc           \
          /usr/local/bin           \
          /usr/local/sbin          \
          /usr/local/gnu/bin       \
          /usr/local/shell-scripts \
          $HOME/Library/bin        \
          $HOME/bin                \
          $HOME/Unix/bin                     
do

         if [ -d "$i" ]; then
            PATH=$i:$PATH
	 fi   
done


Which works niftily, except that at the end of the $PATH is "." !!

See:

# echo $PATH
/usr/local/Users/fpc/Unix/bin:/usr/local/shell-scripts:/usr/local/gnu/bin:/usr/local/sbin:/usr/local/bin:/usr/local/etc:/usr/gnu/bin:/usr/bin:/usr/ucb:/usr/etc:/bin:/usr:/etc:.


Now I don't know where that "." came from, but it really really should not
be there!  In fact, I'd almost recommend a "REFUSE_DOT_IN_PATH" option
when compiling zsh!!! (force ./ if you want to execute a command in $PWD
if $PWD is not in $PATH

Any clues what is going wrong?  This is w/ an older version of zsh... I
don't even know where to get the recent versions now with the patches and
whatnot...

TjL





             reply	other threads:[~1999-04-14 13:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-14 13:24 TjL [this message]
1999-04-14 13:38 ` Andrej Borsenkow

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=9904140918410.2711-100000@localhost \
    --to=tjlists@bigfoot.com \
    --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).