From: Dave Abrahams <dave@boostpro.com>
To: ding@gnus.org
Subject: Re: Where is gnus-simplify-group-name?
Date: Mon, 10 Oct 2011 18:53:11 -0400 [thread overview]
Message-ID: <m2wrcch31k.fsf@pluto.luannocracy.com> (raw)
In-Reply-To: <87mxd9jlut.fsf@zelenka.enovance.com>
on Mon Oct 10 2011, Julien Danjou <julien-AT-danjou.info> wrote:
> On Sat, Oct 08 2011, Dave Abrahams wrote:
>
>> I was writing some code that opened groups today and I was disturbed to
>> find that Gnus would do something different if I spelled the same group
>> in two different ways. My `gnus-select-method' is
>>
>> (nnimap "LocalIMAP"
>> (nnimap-address "localhost") (nnimap-user "dave")
>> (nnimap-server-port 9143) (nnimap-stream network))
>
> IIUC, this is due to the primary/secondary methods mechanism, which add
> a prefix when methods are secondaries.
>
> Last time we spoke about that, the consensus was to remove this
> mechanism so there's not two ways of naming groups like you point out.
I think there still will be two ways, as long as we're allowing people
sometimes to type "INBOX" instead of "nnimap+imap.foo.com:INBOX". And
I think we want to support that, right?
> But we never started doing it mainly because it can be tricky to not
> no break working setups.
>
> Maybe that's time to do it.
Providing the group name normalization function, and using it where it
counts, would be less disruptive. And I predict you'll want one even if
you do get rid of the primary/secondary distinction. However, if you're
up for a big rewrite, all I can say is, "go for it!" :-)
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
next prev parent reply other threads:[~2011-10-10 22:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-08 0:47 Dave Abrahams
2011-10-10 8:23 ` Julien Danjou
2011-10-10 22:53 ` Dave Abrahams [this message]
2011-10-11 8:24 ` Julien Danjou
2011-10-11 12:16 ` Dave Abrahams
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=m2wrcch31k.fsf@pluto.luannocracy.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).