From: Jonathan Corbet <corbet@lwn.net>
To: Rito Rhymes <rito@ritovision.com>,
Rito Rhymes <rito@ritovision.com>,
linux-doc@vger.kernel.org
Cc: Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel@vger.kernel.org, rdunlap@infradead.org
Subject: Re: [PATCH v3] docs: contain horizontal overflow in C API descriptions
Date: Wed, 25 Mar 2026 15:14:45 -0600 [thread overview]
Message-ID: <87jyuzehmi.fsf@trenco.lwn.net> (raw)
In-Reply-To: <DHC5RBUT88C0.2OACW6VS3CYF2@ritovision.com>
"Rito Rhymes" <rito@ritovision.com> writes:
> If you could imagine an optimal solution, what would it look like?
> Can you describe the layout and/or behavior?
It should wrap so that the entire prototype is visible, but the way that
happens on small screens is definitely ugly. The trick would be to have
it wrap the way it would for an overly long line in the source.
jon
next prev parent reply other threads:[~2026-03-25 21:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 14:25 [PATCH 0/1] docs: examples of pages affected by C API signature overflow Rito Rhymes
2026-03-21 14:25 ` [PATCH 1/1] docs: contain horizontal overflow in C API descriptions Rito Rhymes
2026-03-21 21:12 ` Randy Dunlap
2026-03-22 19:37 ` [PATCH v2 0/1] docs: examples of pages affected by C API signature overflow Rito Rhymes
2026-03-22 19:37 ` [PATCH v2 1/1] docs: contain horizontal overflow in C API descriptions Rito Rhymes
2026-03-22 20:35 ` [PATCH v2 0/1] docs: examples of pages affected by C API signature overflow Jonathan Corbet
2026-03-23 9:57 ` Rito Rhymes
2026-03-23 13:42 ` Jonathan Corbet
2026-03-23 15:33 ` [PATCH v3] docs: contain horizontal overflow in C API descriptions Rito Rhymes
2026-03-25 19:00 ` Jonathan Corbet
2026-03-25 20:50 ` Rito Rhymes
2026-03-25 21:14 ` Jonathan Corbet [this message]
2026-03-26 19:10 ` Rito Rhymes
2026-03-26 18:43 ` [PATCH v4] docs: wrap long C API signatures to prevent page overflow 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=87jyuzehmi.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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