From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: "typeset -x" vs. "export" in 3.1.6
Date: Sat, 23 Oct 1999 08:35:09 +0000 [thread overview]
Message-ID: <991023083509.ZM21037@candle.brasslantern.com> (raw)
Consider the following two functions:
putenv() { typeset -x $1=$2 }
setenv() { export $1=$2 }
Is it really intentional that they don't have the same behavior? (They
have the same behavior in every version from 2.5 through 3.0.7, though I
can't say for other stages in the 3.1 chain.)
This is a pretty serious incompatible change.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next reply other threads:[~1999-10-23 9:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-23 8:35 Bart Schaefer [this message]
1999-10-23 17:43 ` Bart Schaefer
1999-10-24 12:25 ` Alexandre Duret-Lutz
1999-10-24 16:09 ` 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=991023083509.ZM21037@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).