Gnus development mailing list
 help / color / mirror / Atom feed
From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: Abandoning the concept of groups as a storage medium?
Date: Tue, 28 Apr 2009 10:56:39 +0200	[thread overview]
Message-ID: <m2prex2m2g.fsf@randomsample.de> (raw)
In-Reply-To: <m24owdoxpm.fsf@tnuctip.rychter.com> (Jan Rychter's message of "Sat, 25 Apr 2009 12:05:09 +0200")

Jan Rychter <jan@rychter.com> writes:
> Then I discovered mairix and nnmairix. They are close to what I need,
> but there is the issue of flag propagation, which nnmairix doesn't do
> for an NNML spool.

I have fixed this. I'll send you a patch soon, but I want to test this a
bit further. nnml is tricky, because it can save marks in .newsrc.eld as
well as the .marks files.

However, mairix won't know anything about marks from nnml spools,
meaning you won't be able to search for ticked/read/replied
articles. This can only be fixed within mairix, but since I've never got
any reaction from the maintainer about the maildir patches, I'm not
terribly motivated to work on this feature.

[...]
> I want to be able to set flags and tags on *any* E-mail message
> *anywhere*, not just in the "real group it belongs to". I don't want
> my "groups" to have anything to do with the way my messages are
> stored. E-mail should be stored in a key/value store with metadata
> copied and indexed separately.
>
> The problem I see with Gnus is that it is designed around a central
> concept of a mail backend which exposes groups. 

Yes, but I don't see this as a restriction for what you would like to
have. Gnus can handle "dynamic" groups, where the contents changes all
the time, although it requires a lot of work to get right. As you say,
nnmairix comes pretty close, and it strictly works with the Gnus group
back end API. My main problem with maintaining nnmairix is that the back
ends behave differently, especially when it comes to marks and unread
count.

> The registry, if I understand correctly, is a workaround for some of
> the problems people encountered with this approach.
>
> Is there any way to achieve what I want with Gnus? Is anybody working on
> something of the kind? What would be the possible approaches?

We just had this discussion, and Ted raised some interesting points
regarding the registry and how it could be extended, and I agree with
him.

I think the registry should save all important headers of a message, and
maybe also some MIME information, like attachment names. Of course, as
Ted also said, this information can't be saved anymore in plain text
files like gnus.registry.eld, but needs some kind of external database
back end.

We could then add a back end which can create virtual groups based on
registry information. One could extend nnir to do that, but I'd vote for
creating a completely new one.

However, full text search is another matter entirely. This simply cannot
be done in Emacs Lisp.

-David



  reply	other threads:[~2009-04-28  8:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-25 10:05 Jan Rychter
2009-04-28  8:56 ` David Engster [this message]
2009-04-29 10:58   ` David Engster
2009-04-30 19:27   ` Ted Zlatanov
2009-05-04 11:07     ` David Engster
2009-05-08 18:18       ` 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=m2prex2m2g.fsf@randomsample.de \
    --to=deng@randomsample.de \
    --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).