From: Andreas Schwab <schwab@suse.de>
To: zsh-users@sunsite.dk
Cc: bug-bash@gnu.org
Subject: Re: POSIX compliance of shells - where to ask/talk about it?
Date: Fri, 26 Jul 2002 20:12:59 +0200 [thread overview]
Message-ID: <jebs8u2w9g.fsf@sykes.suse.de> (raw)
In-Reply-To: <20020725201713.GA17071@stu163.keble.ox.ac.uk> (igloo@earth.li's message of "Thu, 25 Jul 2002 21:17:13 +0100")
igloo@earth.li (Ian Lynagh) writes:
|> Hi all,
|>
|> Where should one ask/talk about POSIX shell compliance (looking for a
|> mailing list probably)?
|>
|> I am reading the standard at
|> http://www.opengroup.org/onlinepubs/007904975/utilities/xcu_chap02.html
|> and finding it very imprecise - disappointingly so (am I looking in the
|> wrong place?). I am therefore looking to implementations to clarify the
|> standard, but with things like this (all shells invoked as sh, bash
|> given --posix):
|>
|> printf "%s\n" `echo '\\\\\\\\\\\\\\\\'`
|> printf "%s\n" "`echo '\\\\\\\\\\\\\\\\'`"
|>
|> Using shells/ash:
|> \\\\
|> \\\\
|>
|> Using shells/bash:
|> \\\\\\\\
|> \\\\\\\\
|>
|> Using shells/zsh:
|> \\\\
|> \\\\\\\\
I think the key difference here is whether echo is interpreting
backslashes or not. By default, bash's builtin echo does not interpret
backslashes, and if you use "echo -e" you get the same output as ash. zsh
seems to be the odd case again.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2002-07-26 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 20:17 Ian Lynagh
2002-07-26 18:12 ` Andreas Schwab [this message]
2002-07-30 11:17 ` Peter Stephenson
2002-07-30 12:06 ` Oliver Kiddle
2002-07-30 12:48 ` Peter Stephenson
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=jebs8u2w9g.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=bug-bash@gnu.org \
--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).