From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] viewing threads oldest-first
Date: Fri, 14 Mar 2008 11:30:58 -0700 [thread overview]
Message-ID: <1205517246-sup-9385@south> (raw)
In-Reply-To: <1205506459-sup-9596@chain.local>
Reformatted excerpts from Matt Liggett's message of 2008-03-14:
> In every mailer I've used before my gmail days, I always viewed my
> email oldest first, especially in any inboxen. Is there a config
> option (I don't see a keyboard shortcut) to do this?
There's no option for this. I don't think it makes quite as much sense
in a world where mailboxes can be arbitrarily large (a Sup mailbox is a
search result across your entire set of email) and where loading is
fairly slow.
But there's no technical reason why this couldn't happen, and other
people have asked for it before, so I'd be willing to add it.
> As I write this, I realize that oldest-first might mean different
> things in a threaded view. Is that the oldest first message in the
> thread, or the oldest last message?
Currently a thread's timestamp is the timestamp of the most recent
message in it, and I would be loathe to change that.
> Do I generally want inbox threads sorted by unread messages (that is,
> ordering by oldest unread message in each thread)?
That would be interesting, but unfortunately is not feasible in Sup. The
index currently knows nothing about threads, just individual messages,
so we can only sort by properties of messages, not by properties of
threads.
The way we build a threadset now is we search for messages which meet
some search criterea, then we build a thread for each message.
> In the meantime, can anyone give me a pointer as to where in the code
> I might start digging regarding such a feature?
Normally I would want a hook, but since there are really only two
options that are technically feasible now, I would add a config variable
called "sort_oldest_first" or something like that. It will follow a
very similar codepath to thread_by_subj (so grep for that): it should be
initialized in sup.rb for new configurations, passed into a ThreadSet
constructor from ThreadIndexMode#initialize_threads, and passed into
Index#each_id_by_date, where it will change the query we send to Ferret.
Finally, ThreadIndexMode#update (which handles the UI component of
sorting) has got to respect this variable.
> I tried mutt+mairix for awhile, but it was kludgy and slow. sup looks
> like it might be the best of both worlds, enabling me to deal with a
> large volume of mail and still giving me the tagging and search that I
> love from gmail.
Yep, you're my target audience. :)
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-03-14 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 15:01 Matt Liggett
2008-03-14 18:30 ` 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=1205517246-sup-9385@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