From: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>
To: a normal guy <ee_in_co@yahoo.com>
Cc: ZSH Workers Mailing List <zsh-workers@sunsite.dk>
Subject: Re: HP-UX 11.00 tgetenv dilemma
Date: Mon, 11 Jun 2001 22:24:53 +0400 [thread overview]
Message-ID: <3B250CF5.6010003@mow.siemens.ru> (raw)
In-Reply-To: <20010611165637.24436.qmail@web12503.mail.yahoo.com>
a normal guy wrote:
> Andrej
>
> At the risk of sounding ignorant, what does SUS stand for? I
> assume it is the governing document for POSIX compatibility or
> the like. Thanks,
>
Single Unix Specification a.k.a. Unix 98 (current version). It is a
superset of XPG (X/Open Portability Guide) that itself is superset of
POSIX. It has a big advantage of being available online as opposed to
either XPG or POSIX :-)
>
> P.S. What is the latest line of thought about the Export word
> splitting problem? To fix or not to fix?
>
It is not bug - it complies with standards. Granted, there are
compatibility issues (both ksh and bash behave the way you desire), but
so far you are the first person to note it :-) That does not mean I am
opposed to "fixing" it - I just have no idea how easy (or difficult) it is.
-andrej
next parent reply other threads:[~2001-06-11 18:22 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 [this message]
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
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=3B250CF5.6010003@mow.siemens.ru \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=ee_in_co@yahoo.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).