From: rlane@club.cc.cmu.edu (Rich Lane)
Subject: [sup-talk] Why inbox-mode instead of default search?
Date: Wed, 30 Sep 2009 13:47:53 -0400 [thread overview]
Message-ID: <1254331067-sup-9065@zyrg.net> (raw)
In-Reply-To: <1254326318-sup-904@yoom.home.cworth.org>
Excerpts from Carl Worth's message of Wed Sep 30 12:12:35 -0400 2009:
> Or said another way, you would get exactly what you want if there was
> nothing magic about inbox.
I've been working on a patch to do this. You can see the current state
at http://github.com/rlane/sup/tree/personal/. It's still buggy and
needs to be cleaned up a lot before I submit it. The basic idea is that
ThreadSet becomes tightly coupled to the Index and stays in sync with
it. This lets us use the index to determine whether a message is
relevant to a query, which was the main cause of magic previously. It
also makes ThreadIndexMode much simpler in general resulting in a net
code reduction.
next prev parent reply other threads:[~2009-09-30 17:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-27 17:04 William Erik Baxter
2009-09-27 17:46 ` William Morgan
2009-09-27 18:50 ` William Erik Baxter
2009-09-30 15:16 ` William Morgan
2009-09-30 16:12 ` Carl Worth
2009-09-30 17:47 ` Rich Lane [this message]
2009-09-30 18:04 ` William Morgan
2009-09-30 19:12 ` Carl Worth
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=1254331067-sup-9065@zyrg.net \
--to=rlane@club.cc.cmu.edu \
/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