From: Marlon Richert <marlon.richert@gmail.com>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Bug report: `setopt noaliases` not respected in `local` statement without assignment.
Date: Thu, 26 Mar 2020 12:27:10 +0200 [thread overview]
Message-ID: <CAHLkEDurch52306wHG4q6QWt-VXxMmtJSWhBE0s-JU=wTf-VdA@mail.gmail.com> (raw)
In-Reply-To: <CAN=4vMq_EAtuj-K9P9FpmGADX_ER5msF5aFL6MtKhcT6O+dXxQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
Aha. So, if I want that aliases don't get expanded in the functions in
https://github.com/junegunn/fzf/blob/master/shell/completion.zsh, then
where should I put the `setopt noaliases` statement? Does it suffice to
just put `emulate -L zsh; setopt localoptions noaliases;` at the top of the
file? I don't want the noaliases option to leak into my own shell
environment.
Or is there a better solution possible here than using noaliases?
On Thu, 26 Mar 2020 at 11:59, Roman Perepelitsa <roman.perepelitsa@gmail.com>
wrote:
> On Thu, Mar 26, 2020 at 10:55 AM Marlon Richert
> <marlon.richert@gmail.com> wrote:
> >
> > Test case:
> >
> > alias -g tail="multitail -Cs --follow-all"
> > f() {
> > setopt localoptions no_aliases
> > local tail
> > tail=1
> > echo $tail
> > }
>
> Alias expansion happens when functions get parsed. If you don't want
> `tail` to be alias-expanded within function `f`, you need to add
> `setopt no_aliases` before the function of `f`.
>
> > g() {
> > setopt localoptions no_aliases
> > local tail=1
> > echo $tail
> > }
>
> `tail` within `local tail=1` is not subject to global alias expansion.
>
> Roman.
>
next prev parent reply other threads:[~2020-03-26 10:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 9:54 Marlon Richert
2020-03-26 9:59 ` Roman Perepelitsa
2020-03-26 10:27 ` Marlon Richert [this message]
2020-03-26 10:38 ` Roman Perepelitsa
2020-03-26 22:34 ` Daniel Shahaf
2020-03-29 10:24 ` Roman Perepelitsa
2020-03-29 20:47 ` Daniel Shahaf
2020-03-29 21:03 ` Roman Perepelitsa
2020-03-29 21:12 ` Daniel Shahaf
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='CAHLkEDurch52306wHG4q6QWt-VXxMmtJSWhBE0s-JU=wTf-VdA@mail.gmail.com' \
--to=marlon.richert@gmail.com \
--cc=roman.perepelitsa@gmail.com \
--cc=zsh-workers@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).