From: Haakon Riiser <haakon.riiser@fys.uio.no>
To: zsh-workers@sunsite.dk
Subject: Unexpected alias expansion in history list
Date: Mon, 11 Aug 2003 00:19:07 +0200 [thread overview]
Message-ID: <20030810221907.GA15013@s.chello.no> (raw)
The following "bug" is probably not important, since it only
happens in a syntactically illegal command, but I chose to report
it anyway, in case the bug has other (more serious) symptomps.
Steps to reproduce:
% zsh -f
% alias foo='foo bar'
% (foo) foo
zsh: parse error near `foo'
% history
1 alias foo='foo bar'
2 (foo) foo bar
^^^^^^^
Here, the second "foo" has been expanded. This only happens when
the first word in the alias expansion is the same as the name of
the alias being expanded.
Verified on the following systems:
zsh 4.1.1 (i686-pc-linux-gnu)
zsh 4.0.2 (i686-pc-linux-gnu)
zsh 4.0.2 (sparc-sun-solaris2.6)
zsh 3.0.6 (sparc-sun-solaris2.6)
--
Haakon
next reply other threads:[~2003-08-10 22:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-10 22:19 Haakon Riiser [this message]
2003-08-11 13:10 ` 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=20030810221907.GA15013@s.chello.no \
--to=haakon.riiser@fys.uio.no \
--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).