Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Saving .newsrc upon *Summary* exit
Date: Tue, 24 Jul 2001 14:18:15 -0400	[thread overview]
Message-ID: <m3elr6chs2.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <2nr8v65i4g.fsf@piglet.jia.vnet> (ShengHuo ZHU's message of "Tue, 24 Jul 2001 10:53:03 -0700")

ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> prj@po.cwru.edu (Paul Jarc) writes:
>> Is it appropriate to add gnus-group-save-newsrc to
>> gnus-summary-exit-hook?  Or is that hook called at a bad time for
>> saving?
> 
> I think it is OK. If not, please post your solution.

I haven't had any problems so far.  Now, since I've gotten into the
habit of not leaving *Summary* buffers hanging around, I can leave one
Gnus running and safely run a second one in a second Emacs (on the
same machine, using the same account, .emacs, etc.).  The first one
will have saved my newsrc, so the second one will see something
consistent and up-to-date when it starts, and when I get back to the
first one, I immediately quit and restart Gnus to pick up the changes
made by the second one.  Quitting won't clobber those changes because
the first Gnus thinks newsrc is already saved.


paul


  reply	other threads:[~2001-07-24 18:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-15 19:47 Paul Jarc
2001-07-24 16:17 ` Colin Rafferty
2001-07-24 17:53 ` ShengHuo ZHU
2001-07-24 18:18   ` Paul Jarc [this message]
2001-07-24 21:55     ` Kai Großjohann
2001-07-24 22:37       ` Paul Jarc
2001-07-25  1:14         ` David S. Goldberg
2001-07-25  8:21         ` Kai Großjohann
2001-07-24 18:39   ` Stainless Steel Rat

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=m3elr6chs2.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    /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).