From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: zsh-workers@zsh.org
Subject: Re: '>>' does not create file if set -C (noclobber) is active
Date: Sun, 28 Jun 2015 08:48:37 +0100 [thread overview]
Message-ID: <20150628074837.GB4818@chaz.gmail.com> (raw)
In-Reply-To: <558F397D.9030708@inlv.org>
2015-06-28 02:02:05 +0200, Martijn Dekker:
[...]
> At the risk of pedantry, I also wonder if 'createappend' or
> 'appendcreate' would be a better name, since "clobbering" is commonly
> understood to mean overwriting pre-existing files, not creating new ones.
[...]
Agreed, I also wonder of the rationale behind that feature. For
zsh, I understand it copied it from csh, but why would
"noclobber" prevent >> from creating files, that has nothing to
do with clobbering.
In 18 years of using zsh and tcsh before that I had never
realised they were doing that and when you reported it, I pretty
much assumed it was a bug and was very surprised when it
revealed to be a feature.
I agree it's a potentially useful feature to prevent >> from
creating files, but it shouldn't be done upon a "noclobber"
option as it's the opposite meaning that noclobber conveys.
BTW, slightly related, I think it would be nice for the shell to
have access to some of the other open() flags. I often found
myself wishing I could use O_NOFOLLOW for instance.
How about a <(flags)> operator
where flags is flag[flag...] and flag being [+] or - followed
by a one-letter flag (like r, w, a, @ (for follow)..., some of
which on by default).
So >> would be <(a)> (a implies -r+w, +w implies +c (create)).
You'd use: <(w-@)> for no-follow...
And we could implement that noclobber on >> with <(a-c)>.
That could even be extended to do lseeks(), dups(), (3<(>+20)>
to lseek(3, 20, SEEK_CUR))...
What do you think?
Yes, with that <(..)> syntax there's a slight risk of breaking
scripts that do:
diff <(cmd1) <(cmd2)> out.txt
--
Stephane
next prev parent reply other threads:[~2015-06-28 7:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 1:02 Martijn Dekker
2015-06-25 1:49 ` Bart Schaefer
2015-06-25 2:22 ` Martijn Dekker
2015-06-25 7:30 ` Bart Schaefer
2015-06-25 14:04 ` Stephane Chazelas
2015-06-25 16:00 ` Bart Schaefer
2015-06-25 19:20 ` Chet Ramey
2015-06-26 14:14 ` Martijn Dekker
2015-06-26 20:15 ` Bart Schaefer
2015-06-27 1:54 ` Martijn Dekker
2015-06-27 3:38 ` Bart Schaefer
2015-06-27 17:02 ` Peter Stephenson
2015-06-28 0:02 ` Martijn Dekker
2015-06-28 0:46 ` Martijn Dekker
2015-06-28 7:48 ` Stephane Chazelas [this message]
2015-06-28 9:15 ` Oliver Kiddle
2015-06-28 14:00 ` Stephane Chazelas
2015-06-28 18:38 ` Bart Schaefer
2015-06-28 19:30 ` Stephane Chazelas
2015-07-23 2:56 ` PATCH: sysopen (was Re: '>>' does not create file if set -C (noclobber) is active) Oliver Kiddle
2015-07-24 10:57 ` Peter Stephenson
2015-07-24 11:55 ` Peter Stephenson
2015-07-30 11:05 ` Mikael Magnusson
2015-07-31 12:41 ` Oliver Kiddle
2015-07-31 14:02 ` Mikael Magnusson
2015-06-28 17:19 ` '>>' does not create file if set -C (noclobber) is active Peter Stephenson
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=20150628074837.GB4818@chaz.gmail.com \
--to=stephane.chazelas@gmail.com \
--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).