Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Ignore killed messages in U screen
Date: Fri, 04 Sep 2009 07:41:49 -0700	[thread overview]
Message-ID: <1252074924-sup-1994@masanjin.net> (raw)
In-Reply-To: <1252010283-sup-4453@yoom.home.cworth.org>

Reformatted excerpts from Carl Worth's message of 2009-09-03:
> But the above discussion of "killed" suggests that the mechanics
> aren't at all like that. But that instead, labels are applied to
> individual messages, and searches match individual messages and then
> construct threads from the results. Is that more or less how things
> work?

Yes. That's why killed is special; it requires work at threading time to
drop threads in which any message has a killed label, regardless of
whether that's the message that matched the query.

> So is there a mismatch between the philosophy and the mechanics, or
> did I just misunderstand the philosophy?

Not sure. Maybe both. :) The philosophy is more about the UI, IMO, than
specific implementation details (though obviosuly there's some
trickle-up).

The other way to implement this, FWIW, is to have labels automatically
spread to all messages in a thread when they're applied. I think that is
probably a better implementation, though it increases the cost at
labeling time. I've been toying with this idea in the sup server code.

> If not, it seems like it would be possible for a query like
> "!label:killed" to do exactly what is wanted without needing any
> special treatment for killed internally.

I think the above implementation would allow this.
-- 
William <wmorgan-sup at masanjin.net>


  reply	other threads:[~2009-09-04 14:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-27 15:36 Edward Z. Yang
2009-08-27 15:50 ` Ben Walton
2009-08-27 15:56 ` Edward Z. Yang
2009-09-03 19:25   ` Rich Lane
2009-09-03 23:06     ` Carl Worth
2009-09-04 14:41       ` William Morgan [this message]
2009-09-04 15:12         ` Carl Worth
2009-09-03 18:47 ` William Morgan
2009-09-03 18:57   ` Edward Z. Yang
2009-09-03 18:58     ` William Morgan
2009-09-03 19:01       ` Edward Z. Yang
2009-09-30 19:56         ` William Morgan
2009-10-01  7:36           ` Nicolas Pouillard
2009-10-01 13:34             ` William Morgan
2009-10-01 14:07               ` Nicolas Pouillard
2009-10-01 17:13                 ` Carl Worth
2009-10-06 17:11                   ` William Morgan
2009-09-03 19:13   ` Ben Walton

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=1252074924-sup-1994@masanjin.net \
    --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