From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: schaefer@brasslantern.com (Bart Schaefer)
Cc: zsh-workers@math.gatech.edu
Subject: Re: PWD parameter
Date: Sun, 24 May 1998 02:51:55 -0500 (CDT) [thread overview]
Message-ID: <199805240751.CAA21301@hzoli.home> (raw)
In-Reply-To: <980523225726.ZM5196@candle.brasslantern.com> from Bart Schaefer at "May 23, 98 10:57:26 pm"
Bart Schaefer wrote:
> On May 23, 11:44pm, Zoltan Hidvegi wrote:
> } Subject: PWD parameter
> }
> } The standard does not mention PWD or OLDPWD in the descriprion of the
> } shell special parameters
>
> Personally, I rather like having PWD be a special parameter. If you go
> by the letter of that standard you quoted, PWD would not be set at all
> when the shell first started up; it would only become set after a "cd".
> That's surely bogus.
My patch does set PWD and OLDPWD on startup. The standard allows that
but does not require it. Why do you think that PWD is better be a
special parameter? Scripts do set PWD and if we want to allow people to
use zsh as /bin/sh then we have to allow them to write PWD. That was my
main reason for the patch, not the standard, since I link /bin/sh to zsh.
If PWD is special, assignments will write directly to the internal pwd
variable which can cause unexpected shell behavior. That's why PWD was
read-only. Alternatively, you can just ignore assignments to PWD without
giving an error message, but that's a bad solution.
As long as you do not try to assign PWD, my patch does not change zsh's
behavior, other than exporting OLDPWD which was not exported before.
Zoltan
next prev parent reply other threads:[~1998-05-24 7:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-24 4:44 Zoltan Hidvegi
1998-05-24 5:57 ` Bart Schaefer
1998-05-24 7:51 ` Zoltan Hidvegi [this message]
1998-05-24 16:42 ` Bart Schaefer
1998-05-24 17:38 ` Zoltan Hidvegi
1998-05-25 2:16 ` Bart Schaefer
1998-05-25 3:02 ` Zoltan Hidvegi
1998-05-25 4:02 ` Bart Schaefer
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=199805240751.CAA21301@hzoli.home \
--to=hzoli@cs.elte.hu \
--cc=schaefer@brasslantern.com \
--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).