From: Philip Oakley <philipoakley@iee.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: Search summaries by thread?
Date: Sun, 17 Feb 2019 23:50:32 +0000 [thread overview]
Message-ID: <a4d03eb3-281f-0c04-8250-b85434bc46b7@iee.org> (raw)
In-Reply-To: <20190217233933.GA12921@dcvr>
Hi Eric,
On 17/02/2019 23:39, Eric Wong wrote:
> Philip Oakley <philipoakley@iee.org> wrote:
>> Hi,
>>
>> I often use the https://public-inbox.org/git/ search facility.
>>
>> A recent query https://public-inbox.org/git/?q=precious highlighted that it
>> may be useful to have a search summary that also summarises by thread.
> So, sorta like combining the subject-only threaded display of
> landing page (e.g <https://public-inbox.org/git/>)
>
> Or, perhaps in other words, similar to:
> <https://public-inbox.org/git/?q=precious&x=t>
> but with only the Subject/Date lines, and no message bodies.
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)
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.
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)
>
>> In this case it should greatly reduce the number of 'hits' because many
>> belong to communal threads, e.g. the "mergetool: what to do about deleting
>> precious files?" thread.
>>
>> Is this something that could be considered?
> Definitely. I don't really like the way the search summary page
> as-is, either.
Thanks
Philip
next prev parent reply other threads:[~2019-02-17 23:50 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 [this message]
2019-02-18 6:30 ` Eric Wong
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: http://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=a4d03eb3-281f-0c04-8250-b85434bc46b7@iee.org \
--to=philipoakley@iee.org \
--cc=e@80x24.org \
--cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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).