From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: emulating mozilla's Label command
Date: Mon, 12 Apr 2004 11:03:39 -0400 [thread overview]
Message-ID: <4noepxs0fo.fsf@b2-25-3.bwh.harvard.edu> (raw)
In-Reply-To: <iluk70qgnu2.fsf@latte.josefsson.org> (Simon Josefsson's message of "Thu, 08 Apr 2004 23:29:57 +0200")
On Thu, 08 Apr 2004, jas@extundo.com wrote:
> Perhaps there are simpler solution, but your report started a
> different process in my mind: It should be easier to introduce new
> flags in Gnus. It should be possible to add user-defined flags. We
> add flags from time to time to Gnus, and the process of doing this
> is technically simple, if only you recall to update all places in
> the code. It can probably be generalized and made available as a
> user command.
I recall that when I added the spam-mark it was not a simple process,
so any sort of automation would be nice.
The gnus-registry may also help here. The registry file can be stored
anywhere (think tramp/scp to a remote server from several clients),
and is backend-neutral. Most users, I would guess, want to associate
a flag with a message ID, not with an article number. Since
arbitrary data can be stored in the registry, and lookup is very
fast, this may be a convenient solution that will allow just about any
flag to be added with a minimum amount of effort, and no backend
support is needed. Just an idea...
Ted
next prev parent reply other threads:[~2004-04-12 15:03 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 [this message]
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
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=4noepxs0fo.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).