From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: How should empty aliases work?
Date: Fri, 29 Dec 2017 00:30:31 -0800 [thread overview]
Message-ID: <CAH+w=7bNy-66-v=QX2BDzkbJ5SadK7mVgd9joHGgF07364PV0w@mail.gmail.com> (raw)
Documentation says that if an alias ends in a space, then the next
word is also subject to aliasing.
Consider:
% alias empty=''
% alias output='empty echo'
% alias echo='print -r bar'
% output foo
What should happen? The doc would lead one to expect:
1. "output" expands to "empty echo"
2. "empty" expands to nothing
3. nothing does not end in a space, so the following word ("echo") is
not expanded
4. "echo foo" is executed
What actually happens is that "echo" expands and "print -r bar foo" is
executed. If that's correct, can someone explain why?
next reply other threads:[~2017-12-29 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 8:30 Bart Schaefer [this message]
2017-12-30 1:14 ` Bart Schaefer
2018-01-03 11:47 ` 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='CAH+w=7bNy-66-v=QX2BDzkbJ5SadK7mVgd9joHGgF07364PV0w@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).