From: Randy Dunlap <rdunlap@infradead.org>
To: Rito Rhymes <rito@ritovision.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Cc: Shuah Khan <skhan@linuxfoundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] docs: allow long unbroken headings to wrap and prevent overflow
Date: Sat, 21 Mar 2026 14:32:54 -0700 [thread overview]
Message-ID: <e2b86d3b-0ffe-47ea-b4eb-defe313151af@infradead.org> (raw)
In-Reply-To: <20260321144855.30429-2-rito@ritovision.com>
On 3/21/26 7:48 AM, Rito Rhymes wrote:
> Some documentation pages contain long headings with unbroken strings
> that can exceed the content width and cause page-wide horizontal
> overflow.
>
> Allow headings to wrap when needed so they stay within the content
> column and do not break page layout.
>
> Signed-off-by: Rito Rhymes <rito@ritovision.com>
> ---
> Documentation/sphinx-static/custom.css | 7 +++++++
> 1 file changed, 7 insertions(+)
Tested-by: Randy Dunlap <rdunlap@infradead.org>
--
~Randy
next prev parent reply other threads:[~2026-03-21 21:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 14:48 [PATCH 0/1] docs: examples of pages affected by heading overflow Rito Rhymes
2026-03-21 14:48 ` [PATCH 1/1] docs: allow long unbroken headings to wrap and prevent overflow Rito Rhymes
2026-03-21 21:32 ` Randy Dunlap [this message]
2026-03-21 21:31 ` [PATCH 0/1] docs: examples of pages affected by heading overflow Randy Dunlap
2026-03-22 12:14 ` Rito Rhymes
2026-03-22 19:29 ` Randy Dunlap
2026-03-22 19:57 ` Rito Rhymes
2026-03-22 19:09 ` [PATCH v2 " Rito Rhymes
2026-03-22 19:09 ` [PATCH v2 1/1] docs: allow long unbroken headings to wrap and prevent overflow Rito Rhymes
2026-03-23 15:30 ` [PATCH v3] " Rito Rhymes
2026-03-25 19:04 ` Jonathan Corbet
2026-03-25 21:32 ` Rito Rhymes
2026-03-25 21:46 ` Rito Rhymes
2026-03-25 22:04 ` Jonathan Corbet
2026-03-26 17:00 ` Rito Rhymes
2026-04-04 8:19 ` Rito Rhymes
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=e2b86d3b-0ffe-47ea-b4eb-defe313151af@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rito@ritovision.com \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®