From: Peter Stephenson <p.stephenson@samsung.com>
To: wumingxwk@gmail.com, zsh-workers@zsh.org
Subject: Re: [BUG]builtin echo error doing arguments parsing
Date: Thu, 22 Feb 2018 09:37:11 +0000 [thread overview]
Message-ID: <20180222093711.0777e602@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <CAGobuLee=R-FsgX=8XBg9Q2XHm17yLU6q3QzPWCiryCeTX7Kfg@mail.gmail.com>
On Wed, 21 Feb 2018 23:23:09 -0800
wumingxwk@gmail.com wrote:
> if there is only a '-' as argument，builtin echo won't print it
It's entirely deliberate and documented, but you're quite right that it
plays merry hell with compatibility.
You might have thought it should at least be turned off in some or most
of the emulation modes...
pws
SHELL BUILTIN COMMANDS
...
All builtin commands other than precommand modifiers, even those that
have no options, can be given the argument `--' to terminate option
processing. This indicates that the following words are non-option
arguments, but is otherwise ignored. This is useful in cases where
arguments to the command may begin with `-'. For historical reasons,
most builtin commands also recognize a single `-' in a separate word
for this purpose; note that this is less standard and use of `--' is
recommended.
next prev parent reply other threads:[~2018-02-22 9:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180222072350epcas2p3185ca17f5f0e3ad69b0a41dbf743f145@epcas2p3.samsung.com>
2018-02-22 7:23 ` wumingxwk
2018-02-22 9:37 ` Peter Stephenson [this message]
2018-02-22 10:32 ` Peter Stephenson
2018-02-22 16:50 ` Mikael Magnusson
2018-02-22 17:26 ` Peter Stephenson
2018-02-22 19:00 ` Mikael Magnusson
2018-02-22 19:04 ` Bart Schaefer
2018-02-22 19:34 ` Peter Stephenson
2018-02-24 8:20 ` Stephane Chazelas
2018-02-24 9:51 ` Peter Stephenson
2018-02-24 19:41 ` Peter Stephenson
2019-04-27 6:46 ` Stephane Chazelas
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=20180222093711.0777e602@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--cc=wumingxwk@gmail.com \
--cc=zsh-workers@zsh.org \
/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).