From: magnus@therning.org (Magnus Therning)
Subject: [sup-talk] Minor maildir change
Date: Sun, 16 Sep 2007 19:19:36 +0100 [thread overview]
Message-ID: <20070916181936.GA5332@die.therning.org> (raw)
In-Reply-To: <1189740088-sup-6296@south>
On Thu, Sep 13, 2007 at 20:33:04 -0700, William Morgan wrote:
>Excerpts from Magnus Therning's message of Sun Sep 09 15:40:34 -0700 2007:
[..]
>> I am somewhat puzzled by the labels one receives from Maildir::each,
>> it's the default labels for the source rather than the labels of the
>> actual message.
>
>It's supposed to be both sets of labels unioned together. The source
>defines any user labels the user wants to automatically apply to new
>messages (kind of a primitive filtering), and we mix these in with the
>labels that carry over the read/unread state, etc.
This is still confusing to me.
It's also a little strange that after a message is read it doesn't
necessarily end up with the correct set of labels. Instead one has to
go to the index to get the proper set.
Another strange thing was that when using PollManager::add_messages_from
all my emails ended up being unread (according to the labels in the
message). I tracked that down to it using the value of a header
("Status") to see whether a mail was read or not. Is that something
that's used for mboxes? (I've attached a patch that removes the code.)
This adds up to some smelliness IMHO. I've done some thinking and I
think I'd like something like this:
- A source has some default labels (including :archive).
- A message is always loaded from a source so it'll get its labels from
the source iff it's a new message. If it's a known message it'll
take its labels from the database.
- Make all sets of labels actual sets.
Would this fit with the way the rest of sup works?
/M
--
Magnus Therning (OpenPGP: 0xAB4DFBA4)
magnus?therning?org Jabber: magnus?therning?gmail?com
http://therning.org/magnus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sup-lblfix.diff
Type: text/x-diff
Size: 561 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20070916/6f2933e7/attachment.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20070916/6f2933e7/attachment-0001.bin
next prev parent reply other threads:[~2007-09-16 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-09 22:40 Magnus Therning
2007-09-14 3:33 ` William Morgan
2007-09-16 18:19 ` Magnus Therning [this message]
2007-09-19 15:59 ` William Morgan
2007-09-19 22:02 ` Magnus Therning
2007-09-24 2:29 ` William Morgan
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=20070916181936.GA5332@die.therning.org \
--to=magnus@therning.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