From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Peter Stephenson <pws@csr.com>,
zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: HP-UX 11.00 tgetenv dilemma
Date: Wed, 13 Jun 2001 05:00:29 +0000 [thread overview]
Message-ID: <1010613050029.ZM25098@candle.brasslantern.com> (raw)
In-Reply-To: <Tc0a88d01541a07696f@mailsweeper01.cambridgesiliconradio.com>
On Jun 12, 5:04pm, Peter Stephenson wrote:
}
} "Bart Schaefer" wrote:
} >
} > The remaining problem is that KSH_TYPESET should be set by `emulate bash',
} > which it is not because `emulate bash' is equivalent to `emulate sh'.
}
} ...and we don't want to set it for that because it's apparently correct for
} the POSIX shell.
Does the POSIX shell even permit parm=value arguments to `export' and
`typeset'? Maybe we're worrying about an impossibility. We've rarely
hesitated to allow forward-compatible-only extensions (i.e., in the
emulated shell the extension would cause an actual syntax error) to
remain in effect even during `emulate -R', as we're mainly concerned
that scripts written *without* such extensions will work properly.
} Should we introduce a separate emulation for bash? It's getting
} horribly complicated and we've never been that concerned about bash
} compatilibity for non-POSIX features.
Hrm. Either we should actually make it work, or we should document that
bash is not fully emulated (the way we document that csh is not fully
emulated). Or both, as there are probably other bash-isms that we don't
emulate, though we have a whole lot of OPT_ALIAS things for bash. Or
else remove `emulate bash' again and have only (|c|k|z)sh.
Doesn't seem like it's all that complicated to add another flag, though.
} By the way, bash also seems to have the equivalent of MAGIC_EQUAL_SUBST
Hrm, again. I suppose we could special-case those two options in the
emulate() function when the argument is `bash', although their default
values would then appear reversed in the output from `setopt'.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-06-13 5:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010611165637.24436.qmail@web12503.mail.yahoo.com>
2001-06-11 18:24 ` Andrej Borsenkow
2001-06-11 22:05 ` Export problem a normal guy
2001-06-11 22:52 ` HP-UX 11.00 tgetenv dilemma Bart Schaefer
2001-06-12 10:25 ` Peter Stephenson
2001-06-12 14:25 ` Bart Schaefer
2001-06-12 16:04 ` Peter Stephenson
2001-06-13 5:00 ` Bart Schaefer [this message]
2001-06-13 5:35 ` Andrej Borsenkow
2001-06-13 13:04 ` Clint Adams
2001-06-12 17:16 ` KSH_TYPESET Peter Stephenson
2001-06-12 17:22 ` KSH_TYPESET Peter Stephenson
[not found] <20010602004009.8849.qmail@web12507.mail.yahoo.com>
2001-06-08 5:26 ` HP-UX 11.00 tgetenv dilemma Andrej Borsenkow
2001-06-08 16:10 ` 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=1010613050029.ZM25098@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=pws@csr.com \
--cc=zsh-workers@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).