From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Alias expansion rules taken up for POSIX standards review
Date: Sat, 13 Jun 2015 14:47:35 -0700 [thread overview]
Message-ID: <CABkvzcu0yY28NVsOZ9k1an60egO4wHeqv7B_mOQXg4fU4h2FDA@mail.gmail.com> (raw)
I should have brought this up last week but have been somewhat
distracted from the austin-group of late. Issue ID 953 has been
opened to clarify whether
alias cmd='foo &'
cmd&bar
should semantically expand to
foo && bar # valid "and" syntax
vs.
foo & & bar # syntax error
We made the latter choice for zsh as of the 5.0.8 release, for what I
think are several good reasons (and one pragmatic one, which is that
not doing that breaks our lexer in an unpleasant and difficult-to-fix
way).
My ability to post to the austin-group list has been crippled for a
while, so if any of you who are still able to be active want to chime
in, it would be appreciated.
reply other threads:[~2015-06-13 21:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CABkvzcu0yY28NVsOZ9k1an60egO4wHeqv7B_mOQXg4fU4h2FDA@mail.gmail.com \
--to=schaefer@brasslantern.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).