From: Bart Schaefer <schaefer@brasslantern.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: zmv exits from function
Date: Sat, 30 Dec 2023 14:21:53 -0800 [thread overview]
Message-ID: <CAH+w=7ZpRTKnkCuXTpHtj2o_Oh4_kr00WevSxC_bd1HD51tC=Q@mail.gmail.com> (raw)
In-Reply-To: <191d8a2b-2fcc-4553-91f4-ac8dfb70b1c8@eastlink.ca>
On Sat, Dec 30, 2023 at 1:02 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
>
> On 2023-12-30 12:38, Bart Schaefer wrote:
> >
> > Arguably zmv could use null_glob. Thoughts from -workers?
>
> That's that option that makes everything grind to a halt if nothing if found?
No, you're thinking of nomatch, which as I said is already in effect
and causing the result that you see. The null_glob option supersedes
no_match and makes globs that don't match anything disappear without
an error. This is in contrast to the no_nomatch option which leaves
the glob un-expanded but does not remove it. Setting null_glob
globally can be dangerous because it can leave a command with no
arguments at all or with its arguments in a different order than
expected.
> Think I recall that " (N) " setting to cope with it?
The (N) glob qualifier turns ON null_glob to override no_match, yes.
That's the suggested amendment to zmv for which I'm asking -workers
opinion.
next prev parent reply other threads:[~2023-12-30 22:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-30 17:42 Ray Andrews
2023-12-30 20:38 ` Bart Schaefer
2023-12-30 21:02 ` Ray Andrews
2023-12-30 22:21 ` Bart Schaefer [this message]
2023-12-30 21:15 ` Mikael Magnusson
2023-12-31 3:43 ` Ray Andrews
2023-12-31 3:58 ` Bart Schaefer
2023-12-31 15:53 ` Ray Andrews
2023-12-31 21:44 ` Bart Schaefer
2023-12-31 22:06 ` Ray Andrews
2024-01-02 14:51 ` Mark J. Reed
2024-01-02 17:01 ` Ray Andrews
2024-01-02 11:50 ` Peter Stephenson
2024-01-02 17:08 ` Ray Andrews
2024-01-02 17:47 ` Mark J. Reed
2024-01-02 18:16 ` Ray Andrews
2024-01-02 20:24 ` Bart Schaefer
2024-01-02 21:32 ` Ray Andrews
2024-01-02 17:48 ` Peter Stephenson
2024-01-02 19:07 ` Bart Schaefer
2024-01-02 19:52 ` Ray Andrews
2024-01-03 9:55 ` Peter Stephenson
2024-01-03 15:46 ` Ray Andrews
2024-01-03 19:01 ` Bart Schaefer
2023-12-30 22:34 ` Bart Schaefer
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=7ZpRTKnkCuXTpHtj2o_Oh4_kr00WevSxC_bd1HD51tC=Q@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=rayandrews@eastlink.ca \
--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).