From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Saving .newsrc upon *Summary* exit
Date: Tue, 24 Jul 2001 18:37:21 -0400 [thread overview]
Message-ID: <m3y9pe9cnc.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <vafg0bmdmac.fsf@lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 24 Jul 2001 23:55:55 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> On Tue, 24 Jul 2001, Paul Jarc wrote:
>> 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.).
>
> This sounds dangerous.
Yes, it sounds that way, but I don't think it is. Anyway, I'm only
using nntp and nnmaildir, and nnmaildir tolerates even less
synchronized concurrency. So I'm not risking much.
> Why don't you do M-x gnus-slave RET for the second one?
Mostly because I didn't know about it. But reading the manual - what
happens if I run a slave, quit from it, and then run a slave again
without touching the master? Will the second slave notice the changes
from the first? With my way, it will, and that's what I want.
paul
next prev parent reply other threads:[~2001-07-24 22:37 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
2001-07-24 21:55 ` Kai Großjohann
2001-07-24 22:37 ` Paul Jarc [this message]
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=m3y9pe9cnc.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).