From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Disabling null elision (was: Re: Most Recent File)
Date: Mon, 25 Oct 2021 23:20:39 +0200 [thread overview]
Message-ID: <CAN=4vMqeHzo=B+413xX_9P=NyjC=M113QFAzR-=wiTLdCaFOdQ@mail.gmail.com> (raw)
In-Reply-To: <048e0b3d-6da9-4905-b1ad-253647cea0d3@www.fastmail.com>
On Mon, Oct 25, 2021 at 10:42 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> Roman Perepelitsa wrote on Mon, 25 Oct 2021 20:02 +00:00:
>
> > It's also nice that this option would affect parsing, only evaluation,
> > so it won't be necessary to care about it when defining functions.
>
> How so?
Some options can be set within a function for the function to work as
the author has intended. For example, extended_glob.
function foo() {
emulate -L zsh -o extended_glob
# can extended-glob here to one's heart's content
[[ $1 == a## ]]
}
Other options must be set when the function is defined. For example,
brace_expand.
# if brace_expand is unset here, bar is screwed
unset brace_expand # bwa-ha-ha
function bar() {
emulate -L zsh -o brace_expand # this won't help
typeset var{1,2,3}=42
}
setopt brace_expand # this won't help either
bar # oh no!
Options of the second kind cause more grief.
As Bar says, autoload -Uz is key when it comes to loading plugins and
sourcing is a losing game (I learned this from Bart earlier).
Sometimes you still have to have a function in a plugin that must run
with user options but at least that's just for evaluation and not for
parsing.
Roman.
next prev parent reply other threads:[~2021-10-25 21:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 16:15 Most Recent File Vin Shelton
2021-10-23 16:43 ` Dominik Vogt
2021-10-23 16:58 ` Peter Stephenson
2021-10-23 17:24 ` Dominik Vogt
2021-10-23 17:32 ` Peter Stephenson
2021-10-23 18:39 ` Bart Schaefer
2021-10-23 19:07 ` Vin Shelton
2021-10-23 19:26 ` Bart Schaefer
2021-10-23 20:43 ` Vin Shelton
2021-10-23 20:56 ` Pier Paolo Grassi
2021-10-23 22:42 ` Bart Schaefer
2021-10-24 0:24 ` Pier Paolo Grassi
2021-10-24 0:32 ` Paul
2021-10-24 1:45 ` Dominik Vogt
2021-10-24 7:22 ` Roman Perepelitsa
2021-10-25 19:45 ` Disabling null elision (was: Re: Most Recent File) Daniel Shahaf
2021-10-25 20:02 ` Roman Perepelitsa
2021-10-25 20:41 ` Daniel Shahaf
2021-10-25 21:00 ` Ray Andrews
2021-10-25 21:09 ` Bart Schaefer
2021-10-25 21:05 ` Bart Schaefer
2021-10-25 21:20 ` Roman Perepelitsa [this message]
2021-10-25 20:05 ` Bart Schaefer
2021-10-24 1:37 ` Most Recent File Dominik Vogt
2021-10-23 16:47 ` david rayner
2021-10-23 16:54 ` Vin Shelton
2021-10-23 16:51 ` david rayner
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=4vMqeHzo=B+413xX_9P=NyjC=M113QFAzR-=wiTLdCaFOdQ@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=d.s@daniel.shahaf.name \
--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).