From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: emulating mozilla's Label command
Date: Tue, 13 Apr 2004 11:30:17 -0400 [thread overview]
Message-ID: <4nad1fq4ja.fsf@b2-25-3.bwh.harvard.edu> (raw)
In-Reply-To: <87n05hnny5.fsf@emptyhost.emptydomain.de>
On Mon, 12 Apr 2004, kai@emptyhost.emptydomain.de wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> 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.
>
> Cool. But what about people who wish to truncate their registry at
> a certain length? I guess people who use the registry for splitting
> with the parent might like to do that.
We can make it so message IDs with extra data, e.g. spam
registration/unregistration or labels, are always preserved. It could
even be a multiple checkbox choice, so you can keep labels but not
spam reg/unreg info if you wanted.
Adding this is pretty easy, and I just did it for extra data named
'label. If such extra data exists, the information is not deleted.
On the other hand, if people want to trim the registry by age, that's
a different function, but it's still doable. Let's see first if
there's interest in storing labels in the registry :)
Ted
next prev parent reply other threads:[~2004-04-13 15:30 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 [this message]
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=4nad1fq4ja.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).