From: Peter Stephenson <pws@ifh.de>
To: zsh-workers@math.gatech.edu (Zsh hackers list)
Subject: Re: bug with empty path
Date: Wed, 04 Dec 1996 10:00:21 +0100 [thread overview]
Message-ID: <199612040900.KAA20985@sgi.ifh.de> (raw)
In-Reply-To: "Zoltan Hidvegi"'s message of "Tue, 03 Dec 1996 17:57:58 MET." <199612031657.RAA25108@bolyai.cs.elte.hu>
Zoltan Hidvegi wrote:
> Peter Stephenson wrote:
> > The lines:
> > path=()
> > and
> > PATH=
> > have different effects: the first produces an empty path array, the
> > second a path with one blank element. This turns up in the following:
>
> I do not think it is a bug. Of course other shells couldn't set an empty
> path but zsh is better than that. The path is really an array and the PATH
> scalar is just a representation which has this inefficiency.
>
> One may want to use a really empty path sometimes which is best achieved
> with path=().
I see the point, but do you really want to try and explain this to the
average user? ``The PATH is sometimes empty, and sometimes really empty,
but only if you set it as an array; if it looks empty, it may be empty
or really empty; if it's empty but not really empty it pretends to be
set to the current directory...''
Besides which, when passed as an environment variable --- even down to another
zsh --- the only possibilities are either not having it set or an empty
PATH (which is therefore not really empty in the above sense).
Still, there's some confusion in having both $path and $PATH which is
probably unavoidable, so I can live with it.
--
Peter Stephenson <pws@ifh.de> Tel: +49 33762 77366
WWW: http://www.ifh.de/~pws/ Fax: +49 33762 77413
Deutches Electronen-Synchrotron --- Institut fuer Hochenergiephysik Zeuthen
DESY-IfH, 15735 Zeuthen, Germany.
next prev parent reply other threads:[~1996-12-04 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-11-25 14:33 Peter Stephenson
1996-12-03 16:57 ` Zoltan Hidvegi
1996-12-04 9:00 ` Peter Stephenson [this message]
1996-12-04 20:59 ` Zoltan Hidvegi
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=199612040900.KAA20985@sgi.ifh.de \
--to=pws@ifh.de \
--cc=zsh-workers@math.gatech.edu \
/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).