From: "Martin Tournoij" <martin@arp242.net>
To: zsh-workers@zsh.org
Subject: Any way to allow clobbering empty files when noclobber is set?
Date: Wed, 03 Jun 2020 10:08:27 +0800 [thread overview]
Message-ID: <89aed74d-db7b-47ad-b218-8158838049e9@www.fastmail.com> (raw)
Hi there,
I switched from tcsh to zsh a while ago (many years too late, I know), and
found zsh can do pretty much everything better. There's one thing I rather
miss though: the 'notempty' option in 'noclobber'. To quote tcsh(1):
> If the shell variable noclobber is set, then the file must not exist or be
> a character special file [...] If notempty is given in noclobber, `>' is
> allowed on empty files; if ask is set, an interacive confirmation is
> presented, rather than an error.
1. Is there any way to do this in zsh (especially the notempty option)? I
know you can use >! to override it, but empty files are rarely important
so just allowing them to be clobbered seems better UX in most cases.
I can't find anything in zshall(1) or the interwebz.
2. Assuming the answer to 1) is "no", would any patches be accepted to add a
setting for this? I rather miss this behaviour (I actually added these
settings to tcsh a few years ago).
For context, the most common case (for me, anyway) is when I accidentally
create a file with a failing command:
$ cmd -wrong-flag > foo
stderr: you made a mistake
# Oops, we used a wrong flag, let's correct it:
$ cmd -correct-flag > foo
zsh: file exists: foo
# Ah, an empty file still got created >_< Need to remove it first, or
# replace > with >!
$ rm foo
$ cmd -correct arg > foo
Thanks,
Martin
P.S. The emailing list software told me to email zsh-workers-faq@zsh.org for
a FAQ about this list, which is what I did and it came back with:
> FAQ - Frequently asked questions of the zsh-workers@zsh.org list.
>
> None available yet.
Maybe remove that part from the template, as there is no FAQ?
next reply other threads:[~2020-06-03 2:09 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200603020919eucas1p13e26ebcbb335784d14bfb97b137f385a@eucas1p1.samsung.com>
2020-06-03 2:08 ` Martin Tournoij [this message]
2020-06-03 12:04 ` Peter Stephenson
2020-06-04 1:48 ` Daniel Shahaf
2020-06-04 2:43 ` Bart Schaefer
2020-06-04 4:06 ` Daniel Shahaf
2020-06-04 5:00 ` Bart Schaefer
2020-06-05 3:10 ` Daniel Shahaf
2020-06-05 3:18 ` Daniel Shahaf
2020-06-06 1:07 ` Bart Schaefer
2020-06-06 4:48 ` Daniel Shahaf
2020-06-06 7:04 ` Bart Schaefer
2020-06-04 6:31 ` Martin Tournoij
2020-06-05 2:22 ` Daniel Shahaf
2020-06-04 2:13 ` Vin Shelton
2020-06-04 2:35 ` Bart Schaefer
2020-06-04 2:36 ` Daniel Shahaf
2020-06-04 11:57 ` Vin Shelton
2020-06-04 5:06 ` Bart Schaefer
2020-06-04 5:41 ` Roman Perepelitsa
2020-06-05 2:07 ` Daniel Shahaf
2020-06-05 4:38 ` Roman Perepelitsa
2020-06-06 1:41 ` Bart Schaefer
2020-06-06 4:55 ` Daniel Shahaf
2020-06-06 6:25 ` Roman Perepelitsa
2020-06-06 7:08 ` Bart Schaefer
2020-06-06 8:03 ` Daniel Shahaf
[not found] ` <1941572212.466119.1591360860372@mail2.virginmedia.com>
[not found] ` <e7f7dfe2-eb4a-457b-85fb-091935a74c0e@www.fastmail.com>
2020-06-06 11:57 ` Peter Stephenson
2020-06-06 12:48 ` Roman Perepelitsa
2020-06-06 15:24 ` Bart Schaefer
2020-06-06 16:24 ` Peter Stephenson
2020-06-07 11:55 ` Daniel Shahaf
2020-06-07 17:00 ` Peter Stephenson
2020-06-08 3:27 ` Daniel Shahaf
2020-06-08 9:30 ` Peter Stephenson
2020-06-07 17:20 ` Bart Schaefer
2020-06-06 15:09 ` Bart Schaefer
2020-06-04 6:47 ` Martin Tournoij
2020-06-04 9:42 ` Peter Stephenson
2020-06-04 12:20 ` Roman Perepelitsa
2020-06-04 12:26 ` Peter Stephenson
2020-06-04 12:15 ` Peter Stephenson
2020-06-04 20:35 ` Bart Schaefer
2020-06-05 1:59 ` Daniel Shahaf
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=89aed74d-db7b-47ad-b218-8158838049e9@www.fastmail.com \
--to=martin@arp242.net \
--cc=zsh-workers@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).