From: "Jun T." <takimoto-j@kba.biglobe.ne.jp>
To: zsh-users@zsh.org
Subject: Re: zmv, case insensivity and possible the lack of coffee
Date: Sat, 8 Aug 2015 20:01:42 +0900 [thread overview]
Message-ID: <CC3D8FC7-0C83-4D26-9DF9-FAF9EB6E5365@kba.biglobe.ne.jp> (raw)
In-Reply-To: <20150808054333.GC4378@solfire>
2015/08/08 14:43, meino.cramer@gmx.de wrote:
> If even detox fails, the script fails none of the zmvs will be
> executed.
> If the first zmv failed the second will not be tried.
Try putting 'set +e' at the beginning of the script:
#!/bin/zsh
set +e
detox ...
If this works, then I suspect you have 'set -e' (or 'setopt errexit')
somewhere in your startup scripts (/etc/zshenv or ~/.zshenv ?).
next prev parent reply other threads:[~2015-08-08 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 5:43 Meino.Cramer
2015-08-08 6:15 ` Eric Cook
2015-08-08 11:01 ` Jun T. [this message]
2015-08-09 0:15 ` 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=CC3D8FC7-0C83-4D26-9DF9-FAF9EB6E5365@kba.biglobe.ne.jp \
--to=takimoto-j@kba.biglobe.ne.jp \
--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).