From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Cc: Martin Tournoij <martin@arp242.net>
Subject: Re: Any way to allow clobbering empty files when noclobber is set?
Date: Thu, 4 Jun 2020 13:26:48 +0100 (BST) [thread overview]
Message-ID: <217711433.430038.1591273608743@mail2.virginmedia.com> (raw)
In-Reply-To: <CAN=4vMq0iRVjcSDOTSc-tzqK1Uq1X3pa83s9ZT=1auZBxfXxkw@mail.gmail.com>
> On 04 June 2020 at 13:20 Roman Perepelitsa <roman.perepelitsa@gmail.com> wrote:
> On Thu, Jun 4, 2020 at 11:43 AM Peter Stephenson
> <p.w.stephenson@ntlworld.com> wrote:
> > At the least we'd need to open the existing file without
> > truncating (then either close it or leave it open for writing
> > if it was already empty).
>
> If you mean opening the file with O_APPEND, this could result in
> unexpected file content.
>
> I should also note that the existing no_clobber option can be used to
> implement file locks.
>
> Regardless of what gets decided w.r.t. no-clobber extensions, I hope
> this would keep working.
Indeed, this is the sort of thing backing up my thinking that we keep
the clobbering open function call exactly as it now is if we add the
extension for empty files.
pws
next prev parent reply other threads:[~2020-06-04 12:27 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
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 [this message]
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=217711433.430038.1591273608743@mail2.virginmedia.com \
--to=p.w.stephenson@ntlworld.com \
--cc=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).