all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34093@debbugs.gnu.org, leonard@lausen.nl
Subject: bug#34093: auto-save prevents quitting emacs on read-only filesystem
Date: Tue, 18 Aug 2020 18:44:06 +0000	[thread overview]
Message-ID: <CADwFkmmPHaA2y2wsKuQjysiD+ua3Bg+=tvaLS3mf4maa88qUiQ@mail.gmail.com> (raw)
In-Reply-To: <83mu2rerz6.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

> Thanks, but is a single warning really enough?  What if the situation
> is slightly different, in that the user could somehow resolve the
> problem -- should we perhaps prompt the user whether to retry or
> ignore the error?

Is it worth it?  The bug will presumably trigger only under rare
circumstances such as serious misconfiguration by the user or serious
system failure ($HOME remounted as read-only sounds fairly exceptional).
And the consequence is that the user will miss out on a very minor
convenience feature.

OTOH, I'm not a regular user of savehist-mode, so I'm not sure.  Maybe
people really depend on saving their minibuffer history between
sessions...  But even then, they would be no worse off with my proposed
fix than they are now.

Best regards,
Stefan Kangas





  reply	other threads:[~2020-08-18 18:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16  3:01 bug#34093: auto-save prevents quitting emacs on read-only filesystem Leonard Lausen
2020-08-18 17:52 ` Stefan Kangas
2020-08-18 18:20   ` Eli Zaretskii
2020-08-18 18:44     ` Stefan Kangas [this message]
2021-05-11 13:58       ` Lars Ingebrigtsen
2021-05-12  4:04         ` Richard Stallman

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='CADwFkmmPHaA2y2wsKuQjysiD+ua3Bg+=tvaLS3mf4maa88qUiQ@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=34093@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=leonard@lausen.nl \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.