Alison Schofield <[email protected]> wrote:
> Hi,
>
> I use Lore and find the threaded results of many Lore Lists useful.
> Then there is x86. It doesn't have a list, so I query:
>
> https://lore.kernel.org/all/?q=tc:[email protected]
>
> The result of that query is not threaded. Can I change my query to
> get the threading, or, as Dave Hansen suggested below, does the
> underlying code need to change.
You can use the `&x=t' parameter to give something similar to
the /$MSGID/T/ URLs which is the "flat" thread output:
https://lore.kernel.org/all/?q=tc:[email protected]&x=t
The `#t' anchor brings you directly to the thread skeleton overview:
https://lore.kernel.org/all/?q=tc:[email protected]&x=t#t
There's also an undocumented t=1 parameter which collapses
threads(*) and might reduce clutter from busy threads:
https://lore.kernel.org/all/?q=tc:[email protected]&x=t&t=1#t
(*) t=1 was only intended for the mbox downloads, but ends up
affecting HTML output
> Dave's diff follows. I don't have a means of trying that out.
Having a dothread= parameter seems redundant with x=t; but
I agree x=t can display too much and the default summary
view not enough...
> I appreciate help in improving the view of x86!
It's tricky to get the because search results can be ordered by
either relevance or date. And also the relevance percentage
next to each message.
I wonder if lore can expose [email protected] as its own inbox even
if it's technically not a subscribable mailing list. That would
be much faster (but less space-efficient) than issuing a Xapian
query to get [email protected] mails.
