Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: ksh Emulation Not Clearing Envariables

X-seq: zsh-users 7442
From: Chris Jepeway <jepeway@xxxxxxxxxxxxxxxxx>
To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
Subject: Re: ksh Emulation Not Clearing Envariables
Date: Tue, 11 May 2004 12:59:19 -0400
Cc: zsh-users@xxxxxxxxxx
In-reply-to: <Pine.LNX.4.44.0405091449250.29962-100000@xxxxxxxxxxxxxxxxxx>
Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
References: <Pine.LNX.4.44.0405091449250.29962-100000@xxxxxxxxxxxxxxxxxx>

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 notsure.

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@xxxxxxxxxxxxxxxxx>.
(Oh, hey, could folk cc me on replies?  I'm not yet on the list.)

Follow-Ups:
- Re: ksh Emulation Not Clearing Envariables
  - From: Peter Stephenson

References:
- Re: ksh Emulation Not Clearing Envariables
  - From: Bart Schaefer

Messages sorted by: Reverse Date, Date, Thread, Author