From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: real time alias?
Date: Fri, 16 Mar 2018 09:47:48 -0700 [thread overview]
Message-ID: <b096bd20-ed30-4400-51c5-719b73b03bc7@eastlink.ca> (raw)
In-Reply-To: <20180315214450.sle4bsb3ab6dt56i@prometheus.u-strasbg.fr>
On 15/03/18 02:44 PM, Marc Chantreux wrote:
> my advice is: see aliases as macro: don't use it as long as you can
> achieve things with functions. one of the reasons is aliases can be used
> after a variable expansion and so you can get some surprising behaviors.
Yeah, I know what to expect, I'm mostly just curious about possibilities.
$ alias test2="echo this is the original alias test2"
$ function test3 () { echo this is function test3 }
$ function test1 ()
{
test2
test3
}
$ alias test2="echo changed alias test2"
$ function test3 () { echo "test3 is now changed" }
$ test1
this is the original alias test2
test3 is now changed
... to be honest I can't even think of a reason to want anything more
than what we have, but I was curious. One might imagine:
$ function test1 ()
{
test2 # unchanged since last sourcing of this function.
setopt GRAB_ALIASES_AGAIN test2
test2 # Up-to-date.
test3
}
Nevermind.
next prev parent reply other threads:[~2018-03-16 16:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 17:51 Ray Andrews
2018-03-15 17:57 ` Jérémie Roquet
2018-03-15 18:13 ` Ray Andrews
2018-03-15 21:44 ` Marc Chantreux
2018-03-15 21:46 ` Marc Chantreux
2018-03-16 17:19 ` Justin M Wozniak
2018-03-16 17:41 ` Ray Andrews
2018-03-17 16:00 ` Marc Chantreux
2018-03-16 17:51 ` Marc Chantreux
2018-03-16 16:47 ` Ray Andrews [this message]
2018-03-16 17:41 ` Marc Chantreux
2018-03-16 18:13 ` Bart Schaefer
2018-03-16 18:56 ` Ray Andrews
2018-03-18 23:01 ` Bart Schaefer
2018-03-19 0:05 ` Ray Andrews
2018-03-17 23:17 ` Bart Schaefer
[not found] <98aa0638-97ed-dfe0-8dd2-39129d02c084__39937.2481661432$1521136270$gmane$org@eastlink.ca>
2018-03-17 22:47 ` Stephane Chazelas
2018-03-18 3:20 ` Ray Andrews
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=b096bd20-ed30-4400-51c5-719b73b03bc7@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@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).