Gnus development mailing list
 help / color / mirror / Atom feed
From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: gmail-like mail backend?
Date: 11 Feb 2005 13:10:03 -0500	[thread overview]
Message-ID: <4nu0ojhssk.fsf@lifelogs.com> (raw)
In-Reply-To: <87zmyc57n6.fsf@koldfront.dk> (Adam =?iso-8859-1?Q?Sj=F8gren'?= =?iso-8859-1?Q?s?= message of "Fri, 11 Feb 2005 00:15:25 +0100")

On Fri, 11 Feb 2005, asjo@koldfront.dk wrote:

On 10 Feb 2005 12:48:56 -0500, Ted wrote:

>> Look at my previous posts in ding on "message labels" that someone
>> was going to implement.
> 
> (I think I was babbling about that, but I haven't gotten around to
> trying to actually do something. Lack of time and knowledge on my
> part).

No rush, Miles' proposal may work together with yours though.

>> This can be done with the registry - just associate the labels as
>> extra data with the message ID, and you can find the message by the
>> message ID.
> 
> How would this work in conjunction with setting
> gnus-registry-max-entries to something besides nil?
> 
> (I'd like to forget information about old spam, but I'd never ever
> want to forget about labels I have assigned).

I can fix gnus-registry-trim so it knows certain kinds of extra data
mean the article should not be expired when the registry is trimmed.

If you mean the article label should stay even after the article is
deleted, that can be arranged too.
gnus-registry-trim-articles-without-groups controls this right now.  I
actually fixed a bug related to this right now, as well.

Ted



  reply	other threads:[~2005-02-11 18:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09  8:08 Miles Bader
2005-02-09 16:15 ` David Abrahams
2005-02-10 17:48 ` Ted Zlatanov
2005-02-10 23:15   ` Adam Sjøgren
2005-02-11 18:10     ` Ted Zlatanov [this message]
2005-02-15 18:03 ` Ian Soboroff

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=4nu0ojhssk.fsf@lifelogs.com \
    --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).