From: Bart Schaefer <schaefer@brasslantern.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 14:05:54 -0700 [thread overview]
Message-ID: <CAH+w=7aB1+Fz3gVU8Ex2Wgb7jUh0LY+uCOy=Az6e9bK7-X+E6w@mail.gmail.com> (raw)
In-Reply-To: <048e0b3d-6da9-4905-b1ad-253647cea0d3@www.fastmail.com>
On Mon, Oct 25, 2021 at 1:41 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> I don't see why a function's caller should decide whether the callee
> should or shouldn't elide nulls. I think the function's author should
> make that decision. [...] Having some
> way to provide packaged code to others in a way that the code will
> run under predictable syntax would be nice…
Isn't that what
emulate zsh [options] -c 'autoload -U packagebootstrapper'
is for? Yeah, some syntactic sugar would be nice (e.g., it's a pain
to have to quote the argument of the -c option, rather than [say]
using a code block in braces).
Anyway, we haven't yet explored all the ramifications of changing null
elision. What effect does it have on $(...) in an array context, for
example? Any?
next prev parent reply other threads:[~2021-10-25 21:06 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 [this message]
2021-10-25 21:20 ` Roman Perepelitsa
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='CAH+w=7aB1+Fz3gVU8Ex2Wgb7jUh0LY+uCOy=Az6e9bK7-X+E6w@mail.gmail.com' \
--to=schaefer@brasslantern.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).