From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Marlon Richert <marlon.richert@gmail.com>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Bug report: `setopt noaliases` not respected in `local` statement without assignment.
Date: Sun, 29 Mar 2020 12:24:26 +0200 [thread overview]
Message-ID: <CAN=4vMpbXEL=XSji4J9NRcaBud3-+YzNXpePj0i79EDB67juRA@mail.gmail.com> (raw)
In-Reply-To: <20200326223449.0a090ae6@tarpaulin.shahaf.local2>
On Thu, Mar 26, 2020 at 11:34 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> There are a few other options to worry about, e.g., KSH_ARRAYS,
> IGNORE_CLOES_BRACES.
Good point.
I also should've mentioned that `emulate zsh -o no_aliases -c "..."`
shouldn't be used if some of the functions you define must run with
user-defined options. E.g., if you want to respect user's
dot_glob/no_dot_glob (fzf does) or
interactive_comments/no_interactive_comments (f-sy-h does), then this
approach is out.
Here's another option that doesn't require one to create a new file:
() { 'emulate' '-L' 'zsh' '-o' 'no_aliases' && 'eval' "$(<<\END
# original file content goes here
END
)"; }
Downsides:
- one fork (increases loading time)
- breaks syntax highlighting in code editors
- zcompile won't be effective at speeding up loading time
- some aliases can still break this; for example: alias -g '()'=nope
Roman.
next prev parent reply other threads:[~2020-03-29 10:25 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
2020-03-26 10:38 ` Roman Perepelitsa
2020-03-26 22:34 ` Daniel Shahaf
2020-03-29 10:24 ` Roman Perepelitsa [this message]
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='CAN=4vMpbXEL=XSji4J9NRcaBud3-+YzNXpePj0i79EDB67juRA@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=d.s@daniel.shahaf.name \
--cc=marlon.richert@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).