From: Richard Coleman <coleman@math.gatech.edu>
To: Peter Stephenson <pws@ifh.de>, zsh-workers@math.gatech.edu
Subject: Re: Final demise of alias stack
Date: Tue, 10 Dec 1996 11:32:00 -0500 [thread overview]
Message-ID: <199612101632.LAA09236@redwood.skiles.gatech.edu> (raw)
In-Reply-To: Your message of "Tue, 10 Dec 1996 15:32:08 +0100." <199612101432.PAA07599@sgi.ifh.de>
> (Note that this mechanism only expands one level of aliases: if the
> resulting alias is itself an alias it will not be expanded. I have
> kept this, but is it a bug?)
Peter, I haven't tried the patch yet, but are you saying that
alias ls='/usr/local/bin'
alias ll='ls -l'
won't expand all the way? Is that right?
rc
next prev parent reply other threads:[~1996-12-10 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-12-10 14:32 Peter Stephenson
1996-12-10 16:32 ` Richard Coleman [this message]
1996-12-11 8:20 ` Peter Stephenson
1996-12-11 15:52 ` 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=199612101632.LAA09236@redwood.skiles.gatech.edu \
--to=coleman@math.gatech.edu \
--cc=pws@ifh.de \
--cc=zsh-workers@math.gatech.edu \
/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).