From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs-devel@gnu.org
Subject: Re: Improve reporting of I/O, access errors for Emacs
Date: Tue, 17 Sep 2019 19:25:21 -0700 [thread overview]
Message-ID: <e6c828ce-62ba-baef-9644-8d9ed46cfdcc@cs.ucla.edu> (raw)
In-Reply-To: <8336h01wa7.fsf@gnu.org>
On 9/13/19 12:37 AM, Eli Zaretskii wrote:
> My point was that in the
> code of the primitive itself, we have all the information to decide
> whether or not to signal an error; but on lower levels, we don't have
> enough context to make such decisions, so we should only return an
> error indication from those lower levels.
OK, thanks for clarifying. I reworked the patch along the lines that you
suggested, and installed it into master.
next prev parent reply other threads:[~2019-09-18 2:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 8:22 Improve reporting of I/O, access errors for Emacs Paul Eggert
2019-09-12 18:04 ` Eli Zaretskii
2019-09-12 18:27 ` Paul Eggert
2019-09-12 19:34 ` Eli Zaretskii
2019-09-12 20:32 ` Paul Eggert
2019-09-13 7:37 ` Eli Zaretskii
2019-09-18 2:25 ` Paul Eggert [this message]
2019-09-18 9:50 ` Richard Copley
2019-09-16 11:07 ` Richard Copley
2019-09-16 14:53 ` Eli Zaretskii
2019-09-16 18:11 ` Richard Copley
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=e6c828ce-62ba-baef-9644-8d9ed46cfdcc@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=Emacs-devel@gnu.org \
--cc=eliz@gnu.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.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).