From: Chris Mason <chris.mason@oracle.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel] searching by message instead of thread
Date: Mon, 15 Nov 2010 07:21:57 -0500 [thread overview]
Message-ID: <1289823372-sup-3394@think> (raw)
Hi everyone,
The default search setup in sup seems to just pop up the whole thread in
the results, which helps a lot because you can easily find the
related context.
But, I often get stuck on threads that last for weeks and have many many
messages. It's hard to find the actual messages that match the search.
Three things would help:
1) Toggle between the whole thread and the matching messages in the
thread view
2) Expand just the matching messages and collapse the others
3) When you hit / to search for text in the thread display, have a key
for next.
Do any of these already exist? If not, which ones seem most likely to
be acceptable?
-chris
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2010-11-15 12:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 12:21 Chris Mason [this message]
2010-11-16 23:25 ` Cameron Matheson
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=1289823372-sup-3394@think \
--to=chris.mason@oracle.com \
--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