From: Dave Abrahams <dave@boostpro.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: Auto-slave gnusae?
Date: Mon, 08 Feb 2016 06:27:34 -0800 [thread overview]
Message-ID: <m2lh6v6zvt.fsf@boostpro.com> (raw)
In-Reply-To: <87fux3g4p2.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 08 Feb 2016 16:18:49 +1100")
on Sun Feb 07 2016, Lars Ingebrigtsen <larsi-AT-gnus.org> wrote:
> Dave Abrahams <dave@boostpro.com> writes:
>
>>> Besides, I'm not sure we could reliably detect this situation.
>>
>> Look for a dribble file or something similar?
>
> A dribble file might be an indication...
>
> But anyway, I'm not sure that this is something that should be done.
> I'm often ssh-ing in from somewhere to read news on my home machine,
> and starting a Gnus works just fine, even if one is already running.
> You just ... have to be careful not to let the older one overwrite the
> state created by the new one.
Someone like you (meaning, just you) knows exactly how to do that
because they're familiar with all of the state management Gnus does. I
think “ordinary users” shouldn't be expected to figure that out.
> But I guess that's what's Gnus slaves do, anyway... But will the
> "other" running Gnus detect the slave data automatically without doing
> anything?
Only Lars can say!
--
-Dave
next prev parent reply other threads:[~2016-02-08 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 0:33 Dave Abrahams
2016-02-06 5:54 ` Lars Ingebrigtsen
2016-02-07 15:57 ` Dave Abrahams
2016-02-08 5:18 ` Lars Ingebrigtsen
2016-02-08 14:27 ` Dave Abrahams [this message]
2016-02-09 4:16 ` Lars Ingebrigtsen
2016-02-10 20:53 ` Dave Abrahams
2016-02-08 17:27 ` Andreas Schwab
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=m2lh6v6zvt.fsf@boostpro.com \
--to=dave@boostpro.com \
--cc=ding@gnus.org \
--cc=larsi@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).