From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>, linux-doc@vger.kernel.org
Cc: David Gow <davidgow@google.com>,
Sadiya Kazi <sadiyakazi@google.com>,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH RFC V2] docs: Add more information to the HTML sidebar
Date: Tue, 14 Feb 2023 11:33:09 -0700 [thread overview]
Message-ID: <874jroksgq.fsf@meer.lwn.net> (raw)
In-Reply-To: <8469fe5b-a8dc-98a8-05fb-8645c8a43c47@infradead.org>
Randy Dunlap <rdunlap@infradead.org> writes:
> Is there a reason that the main index's "sections" (single underline)
> don't show up in the sidebar index? Is that on purpose?
> Or just a relic of them being "sections"?
That's just how the sidebar gets generated. I would much rather see the
sections there...but if we want that, I think we'll have to implement it
ourselves.
> (Why are they sections? Why is the main document's title a chapter
> instead of being the Document title?)
Good question...that's just how it was done. Probably worth fixing.
> I would like to be able to see visually when the sidebar index goes from
> one "section" to another one, e.g., from "Internal API manuals"
> to "Development tools and processes". I think that there might be a
> small blank (like 1/2 line space) between these sections now, but
> that is easy to overlook.
See above :)
Thanks,
jon
next prev parent reply other threads:[~2023-02-14 18:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 23:09 [PATCH RFC V2] docs: Add more information to the HTML sidebar Jonathan Corbet
2023-02-04 0:02 ` Jonathan Corbet
2023-02-04 0:20 ` Akira Yokosawa
2023-02-04 7:33 ` Akira Yokosawa
2023-02-04 21:39 ` Jonathan Corbet
2023-02-04 0:02 ` Randy Dunlap
2023-02-06 19:25 ` Jonathan Corbet
2023-02-14 18:25 ` Randy Dunlap
2023-02-14 18:33 ` Jonathan Corbet [this message]
2023-02-15 10:23 ` Akira Yokosawa
2023-02-16 23:55 ` Jonathan Corbet
2023-02-04 4:36 ` David Gow
2023-02-06 11:22 ` Sadiya Kazi
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=874jroksgq.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=davidgow@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sadiyakazi@google.com \
/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