all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Matthieu Moy <Matthieu.Moy@ormelune.imag.fr>
Cc: emacs-devel@gnu.org
Subject: Re: saveplace prevent me from quitting if ~/.emacs-places is write-protected
Date: Sat, 08 Mar 2003 13:19:49 +0100	[thread overview]
Message-ID: <vpqk7facaoq.fsf@imag.fr> (raw)
In-Reply-To: <E18rNhf-0008GH-00@fencepost.gnu.org> (Richard Stallman's message of "Fri, 07 Mar 2003 14:40:23 -0500")

Richard Stallman <rms@gnu.org> writes:

>     Assuming we can reproduce this, what is the right solution?  Is there
>     already a policy for how Emacs should behave when there's an error
>     saving a file at exit time, and that file is managed by Emacs (i.e.,
>     is not just a regular file visited for editing by the user)?
>
> It may as well ignore the error.  I don't see a better alternative.
> The user wants to exit and should not be impeded.

I don't  remember if  it is  possible to catch  an (error  "...") with
something  like (condition-case  ...), but  if it  is, then,  the best
solution would be to catch it, and then ask the user :

"Some errors occured during saving. Quit anyway ? (y/n)"

A bit like  what happens when you refuse to  save a buffer. ("Modified
buffers exist, exit anyway ?") 

Note that this would cover any kind of errors during saving.

Or we can consider that my configuration is an exotic one and say that
the bug is not serious enough ...

-- 
Matthieu

  reply	other threads:[~2003-03-08 12:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-04 17:30 saveplace prevent me from quitting if ~/.emacs-places is write-protected matthieu.moy
2003-03-05 20:47 ` Richard Stallman
2003-03-06  2:48   ` Karl Fogel
2003-03-06  7:14     ` Matthieu Moy
2003-03-07 19:40     ` Richard Stallman
2003-03-08 12:19       ` Matthieu Moy [this message]
     [not found] <mailman.2738.1046800682.21513.bug-gnu-emacs@gnu.org>
2003-03-05 19:04 ` Kevin Rodgers

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=vpqk7facaoq.fsf@imag.fr \
    --to=matthieu.moy@ormelune.imag.fr \
    --cc=emacs-devel@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 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.