From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-man@vger.kernel.org, Alejandro Colomar <alx@kernel.org>
Subject: Re: [PATCH 2/4] man/man7/sched.7: Update the documentation references
Date: Mon, 8 Sep 2025 10:02:48 -0500 [thread overview]
Message-ID: <20250908150248.a2inbo66jrukhncb@illithid> (raw)
In-Reply-To: <20250908143411.hXW9GRME@linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 2390 bytes --]
Hi Sebastian,
At 2025-09-08T16:34:11+0200, Sebastian Andrzej Siewior wrote:
> On 2025-09-08 09:29:15 [-0500], G. Branden Robinson wrote:
> > Okay. What terminal type are you using? xterm, gnome-terminal,
> > Linux VT, etc.?
>
> lxterminal 0.4.1-1
>
> > Also, try this:
> >
> > $ MANROFFOPT=-rU0 man $your_sched_page
>
> So this renders is as
>
> | The Linux kernel documentation for the scheduler ⟨https://docs.kernel.org/scheduler⟩
>
> which would be okay. So the problem is more on my end then?
Yes and no. You've done nothing wrong, but your system configuration is
manifesting a problem. It sounds like lxterminal doesn't support OSC 8
escape sequences[1], but handles unsupported ECMA-48 escape sequences
correctly, ignoring them instead of making the terminal screen a mess.
This same problem was raised by Helge Kreutzmann last month. I expect
we're starting to see it more frequently because groff 1.23.0 (released
July 2023) finally made it into a Debian stable release, and there are
even more Debian users than I suspected.
https://lore.kernel.org/linux-man/20250825230420.2dl2kkchtmkwjge7@illithid/
There are a number of workarounds while the community sorts out an
end-to-end solution that will involve cooperation between grotty(1) [on
my plate], ncurses/terminfo, and, ideally, terminal emulator
maintainers. (Strictly speaking, the last group doesn't _need_ to be
involved; anybody could submit patches to ncurses's terminfo database to
advertise relevant terminal types' support for a so-far-unnamed
capability representing OSC 8 support.) Beyond those mentioned at the
top of the foregoing mail, here's another approach you could put in your
(more or less POSIX-conforming) shell's startup file.
case "$TERM" in
xterm*) MANROFFOPT=-rU0 ;;
*) ;;
esac
export MANROFFOPT
(I don't see a terminal type entry for "lxterminal" in ncurses's
"terminfo.src" file; this isn't a problem as long as lxterminal _very
faithfully_ emulates xterm. If it doesn't, an lxterminal developer or
power user should probably submit a type description. This is true
irrespective of OSC 8 support.)
I'm sorry for the difficulty; advancing the terminal emulation state of
the art takes the work of multiple pairs of hands.
Regards,
Branden
[1] https://gist.github.com/egmontkob/eb114294efbcd5adb1944c9f3cb5feda
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-09-08 15:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 16:01 [PATCH 0/4] sched.7 and small futex.2 updates Sebastian Andrzej Siewior
2025-08-29 16:01 ` [PATCH 1/4] man/man7/sched.7: Update the real-time section Sebastian Andrzej Siewior
2025-09-02 7:24 ` Juri Lelli
2025-09-08 13:59 ` Sebastian Andrzej Siewior
2025-08-29 16:01 ` [PATCH 2/4] man/man7/sched.7: Update the documentation references Sebastian Andrzej Siewior
2025-08-30 7:28 ` G. Branden Robinson
2025-09-08 13:51 ` Sebastian Andrzej Siewior
2025-09-08 14:11 ` G. Branden Robinson
2025-09-08 14:25 ` Sebastian Andrzej Siewior
2025-09-08 14:29 ` G. Branden Robinson
2025-09-08 14:34 ` Sebastian Andrzej Siewior
2025-09-08 15:02 ` G. Branden Robinson [this message]
2025-09-08 15:44 ` Sebastian Andrzej Siewior
2025-09-08 16:47 ` G. Branden Robinson
2025-08-29 16:01 ` [PATCH 3/4] man/man2/futex.2: Recycle two gmane URLs Sebastian Andrzej Siewior
2025-08-29 16:43 ` Carlos O'Donell
2025-08-29 17:39 ` Sebastian Andrzej Siewior
2025-08-29 17:54 ` Carlos O'Donell
2025-08-31 8:48 ` Alejandro Colomar
2025-08-29 16:02 ` [PATCH 4/4] man/man2/futex.2: Add a pointer to Linux' memory-barrier Sebastian Andrzej Siewior
2025-08-29 17:46 ` Carlos O'Donell
2025-09-08 14:21 ` Sebastian Andrzej Siewior
2025-08-30 7:33 ` G. Branden Robinson
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=20250908150248.a2inbo66jrukhncb@illithid \
--to=g.branden.robinson@gmail.com \
--cc=alx@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=linux-man@vger.kernel.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