From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: permission denied
Date: Mon, 17 Apr 2023 15:44:42 -0700 [thread overview]
Message-ID: <97340853-a204-e2f8-e85f-e1fbea4b2c31@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7a+h1gibX=cXk6rki50jCdf=MUHKhf5+Pb5WT-KEzJzDA@mail.gmail.com>
On 2023-04-17 14:52, Bart Schaefer wrote:
>
> Aliases are replaced before variable substitutions occur (if that
> weren't true, you couldn't refer to a variable in an alias).
>
So, when $chain expands to 'l' it's too late for 'l' to undergo alias
expansion? Gotta think about that, no doubt there's rigor in order of
operations but it seems counter intuitive here. I'm expecting 'l' to be
processed just as it would be if typed on the command line. Mind,
that's what 'eval' does. Maybe if I thought about it a bit harder then
I'd see it. Obviously very basic stuff, not open to critique, but I'm
expecting 'outside in' parsing so that an alias inside a variable and a
variable inside an alias would both be fully expanded. Still there
could be very good reasons not to do that I suppose. Probably not worth
worrying about.
next prev parent reply other threads:[~2023-04-17 22:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 18:34 Ray Andrews
2023-04-17 19:07 ` Roman Perepelitsa
2023-04-17 20:41 ` Ray Andrews
2023-04-17 21:52 ` Bart Schaefer
2023-04-17 22:44 ` Ray Andrews [this message]
2023-04-18 2:41 ` Bart Schaefer
2023-04-18 3:35 ` Ray Andrews
2023-04-20 21:35 ` Ray Andrews
2023-04-20 21:47 ` Roman Perepelitsa
2023-04-20 22:09 ` Ray Andrews
2023-04-20 22:13 ` Bart Schaefer
2023-04-20 22:47 ` Ray Andrews
2023-04-21 3:12 ` Bart Schaefer
2023-04-21 13:33 ` Ray Andrews
2023-04-21 14:12 ` Peter Stephenson
2023-04-21 14:42 ` Ray Andrews
2023-04-21 21:58 ` Bart Schaefer
2023-04-22 0:56 ` Ray Andrews
2023-04-20 22:17 ` Roman Perepelitsa
-- strict thread matches above, loose matches on Subject: below --
2020-12-21 23:01 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=97340853-a204-e2f8-e85f-e1fbea4b2c31@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).