From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: real time alias?
Date: Fri, 16 Mar 2018 11:56:31 -0700 [thread overview]
Message-ID: <f97012ca-0648-965b-7999-182117252769@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7Y4OdizU28ZAMZ=Hw9sz1hgarg9e+KuQbtHtOTAWOheqw@mail.gmail.com>
On 16/03/18 11:13 AM, Bart Schaefer wrote:
> 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.
Right, because it might not be a self contained block of code, it could
have syntactic effects on the rest 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.
I get it. The function can't 'grab' a new version of the alias without
recompiling itself which ends up being far more trouble than it's
worth. Mind, my functions do know where they came from:
(1)TYPE: c is a shell function from /aWorking/Zsh/Source/c:
... still I get the point, the sort of thing I'm speculating about is
square circles, best to leave aliases as the strings of characters that
they are.
next prev parent reply other threads:[~2018-03-16 18:56 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
2018-03-16 18:56 ` Ray Andrews [this message]
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=f97012ca-0648-965b-7999-182117252769@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).