From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel@rubyforge.org
Subject: Re: [sup-devel] [Heliotrope/Turnsole] How to use IMAP?
Date: Tue, 28 Feb 2012 17:11:56 -0800 [thread overview]
Message-ID: <1330468308-turnsole-43856@terminus-est> (raw)
In-Reply-To: <1330333805-sup-1287@stapelberg.de>
Excerpts from Michael Stapelberg's message of 2012-02-27 01:16:43 -0800:
> 1) It will completely ignore it.
Correct. This is the problem that the ctime solution is meant to address.
> So, let’s stick to my above example of the spam email and let’s assume
> that you changed the code to use ctimes. The spam mail arrives, its
> ctime is new, it gets picked up into my index. To my understanding, I
> now need to reorder. I have multiple questions:
>
> 1) What are the immediate consequences? Where will this email appear in my
> inbox, when my inbox contains 5 emails. Always at the top? Bottom? You
> mentioned I can see the effect when paging. Can you elaborate please?
Heliotrope will return it as the first result, since it returns messages
in LIFO order.
Currently Turnsole currently re-sorts all messages returned by sort by
date, and so it will place it at the bottom. This is also where the
pagination issues may come from. Maybe it would be less confusing for it
to stick to search result order.
> 2) How do I know when I have to reorder?
You have to reorder whenever you want Heliotrope to return messages in
Date header order instead of in LIFO order. I think this will typically
happen when you import a couple batches of preexisting mail, and not
when you're adding new mail.
--
William <wmorgan@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2012-02-29 1:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-08 22:48 Michael Stapelberg
2012-01-10 0:40 ` William Morgan
2012-02-06 20:45 ` Michael Stapelberg
2012-02-06 23:08 ` Matthieu Rakotojaona
2012-02-06 23:46 ` Michael Stapelberg
2012-02-07 12:27 ` Matthieu Rakotojaona
2012-02-07 19:11 ` Michael Stapelberg
2012-02-07 21:54 ` Matthieu Rakotojaona
2012-02-13 6:16 ` William Morgan
2012-02-22 21:39 ` Michael Stapelberg
2012-02-23 6:25 ` William Morgan
2012-02-23 11:24 ` Michael Stapelberg
2012-02-25 6:35 ` William Morgan
2012-02-27 9:16 ` Michael Stapelberg
2012-02-29 1:11 ` William Morgan [this message]
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=1330468308-turnsole-43856@terminus-est \
--to=wmorgan-sup@masanjin.net \
--cc=sup-devel@rubyforge.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