From: Bart Schaefer <schaefer@brasslantern.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: real time alias?
Date: Fri, 16 Mar 2018 11:13:38 -0700 [thread overview]
Message-ID: <CAH+w=7Y4OdizU28ZAMZ=Hw9sz1hgarg9e+KuQbtHtOTAWOheqw@mail.gmail.com> (raw)
In-Reply-To: <b096bd20-ed30-4400-51c5-719b73b03bc7@eastlink.ca>
On Fri, Mar 16, 2018 at 9:47 AM, Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> $ function test1 ()
> {
> test2 # unchanged since last sourcing of this function.
> setopt GRAB_ALIASES_AGAIN test2
> test2 # Up-to-date.
> test3
> }
The result of expanding an alias might include parens, braces, pipes,
etc. - it can actually change the parsed syntax of the function body.
So to "grab aliases again" you have to recompile the whole body of the
function.
The original (unparsed) body of the function is not stored anywhere,
so to recompile it you have to get it back from wherever it originally
appeared. That's easy if the function was autoloaded from your
$fpath:
% unfunction test1; autoload test1
If the function came from some larger file (such as .zshrc), or was
defined at the command line, or was loaded from a plugin manager like
Sebastian's, the details of how to reparse it will vary.
next prev parent reply other threads:[~2018-03-16 18:13 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
2018-03-16 17:41 ` Marc Chantreux
2018-03-16 18:13 ` Bart Schaefer [this message]
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='CAH+w=7Y4OdizU28ZAMZ=Hw9sz1hgarg9e+KuQbtHtOTAWOheqw@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=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).