From: Dave Abrahams <dave@boostpro.com>
To: ding@gnus.org
Subject: Re: Auto-slave gnusae?
Date: Sun, 07 Feb 2016 07:57:29 -0800 [thread overview]
Message-ID: <m2a8ncms2e.fsf@boostpro.com> (raw)
In-Reply-To: <877fiiqt7n.fsf@gnus.org>
on Fri Feb 05 2016, Lars Ingebrigtsen <larsi-AT-gnus.org> wrote:
> Dave Abrahams <dave@boostpro.com> writes:
>
>> Just reading through the Gnus manual and noticed that we can get into
>> trouble by starting two non-slave Gnusae at once:
>> [[info:gnus#Slave%20Gnusae][info:gnus#Slave Gnusae]]
>>
>> So, shouldn't `M-x gnus' automatically dispatch to `gnus-slave' in that
>> case?
>
> There are legitimate reasons to use two separate Gnus instances -- for
> instance, if you want to "throw away" the reading results for some
> reason or other.
Sure, but that doesn't seem like a good default, does it? You could
choose it explicitly.
> Besides, I'm not sure we could reliably detect this situation.
Look for a dribble file or something similar?
--
-Dave
next prev parent reply other threads:[~2016-02-07 15:57 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 [this message]
2016-02-08 5:18 ` Lars Ingebrigtsen
2016-02-08 14:27 ` Dave Abrahams
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=m2a8ncms2e.fsf@boostpro.com \
--to=dave@boostpro.com \
--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).