From: Chris Jepeway <jepeway@blasted-heath.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-users@sunsite.dk
Subject: Re: ksh Emulation Not Clearing Envariables
Date: Tue, 11 May 2004 12:59:19 -0400 [thread overview]
Message-ID: <8AFD8741-A36C-11D8-B3B9-000A95B34D8E@blasted-heath.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0405091449250.29962-100000@toltec.zanshin.com>
>
>> I'd expect the output to be
>>
>> X=one
>>
>> Instead, I see
>>
>> X=one
>> X=one
>>
>> Without ksh emulation enabled, I see the expected output.
>>
>> This is a bug, right?
>
> It's the intended behavior. Whether the intention is wrong, I'm not
> sure.
Odd.
POSIX wants the envariable to persist across invocations
of the function "e"? That seems...counter-intuitive.
I thought the whole point of
VAR=val cmd
was as a shortcut to
export VAR=val ; cmd ; unset VAR
nevermind dovetailing with execve()'s env pointer.
Sure, in this case, cmd is a shell function, but...well...so what?
Eeesh. POSIX.
But, anyways, the command is "emulate ksh" not "emulate posix".
Any chance this behavior could change to follow ksh? ksh88 as
distributed w/ Solaris-8 is what I'm using for comparison.
>> Me
> Bart
Chris <jepeway@blasted-heath.com>.
(Oh, hey, could folk cc me on replies? I'm not yet on the list.)
next prev parent reply other threads:[~2004-05-11 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-09 0:41 Chris Jepeway
2004-05-09 21:58 ` Bart Schaefer
2004-05-10 14:52 ` Peter Stephenson
2004-05-11 17:03 ` Chris Jepeway
2004-05-11 16:59 ` Chris Jepeway [this message]
2004-05-11 17:34 ` Peter Stephenson
[not found] ` <040511181944.AA29985.SM@caleb.ins.cwru.edu>
2004-05-11 18:44 ` Chris Jepeway
2004-05-11 20:22 ` Bart Schaefer
[not found] ` <040511192759.AA02456.SM@caleb.ins.cwru.edu>
2004-05-11 20:38 ` Chris Jepeway
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=8AFD8741-A36C-11D8-B3B9-000A95B34D8E@blasted-heath.com \
--to=jepeway@blasted-heath.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@sunsite.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).