Linux Manual Pages development
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>, groff <groff@gnu.org>,
	linux-man <linux-man@vger.kernel.org>
Subject: modal man(7) extensions for groff and man-db man(1) (was: Manual page sections shouting)
Date: Tue, 10 Jan 2023 13:08:02 -0600	[thread overview]
Message-ID: <20230110190802.q6g25ooerpilg5km@illithid> (raw)
In-Reply-To: <Y72esggaPZ5jy8Z3@beryllium>

[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]

Hi Lennart,

At 2023-01-10T17:21:54+0000, Lennart Jablonka wrote:
> 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.

I like this idea.  It meshes well with another I've had to eliminate the
necessity for lexgrog(1) by supporting a mode (selected by a register or
string specified at formatting time) where the page formats the contents
of the "Name" section, and _only_ that, and exits (technically, `nx`es).

It would be up to man(1) to stuff the tag output into a temporary file
and tell less(1) to use it, but that sort of thing is consistent with
its existing feature set, I think.

Regards,
Branden

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-01-10 19:09 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
2023-01-10 19:08     ` G. Branden Robinson [this message]

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=20230110190802.q6g25ooerpilg5km@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=alx.manpages@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox