From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: emulating mozilla's Label command
Date: Thu, 15 Apr 2004 15:40:54 -0400 [thread overview]
Message-ID: <4nk70hav21.fsf@b2-25-3.bwh.harvard.edu> (raw)
In-Reply-To: <m2smf7bsh4.fsf@catbert.dok.org> (Chris Green's message of "Tue, 13 Apr 2004 15:14:31 -0400")
On Tue, 13 Apr 2004, cmg@dok.org wrote:
> I glanced at the registry and it seems separating out the parent
> threading functions from what directories the registry actually
> watches might be desirable.
I don't understand, sorry.
> My thinking there is I'd want to watch every single folder for
> labeling.It doesn't matter much to me since I don't split much
> within gnus.
>
> Rough outline of what needs to be done:
> insert label(s) in registry
store label list:
(gnus-registry-store-extra-entry id 'label label-value-list)
fetch label list:
(gnus-registry-fetch-extra id 'label)
> allow display of labels outside of *Summary*
See above.
> label commands for *Summary*/*Article*
I don't think there's any letters left :) Any suggestions are
welcome. Maybe M-l?
> allow display of labels in *Summary*
Probably doable with a user display function. I don't know much about
that side of Gnus.
> It looks like the registry cache's enough to make the display of
> labels straight from the registry easy. Would the searching of the
> registry for all things having a "label" data be prohibitive?
Yes, but why would you? You just need to look up the article of
interest by message ID.
Ted
next prev parent reply other threads:[~2004-04-15 19:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 14:02 Chris Green
2004-04-08 15:59 ` Wes Hardaker
2004-04-10 10:40 ` Sacha Chua
2004-04-10 14:14 ` Wes Hardaker
2004-04-08 21:29 ` Simon Josefsson
2004-04-12 15:03 ` Ted Zlatanov
2004-04-12 16:46 ` Kai Grossjohann
2004-04-13 15:30 ` Ted Zlatanov
2004-04-13 19:14 ` Chris Green
2004-04-15 19:40 ` Ted Zlatanov [this message]
2004-04-15 20:01 ` Chris Green
2004-04-16 14:53 ` Ted Zlatanov
2004-04-16 16:30 ` Chris Green
2004-04-16 20:10 ` 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=4nk70hav21.fsf@b2-25-3.bwh.harvard.edu \
--to=tzz@lifelogs.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).