From: Lennart Jablonka <vol@ljabl.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
Alejandro Colomar <alx.manpages@gmail.com>
Cc: groff <groff@gnu.org>, linux-man <linux-man@vger.kernel.org>
Subject: Re: Manual page sections shouting
Date: Tue, 10 Jan 2023 17:21:54 +0000 [thread overview]
Message-ID: <Y72esggaPZ5jy8Z3@beryllium> (raw)
In-Reply-To: <20230107101752.p66xbjbojut4azes@illithid>
Quoth G. Branden Robinson:
>_If_ we added yet another groff extension to man(7), analogous to
>mdoc(7)'s `Sx`, we could support hyperlinks directly to man page
>sections and subsections. (On terminals, we'd still need a way to mark
>locations in the page text as link targets, and for it to be practically
>useful, pagers would have to grow more features. Given the amount of
>idiocy, particularly from people who think that a URL in a terminal
>window is a security risk in some way that a URL on a web page isn't,
>that Egmont Koblinger has had to put up with in promulgating OSC 8, I
>would not count on the infrastructure for this materializing soon.) But
>for PDF all the pieces are in place; they just need some glue in the
>groff man(7) package.
Surely man(1) and man(7) could coorperate to produce a tags file that
could be used by a pager. On OpenBSD, you can use less(1)’s :t to jump
to a bunch of stuff in a man page.
--
Lennart
next prev parent reply other threads:[~2023-01-10 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 0:25 Manual page sections shouting Alejandro Colomar
2023-01-07 0:34 ` Alejandro Colomar
2023-01-07 10:17 ` G. Branden Robinson
2023-01-07 12:04 ` Alejandro Colomar
2023-01-10 17:21 ` Lennart Jablonka [this message]
2023-01-10 19:08 ` modal man(7) extensions for groff and man-db man(1) (was: Manual page sections shouting) 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=Y72esggaPZ5jy8Z3@beryllium \
--to=vol@ljabl.com \
--cc=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=groff@gnu.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.