From: Deus Max <deusmax@gmx.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>,
37926@debbugs.gnu.org, dick.r.chiang@gmail.com,
Deus Max <deusmax@gmx.com>
Subject: bug#37926: [PATCH] Unify Gnus select methods
Date: Sat, 02 Nov 2019 16:09:49 +0200 [thread overview]
Message-ID: <87zhhe74k2.fsf@dellcorei5dias.home> (raw)
In-Reply-To: <87r22qo0w8.fsf@igel.home> (Andreas Schwab's message of "Sat, 02 Nov 2019 14:36:55 +0100")
On Sat, Nov 02 2019, Andreas Schwab wrote:
> On Nov 02 2019, Deus Max wrote:
>
>> Preserving the one group of the primary selection makes it special
>
> That's the point of the primary select method.
>
Not really. Gnus started as a news reader and that was its primary use.
The other methods were added later and thus were "secondary".
Anyway, besides history, the 'primary-select-method' is arbitrary and
creates problems. Today, let's say, my primary provider is GMail, so it
is set as the 'primary-select-method'. Next month, it could be another,
perhaps switching to ProtonMail. Setting the new provider as the
'primary-select-method' creates all sorts of problems - not to mention
breaking all the org-gnus links.
Also, having different 'primary-select-method'(s) at home and office,
*confuses* org-mode !!
The purpose of unifying the select methods, is to treat them all the
same and reap the benefits. Otherwise, why change ?
next prev parent reply other threads:[~2019-11-02 14:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 20:08 bug#37926: [PATCH] Unify Gnus select methods dick.r.chiang
2019-10-26 20:21 ` Eric Abrahamsen
2019-10-26 20:59 ` Andreas Schwab
2019-11-02 13:09 ` Deus Max
2019-11-02 13:36 ` Andreas Schwab
2019-11-02 14:09 ` Deus Max [this message]
2019-11-02 14:26 ` Andreas Schwab
2019-10-27 14:01 ` Lars Ingebrigtsen
2019-10-27 18:21 ` Eric Abrahamsen
2019-11-02 13:41 ` Deus Max
2019-11-02 14:10 ` dick.r.chiang
2019-11-02 14:52 ` Deus Max
2019-11-02 21:10 ` Eric Abrahamsen
2019-10-28 3:55 ` dick.r.chiang
2019-10-28 11:20 ` Lars Ingebrigtsen
2019-10-28 13:54 ` dick.r.chiang
2019-10-28 14:03 ` Lars Ingebrigtsen
2019-10-29 6:05 ` dick.r.chiang
2019-10-29 12:04 ` Lars Ingebrigtsen
2019-10-29 16:35 ` dick.r.chiang
2019-11-17 9:56 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zhhe74k2.fsf@dellcorei5dias.home \
--to=deusmax@gmx.com \
--cc=37926@debbugs.gnu.org \
--cc=dick.r.chiang@gmail.com \
--cc=eric@ericabrahamsen.net \
--cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).