From: Colin Rafferty <craffert@ml.com>
Subject: Re: saving gnus .newsrc.eld
Date: 25 Sep 1997 10:01:54 -0400 [thread overview]
Message-ID: <ocru3f95w6l.fsf@ml.com> (raw)
In-Reply-To: Mark Hovey's message of "25 Sep 1997 07:01:43 +0000"
Mark Hovey writes:
> If I run Gnus, then forget about it and kill emacs later
> without ever quitting Gnus, then save-buffers-kill-emacs (C-x C-c) asks
> me if I want to save .newsrc-dribble. At this point I have no good
> option except to hit C-g, switch to the *Group buffer, and quit Gnus.
> Is there some variable I can set so that Gnus will automatically save
> itself when I leave a Gnus-controlled buffer, or something of that
> sort? In general, is there a good solution to this?
While it is very difficult to recognize leaving a Gnus buffer, there are
ways of coming close.
I have the following in my .gnus.el:
(add-hook 'gnus-summary-exit-hook 'gnus-dribble-save)
You could change it from gnus-dribble-save to gnus-group-save-newsrc,
but I don't think the time spent is worth it.
> My current solution is to redefine save-buffers-kill-emacs in my .gnus
> file by adding the lines
> (setq gnus-interactive-exit nil)
> (gnus-group-exit)
> right after the interactive statement.
> Anybody have anything better to do?
A better choice might be to put something on `kill-emacs-query-functions'.
Untested code follows:
(add-hook 'kill-emacs-query-functions
'(lambda ()
(let ((gnus-interactive-exit nil))
(gnus-group-exit)
nil))) ; this nil is important, see doc for k-e-q-f
--
export-a-crypto-system, see: http://www.dcs.ex.ac.uk/~aba/rsa/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
prev parent reply other threads:[~1997-09-25 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-25 7:01 Mark Hovey
1997-09-25 14:01 ` Colin Rafferty [this message]
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=ocru3f95w6l.fsf@ml.com \
--to=craffert@ml.com \
/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).