Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Rich Lane <rlane@club.cc.cmu.edu>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] updated xapian experimental branch
Date: Sun, 01 Nov 2009 18:42:38 -0500	[thread overview]
Message-ID: <1257118189-sup-7392@zyrg.net> (raw)

I've pushed a few more commits to http://github.com/rlane/sup/tree/experimental

The major feature on this branch is the immediate label updates I've
mentioned before on the list. The bulk of the actual changes are
basically consequences of this feature:

Use of Xapian for thread relevance checks
 - Instead of hardcoding the policy into InboxMode
 - New 'z' key to clear irrelevant threads
  - Not strictly necessary, but removing messages in response to index
    events is difficult with the current UI code
  - Saves us from (half of the) adding/removing threads changes cursor_thread problem
 - Relevant messages added to thread-index-modes without reload

Async message state saving
 - Keeps the UI responsive
 - Prepares us for a sup-server future

Fallout from async message saving
 - UpdateManager messages handled in main event loop
  - Avoids many races but can lag UI unless we're careful

New, simpler undo implementation
 - Still needs work at a few use-sites to be completely correct

Let me know what you all think of these changes. I'll need to do a lot
of rebasing before this branch is clean enough to be merged.

A couple of bugs I know about:
  - Discarding drafts is disabled
  - Occasionally, new messages in an existing undisplayed thread fail to
    get added to the ThreadSet. I haven't been able to come up with a
    test case for this, so if someone wants to give that a shot it would
    be very helpful.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


             reply	other threads:[~2009-11-01 23:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-01 23:42 Rich Lane [this message]
2009-11-02 12:08 ` William Morgan
2009-11-03  3:48   ` Rich Lane
2009-11-03  8:39     ` Nicolas Pouillard
2009-11-03 16:12       ` Rich Lane
2009-11-03 16:15         ` Nicolas Pouillard

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=1257118189-sup-7392@zyrg.net \
    --to=rlane@club.cc.cmu.edu \
    --cc=sup-talk@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