From: Eli Zaretskii <eliz@gnu.org>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 34338@debbugs.gnu.org, stefan@marxist.se
Subject: bug#34338: 26.1; delete-file return codes and failures
Date: Fri, 01 Nov 2019 11:55:15 +0200 [thread overview]
Message-ID: <838sozncos.fsf@gnu.org> (raw)
In-Reply-To: <20191101093423.q6qm3eijb6ilrkpg@E15-2016.optimum.net> (message from Boruch Baum on Fri, 1 Nov 2019 05:34:23 -0400)
> Date: Fri, 1 Nov 2019 05:34:23 -0400
> From: Boruch Baum <boruch_baum@gmx.com>
> Cc: stefan@marxist.se, 34338@debbugs.gnu.org
>
> On 2019-10-31 16:32, Eli Zaretskii wrote:
> > The current implementation basically is a moral equivalent of "rm -f".
> > It also is biased towards interactive usage, where the return value is
> > not very important.
> >
> > Does it answer your question?
>
> Not satisfactorily.
Actually, from what you wrote, it follows that it did answer your
question, you just disagree that delete-file should have been coded to
work as it does.
Please note that I didn't try to justify its behavior, only to explain
its rationale, in response to your question "If it didn't matter, why
waste your time attempting the deletion?" IOW, there certainly _are_
valid use cases where "it doesn't matter", and the fact that "rm -f"
exists is an evidence.
next prev parent reply other threads:[~2019-11-01 9:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 21:47 bug#34338: 26.1; delete-file return codes and failures Boruch Baum
2019-02-06 8:24 ` Michael Albinus
2019-02-06 9:35 ` Boruch Baum
2019-02-06 16:19 ` Eli Zaretskii
2019-02-06 21:02 ` Boruch Baum
2019-02-07 3:36 ` Eli Zaretskii
2019-02-07 5:14 ` Boruch Baum
2019-10-09 11:48 ` Stefan Kangas
2019-10-30 21:07 ` Stefan Kangas
2019-10-30 22:22 ` Boruch Baum
2019-10-30 22:52 ` Stefan Kangas
2019-10-31 1:33 ` Boruch Baum
2019-10-31 14:32 ` Eli Zaretskii
2019-11-01 9:34 ` Boruch Baum
2019-11-01 9:55 ` Eli Zaretskii [this message]
2019-11-08 13:00 ` Stefan Kangas
2019-10-31 14:01 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838sozncos.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34338@debbugs.gnu.org \
--cc=boruch_baum@gmx.com \
--cc=stefan@marxist.se \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).