From: "Lawrence Velázquez" <larryv@zsh.org>
To: "Anthony Heading" <ajrh@ajrh.net>
Cc: zsh-users@zsh.org
Subject: Re: view onto command pipeline?
Date: Wed, 20 Jul 2022 21:35:51 -0400 [thread overview]
Message-ID: <645ba344-9d97-4ddf-82c6-e6338c98da8b@www.fastmail.com> (raw)
In-Reply-To: <da22373c-43d5-44ad-b146-8c09f22c6665@www.fastmail.com>
On Wed, Jul 20, 2022, at 8:15 PM, Anthony Heading wrote:
> Agree
> quoting $@ makes sense here since this is a wrapper, but I find more
> often dropping empty
> arguments is often very helpful after splits and suchlike.
>
> But as to "${opts[@]}"... Just too ugly to do that all the time, no?
> Instead, use
> zsh's awesome sticky emulation:
>
> emulate zsh -c 'autoload -Uz ~/my-zsh-funcs/*'
Leaving $opts[@] unquoted still elides empty elements in this
context; that behavior is not limited to $@. (If this is what you
actually want, go for it. Just don't think that fiddling with
options has an effect.)
> Very helpful for insulating the risks of unexpected option settings,
> and makes it
> safe to use unquoted variables. As a rule of thumb, at least :-)
It's better to run ''emulate -L zsh'' inside the function itself
(or localize and [un]set options individually as desired) to achieve
a known state, rather than relying on a specific method of invocation.
--
vq
next prev parent reply other threads:[~2022-07-21 1:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 16:15 Anthony Heading
2022-07-16 21:30 ` Bart Schaefer
2022-07-20 11:23 ` Anthony Heading
2022-07-20 11:37 ` Dominik Vogt
2022-07-20 12:22 ` Vincent Bernat
2022-07-20 12:35 ` Dominik Vogt
2022-07-20 19:07 ` Lawrence Velázquez
2022-07-21 0:15 ` Anthony Heading
2022-07-21 1:35 ` Lawrence Velázquez [this message]
2022-07-21 2:11 ` Anthony Heading
2022-07-21 3:15 ` Lawrence Velázquez
2022-07-21 6:43 ` Dominik Vogt
2022-08-04 21:12 ` Felipe Contreras
2022-07-20 19:27 ` Phil Pennock
2022-07-21 0:18 ` Anthony Heading
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=645ba344-9d97-4ddf-82c6-e6338c98da8b@www.fastmail.com \
--to=larryv@zsh.org \
--cc=ajrh@ajrh.net \
--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).