From: Stefan Kangas <stefan@marxist.se>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 34338@debbugs.gnu.org
Subject: bug#34338: 26.1; delete-file return codes and failures
Date: Wed, 9 Oct 2019 13:48:37 +0200 [thread overview]
Message-ID: <CADwFkmmhRAptdebg1DC5Xg9v2Xw6NagYKgL2fVBP7peqPJjaqw@mail.gmail.com> (raw)
In-Reply-To: <20190205214737.vswyk7sfmgkliv7v@E15-2016.optimum.net>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
Boruch Baum <boruch_baum@gmx.com> writes:
> On 2019-02-07 05:36, Eli Zaretskii wrote:
>> > Date: Wed, 6 Feb 2019 16:02:11 -0500
>> > From: Boruch Baum <boruch_baum@gmx.com>
>> >
>> > So the messages are unique, but not clear.
>>
>> The description comes from the error code returned by a C library
>> function. Doing more than that would mean additional checks, which
>> will be expensive and probably non-portable. I don't see the benefit.
>> I mean, why isn't "Operation not permitted" enough, it tells you that
>> your user is not permitted to do that, which is clear enough IMO.
>
> Reasonable.
It seems to me from the discussion like we don't want to make the proposed
change, since it has an unclear benefit and is backwards
incompatible.
Is there is something I'm missing here? Otherwise, I think we can close
this as wontfix.
Best regards,
Stefan Kangas
[-- Attachment #2: Type: text/html, Size: 1161 bytes --]
next prev parent reply other threads:[~2019-10-09 11:48 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 [this message]
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
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=CADwFkmmhRAptdebg1DC5Xg9v2Xw6NagYKgL2fVBP7peqPJjaqw@mail.gmail.com \
--to=stefan@marxist.se \
--cc=34338@debbugs.gnu.org \
--cc=boruch_baum@gmx.com \
/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).