public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rito Rhymes" <rito@ritovision.com>
To: "Randy Dunlap" <rdunlap@infradead.org>,
	"Rito Rhymes" <rito@ritovision.com>
Cc: <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] docs: advanced search with benchmark harness
Date: Thu, 09 Apr 2026 05:04:44 -0400	[thread overview]
Message-ID: <DHOI5DYYBXEN.3MWP1RMB6ECES@ritovision.com> (raw)
In-Reply-To: <b3c87ef0-5faf-4bda-90e4-e6b24419e0c0@infradead.org>

> I like it. I think it's useful -- the old search could give a bit too
> much output. The search result tabs (groups) are helpful.

Thanks for taking the time to test it out again and give feedback.
I'm glad you see potential utility for it.

> I mostly use 'grep' for searching Documentation/ and I expect lots
> of other developers also do that (if they bother to look).

That's definitely what I expect kernel hackers to default to.

I'd like to get a clearer sense of your perspective, it may represent
others too, and I can weigh it against my own assumptions here.

So my question framed for you is:

You know a particular concept you want to look up, but you do not know
the exact file, and related words repeat a lot across the source.

Could you imagine yourself going through grep results, not quickly
finding what you need, burning mental bandwidth and then deciding:
"let me just go on docs.kernel.org real quick, hit the advanced search,
and see what I find"?

Is that something you could actually see ever happening?

Maybe even, in that type of situation, eventually defaulting to that
mode first to avoid spending time scanning through noisy grep results.

Or is grep and staying in the terminal a comfortable enough place to
remain even when the results are not very fruitful and the time spent
there is not especially efficient?

Or does that situation just not come up often enough to justify a
separate mental workflow for it outside the grep norm?

> I do notice under the Pages tab that all of the pages listed say
> "Summary unavailable." I don't know what should be there instead of
> that message.

It's supposed to be populated with an excerpt from the page related
to the search criterion; 2-3 lines of text or so.

I encountered that same issue after an incremental rebuild, doing a
full rebuild fixed it.

Could you please confirm if it works after a full rebuild?

Rito

      reply	other threads:[~2026-04-09  9:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-21 18:15 [PATCH] docs: add advanced search for kernel documentation Rito Rhymes
2026-03-21 22:53 ` Randy Dunlap
2026-03-21 23:15   ` Rito Rhymes
2026-03-21 23:59     ` Randy Dunlap
2026-03-22  1:12       ` Rito Rhymes
2026-03-22 19:59         ` Randy Dunlap
2026-03-23 22:50           ` Rito Rhymes
2026-03-23 23:01             ` Randy Dunlap
2026-03-28 20:55               ` Rito Rhymes
2026-03-22 16:01 ` Jonathan Corbet
2026-03-22 17:08   ` Rito Rhymes
2026-03-22 17:25     ` Rito Rhymes
2026-03-22 20:25     ` Jonathan Corbet
2026-03-22 18:17 ` [PATCH v2] " Rito Rhymes
2026-04-04  7:34 ` [PATCH v3 0/2] docs: advanced search with benchmark harness Rito Rhymes
2026-04-04  7:34   ` [PATCH v3 1/2] docs: add advanced search for kernel documentation Rito Rhymes
2026-04-04  7:34   ` [PATCH v3 2/2] docs: add advanced search benchmark harness and instrumentation Rito Rhymes
2026-04-05 12:43     ` kernel test robot
2026-04-04  7:50 ` [PATCH v3 0/2] docs: advanced search with benchmark harness Rito Rhymes
2026-04-05  5:51   ` Randy Dunlap
2026-04-09  9:04     ` Rito Rhymes [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DHOI5DYYBXEN.3MWP1RMB6ECES@ritovision.com \
    --to=rito@ritovision.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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