From: dick.r.chiang@gmail.com
To: Lars Ingebrigtsen <larsi@gnus.org>,
eric@ericabrahamsen.net, schwab@linux-m68k.org
Cc: 37926@debbugs.gnu.org, dick.r.chiang@gmail.com
Subject: bug#37926: [PATCH] Unify Gnus select methods
Date: Mon, 28 Oct 2019 09:54:02 -0400 [thread overview]
Message-ID: <87sgndht6t.fsf@dick> (raw)
In-Reply-To: <87imo9azh4.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 28 Oct 2019 12:20:07 +0100")
The first reaction of Andreas Schwab was also to ensure the primary remains
unprefixed. I am not privy to the history of this sensitivity, but I assume
there is one, and I trust you'll tell me why the patch breaks this.
My current understanding is that `gnus-select-method` and
`gnus-secondary-select-methods` remain appropriately defined if someone only
specifies the unified `gnus-select-methods`.
Under the existing code, I assume changing one's gnus-select-method wreaks havoc on a
dot.newsrc.eld that assumes some other non-nnnil gnus-select-method. This patch does
nothing to alleviate that.
next prev parent reply other threads:[~2019-10-28 13:54 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sgndht6t.fsf@dick \
--to=dick.r.chiang@gmail.com \
--cc=37926@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=larsi@gnus.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.