Gnus development mailing list
 help / color / mirror / Atom feed
From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: too easy to quit emacs without proper saving of gnus files
Date: Sat, 05 Mar 2011 11:25:57 +0100	[thread overview]
Message-ID: <87ipvxlv7u.fsf@randomsample.de> (raw)
In-Reply-To: <m3ei6lamz5.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sat, 05 Mar 2011 11:19:26 +0100")

Lars Magne Ingebrigtsen writes:
> Tassilo Horn <tassilo@member.fsf.org> writes:
>
>> Yes, I also think I was queried when quitting emacs from whatever the
>> current buffer was.  But OTOH, it doesn't make a big difference if you
>> are queried to load autosave files on startup or if you are queried to
>> really quit as long as nothing's lost.
>
> You're seeing the result of this change:
>
> 	* gnus-start.el (gnus-dribble-read-file): Set
> 	buffer-save-without-query, since we always want to save the dribble
> 	file, probably.
>
> The rationale for the change was that it was pointed out that if you're
> using Gnus in an Emacs where you're also doing development, `M-x
> compile' (and friends) will constantly query you for whether to save the
> dribble file.
>
> Which is annoying.
>
> The side effect is that Emacs no longer queries you on Emacs shutdown,
> either, but...
>
> I think the new behaviour is probably better than the old one, but I'm
> not sure.  Opinions?

My suggestion would be to add a function to the kill-emacs-hook which
checks if Gnus is still running. This should be customizable, of course.

Another thing is that whenever you run 'compile', 'magit-status' etc.,
Emacs will issue "(Some special files were saved without asking)", but
doesn't say *which* files. AFAIK jidanni has already written a bug
report for that.

-David



  reply	other threads:[~2011-03-05 10:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04  9:54 jidanni
2011-03-04 11:11 ` Steinar Bang
2011-03-04 11:26   ` Tassilo Horn
2011-03-05 10:19     ` Lars Magne Ingebrigtsen
2011-03-05 10:25       ` David Engster [this message]
2011-03-05 10:39         ` Lars Magne Ingebrigtsen
2011-03-05 11:00           ` David Engster
2011-03-05 11:07       ` Julien Danjou
2011-03-05 20:03         ` Steinar Bang
2011-03-04 12:43   ` Richard Riley

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=87ipvxlv7u.fsf@randomsample.de \
    --to=deng@randomsample.de \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).