From: Eric Wong <e@80x24.org>
To: Philip Oakley <philipoakley@iee.org>
Cc: meta@public-inbox.org
Subject: Re: Search summaries by thread?
Date: Mon, 18 Feb 2019 06:30:44 +0000 [thread overview]
Message-ID: <20190218063044.5muo3jwctdmctmeg@dcvr> (raw)
In-Reply-To: <a4d03eb3-281f-0c04-8250-b85434bc46b7@iee.org>
Philip Oakley <philipoakley@iee.org> wrote:
> And even better if those messages in the thread that _don't_ have the search
> term at summarised as '.....' to remove multiple irrelevant subject lines,
> e.g. within a big patch series [N/30] where you may have only one patch, and
> it's review, that should be shown)
Right, the current search results (even &x=t) won't show
non-matching messages.
> Even better maybe a limit on the number displayed within any thread (e.g.
> 10), just to reduce the amount of screen display (if it's relevant the user
> will jump to the thread.
Not sure if it'll be necessary, or not. Maybe the relevancies can be
links to individual messages on a single line:
* common subject here for 4 matches below
[56%] [42%] [12%] [4%]
> Bikeshedding, it might even be a possibility to search just within one
> thread (given a message ID or longer subject line portion to anchor the
> thread)
Wouldn't that overlap with a browser's native "Find"
functionality in the $MESSAGE_ID/T/ and $MESSAGE_ID/t/ cases?
But it could be a possibility for the $MESSAGE_ID/ (no /[tT])
endpoints, I suppose...
Anyways, I'll try to get to this once the git/cgit integration
stuff is done (soon, I hope; but life stuff interfering :<)
prev parent reply other threads:[~2019-02-18 6:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 21:56 Search summaries by thread? Philip Oakley
2019-02-17 23:39 ` Eric Wong
2019-02-17 23:50 ` Philip Oakley
2019-02-18 6:30 ` Eric Wong [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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190218063044.5muo3jwctdmctmeg@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
--cc=philipoakley@iee.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).