unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: michael.albinus@gmx.de, emacs-devel@gnu.org
Subject: Re: master 9dc306b1: Improve reporting of I/O, access errors
Date: Fri, 20 Sep 2019 08:48:08 +0300	[thread overview]
Message-ID: <83ef0btt5z.fsf@gnu.org> (raw)
In-Reply-To: <585476bd-e9f4-f622-a114-d7db6a36b06a@cs.ucla.edu> (message from Paul Eggert on Thu, 19 Sep 2019 17:21:09 -0700)

> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Thu, 19 Sep 2019 17:21:09 -0700
> Cc: emacs-devel@gnu.org
> 
> Although the jury might still be out on the 
> ancestor-directory-permissions aspect of the change (certainly on 
> MS-Windows, which reports EACCES for missing directories), surely Emacs 
> should not simply ignore I/O errors and the like.

I think the jury is still out on the latter part as well.  I, for one,
am not convinced.  Emacs is not a file- or directory-management
utility, it's an editor, so its file I/O aspects are secondary to the
primary goal of modifying files' contents.  IMO, we need to closely
watch the results of these changes, which from my POV are still
experimental, and carefully draw conclusions from the user reports.
(What's worse, these changes might significantly delay the release of
Emacs 27.1, but that ship has sailed.)

> And the permissions change has been helpful for testing

That could mean these changes should be only activated by some
build-time option, or maybe a run-time option, by default off.  It
isn't an evidence in favor of the changes being active by default, at
least not a significant evidence.



  reply	other threads:[~2019-09-20  5:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190918022442.11082.40975@vcs0.savannah.gnu.org>
     [not found] ` <20190918022444.103AC207F5@vcs0.savannah.gnu.org>
2019-09-18  7:41   ` master 9dc306b1: Improve reporting of I/O, access errors Michael Albinus
2019-09-18  7:44     ` Michael Albinus
2019-09-20  0:21     ` Paul Eggert
2019-09-20  5:48       ` Eli Zaretskii [this message]
2019-09-20 12:43       ` Michael Albinus
2019-09-20 19:05         ` Paul Eggert
2019-09-20 19:22           ` Michael Albinus

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=83ef0btt5z.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    /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).