From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>,
zsh-workers@sunsite.auc.dk
Subject: Re: List of unresolved issues
Date: Wed, 12 Apr 2000 17:26:13 -0700 [thread overview]
Message-ID: <000412172613.ZM12744@candle.brasslantern.com> (raw)
In-Reply-To: <E12fUAM-0001Ef-00.2000-04-12-21-55-14@cmailg1.svr.pol.co.uk>
On Apr 12, 9:55pm, Peter Stephenson wrote:
>
> I looked at the discussion we had earlier about typeset -x in functions
> (accidentally, by going to the top of the folder and starting to reply to
> things 3000 messages ago... just as well I realised) and frankly it doesn't
> increase my enthusiasm for doing anything about it. It's all due to the
> confusion of `typeset' and `local' in ksh. With the documented fact that
> `export' is equivalent to `typeset -gx', zsh is even now the only shell to
> handle this in a consistent way.
Are we both talking about the same things here?
There's already been a patch that makes `typeset -x' == `typeset -gx'.
The only remaining question (I think) is whether a variable that is already
a local can be put into the environment, and if so, whether such a variable
can be automatically removed from the environment again when the scope ends.
E.g.:
local foo
export foo # in zsh this is a no-op;
# in ksh it creates an environment string that is
# removed from the environment at function exit
This doesn't have anything to do with confusion of `typeset' and `local';
it has to do with `export' NOT being confused with `typeset'.
How does that make zsh more consistent?
next prev parent reply other threads:[~2000-04-13 0:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-12 6:14 Bart Schaefer
2000-04-12 15:56 ` Andrej Borsenkow
2000-04-12 20:55 ` Peter Stephenson
2000-04-13 0:26 ` Bart Schaefer [this message]
2000-04-13 8:56 ` Peter Stephenson
2000-04-13 14:10 ` PATCH: local exports Peter Stephenson
2000-04-13 15:42 ` Bart Schaefer
2000-04-13 17:54 ` PATCH: " Peter Stephenson
2000-05-01 5:21 ` List of unresolved issues (update) Bart Schaefer
2000-05-01 9:09 ` Adam Spiers
2000-05-02 9:50 ` Peter Stephenson
2000-04-13 12:46 List of unresolved issues Sven Wischnowsky
2000-04-13 15:55 ` Bart Schaefer
2000-04-14 8:18 Sven Wischnowsky
2000-04-14 14:57 ` 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=000412172613.ZM12744@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=pws@pwstephenson.fsnet.co.uk \
--cc=zsh-workers@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).