From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: too easy to quit emacs without proper saving of gnus files
Date: Sat, 05 Mar 2011 11:39:05 +0100 [thread overview]
Message-ID: <m362rx97hy.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87ipvxlv7u.fsf@randomsample.de>
David Engster <deng@randomsample.de> writes:
> 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.
I'm slightly wary of adding stuff to `kill-emacs-hook', since if you do
something wrong there, then you can't ever kill Emacs...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2011-03-05 10:39 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
2011-03-05 10:39 ` Lars Magne Ingebrigtsen [this message]
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=m362rx97hy.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).