From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Minor maildir change
Date: Wed, 19 Sep 2007 08:59:58 -0700 [thread overview]
Message-ID: <1190216731-sup-3428@south> (raw)
In-Reply-To: <20070916181936.GA5332@die.therning.org>
Excerpts from Magnus Therning's message of Sun Sep 16 11:19:36 -0700 2007:
> 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.
What do you mean? For a new, unseen message, the initial set of label is
uniquely determined by the source's default labels, unioned with
whatever state (read/unread, flagged, etc) we carry over from the
source. This is what Source#each does.
Now sup-sync has some complicated behavior that does involve the labels
on the index, but that has to do with situations where the message
already exists in the index, or the message state exists in a dumpfile
somewhere, and you're resolving the two potentially different label
sets.
> 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.)
That is a hack to avoid having the mbox code read the header twice, one
for the labels and again for the actual header contents. Since I'm
planning on reworking mbox anyways (to avoid keeping the file pointer
always open, and to clean up the interface between loader and
ssh-loader), so I'll try and think of a better way to do this. There
might not be.
In the mean time, I'll remove the second half of that statement, which
should make everyone happy.
> - 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.
Not sure what you mean by "actual sets", but I think this is pretty much
the way Sup works now.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2007-09-19 15:59 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
2007-09-19 15:59 ` William Morgan [this message]
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=1190216731-sup-3428@south \
--to=wmorgan-sup@masanjin.net \
/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