From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: message registry for Gnus
Date: Fri, 07 Feb 2003 17:45:12 -0500 [thread overview]
Message-ID: <m3smuz7ls7.fsf@heechee.beld.net> (raw)
In-Reply-To: <m33cmz94qa.fsf@quimbies.gnus.org>
On Fri, 07 Feb 2003, larsi@gnus.org wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> (gnus-group-full-name group (gnus-find-method-for-group group))
>>
>> will find "nnml+private:mail" even though the spooling is being
>> done for "nnimap+server.name.com:mail".
>
> `gnus-find-method-for-group' only works (reliably) for Gnus groups
> names, and not for server group names. That is, it works for
> prefixed group names, which is what you're trying to find. :-)
Argh.
> So you can't use that in the back end. You have to do it the other
> way around, and feed `gnus-group-prefixed-name' the select method in
> some manner.
I'm not sure how to get the select method though. I thought it would
be gnus-current-select-method, but that's always the nnml method, even
when nnimap splitting is done! I think there's something with the
binding of that variable, and my Lisp is hardly good enough to figure
out those closures or whatever is going on.
So instead I brute-forced gnus-request-scan to set the new variable
gnus-internal-registry-spool-current-method to gnus-command-method
before a request-scan operation, and then gnus-registry.el uses that
variable. It works very nicely, and I'm happy with the registry now,
but please take a look and let me know if I'm missing something
obvious as usual.
I named the variable gnus-internal-registry-spool-current-method, I
hope that's OK with everyone. It's certainly long enough that you
can't miss it :)
Ted
next prev parent reply other threads:[~2003-02-07 22:45 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 17:15 Ted Zlatanov
2003-02-01 10:28 ` Kai Großjohann
2003-02-01 16:39 ` Lars Magne Ingebrigtsen
2003-02-01 20:20 ` Ted Zlatanov
2003-02-02 12:10 ` Lars Magne Ingebrigtsen
2003-02-02 15:14 ` Ted Zlatanov
2003-02-07 12:20 ` Lars Magne Ingebrigtsen
2003-02-02 16:54 ` Kai Großjohann
2003-02-03 20:47 ` Ted Zlatanov
2003-02-04 15:25 ` Simon Josefsson
2003-02-04 19:57 ` Ted Zlatanov
2003-02-05 5:56 ` Simon Josefsson
2003-02-07 20:43 ` Ted Zlatanov
2003-02-02 0:35 ` Raja R Harinath
2003-02-02 1:30 ` Ted Zlatanov
2003-02-02 17:15 ` Raja R Harinath
2003-02-07 20:48 ` Ted Zlatanov
2003-02-07 21:10 ` Lars Magne Ingebrigtsen
2003-02-07 22:45 ` Ted Zlatanov [this message]
2003-02-08 20:39 ` Lars Magne Ingebrigtsen
2003-02-21 19:05 ` Ted Zlatanov
2003-02-22 22:20 ` Lars Magne Ingebrigtsen
2003-02-24 15:36 ` Ted Zlatanov
2003-02-24 16:58 ` Andreas Fuchs
2006-09-28 13:20 ` gnus-registry: alist-to-hashtable, hashtable-to-alist (was: message registry for Gnus) Reiner Steib
2006-09-28 14:21 ` gnus-registry: alist-to-hashtable, hashtable-to-alist Ted Zlatanov
2006-09-28 16:03 ` CHENG Gao
2006-09-28 16:58 ` Reiner Steib
2003-02-24 21:57 ` message registry for Gnus Lars Magne Ingebrigtsen
2003-02-24 22:14 ` Ted Zlatanov
2003-02-25 7:19 ` Kai Großjohann
2003-02-25 17:57 ` Ted Zlatanov
2003-03-28 9:20 ` Ted Zlatanov
2003-04-16 20:35 ` Ted Zlatanov
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=m3smuz7ls7.fsf@heechee.beld.net \
--to=tzz@lifelogs.com \
/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).