From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: zmv exits from function
Date: Sat, 30 Dec 2023 13:02:02 -0800 [thread overview]
Message-ID: <191d8a2b-2fcc-4553-91f4-ac8dfb70b1c8@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7YUYK+2wg+r4yuxieBY6D4epwvi3sPYrs6tcWJk6GwKbw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
On 2023-12-30 12:38, Bart Schaefer wrote:
> Just run the zmv in a subshell:
>
> ( zmv '(*).SNT' '$1.eml' )
> ( zmv '(*).MES' '$1.eml' )
>
Perfect :-)
> Arguably zmv could use null_glob. Thoughts from -workers?
That's that option that makes everything grind to a halt if nothing if
found? Think I recall that " (N) " setting to cope with it? From a
users point of view it just makes trouble where no trouble really
exists. BTW, I did look at the source and noticed no return values, I
had thought that something like ' zmv ... && echo "Success" || echo
"Nope"' ... might catch it.
[-- Attachment #2: Type: text/html, Size: 1272 bytes --]
next prev parent reply other threads:[~2023-12-30 21:04 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 [this message]
2023-12-30 22:21 ` Bart Schaefer
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=191d8a2b-2fcc-4553-91f4-ac8dfb70b1c8@eastlink.ca \
--to=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).