All of lore.kernel.org
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx@kernel.org>, Jonny Grant <jg@jguk.org>
Cc: linux-man@vger.kernel.org
Subject: Re: ⟨ vs < in hostname man page of hostname
Date: Wed, 9 Aug 2023 22:25:58 -0500	[thread overview]
Message-ID: <20230810032558.bkottjfi47b2mi2j@illithid> (raw)
In-Reply-To: <d508ed7b-7dfb-7b72-e052-c918c24bb1bf@kernel.org> <93144922-493f-f3e2-f124-59129853c083@jguk.org>

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

Hi Alex & Jonny,

At 2023-08-09T12:16:12+0200, Alejandro Colomar wrote:
> > other times '⟨⟩' .
> 
> When you see that, the page was written properly in man(7) (or
> mdoc(7)? I expect both produce the same glyph; Branden?).

https://git.savannah.gnu.org/cgit/groff.git/tree/tmac/an.tmac?h=1.23.0#n1121

At present, mdoc(7) hyperlinks don't render similarly, but I plan to
make them do so for groff 1.24.

Here's an example.

$ cat EXPERIMENTS/use-Lk.mdoc
.Dd 2023-08-09
.Dt use\-Lk 1
.Os
.Sh Name
.Nm use\-Lk
.Nd demonstrate a hyperlink
.Sh Description
What do man pages look like with
.Lk http://example.com hyperlinks ?

use-Lk(1)                   General Commands Manual                  use-Lk(1)

Name
     use-Lk — demonstrate a hyperlink

Description
     What do man pages look like with hyperlinks: http://example.com?

GNU                               2023‐08‐09                         use-Lk(1)

Except for font styling differences, mandoc(1) renders it the same.

At 2023-08-09T11:39:32+0100, Jonny Grant wrote:
> I'd change the groff configuration to generate the web version of
> those UR on man7.org to be <>. Maybe that's just my preference :)

You can express your preference in groff man(7)'s site-local
configuration.  Its installation location for your system is documented
in groff_man(7).

On my Debian system, it's in /etc/groff/man.local.

Adding the following should do the trick:

.if '\*[.T]'utf8' \{\
.  char \[la] <
.  char \[ra] >
.\}

Regards,
Branden

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

  reply	other threads:[~2023-08-10  3:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9d4608c3-1a01-b134-c0f5-423af14563eb@jguk.org>
2023-08-07 15:13 ` ⟨ vs < in hostname man page of hostname Alejandro Colomar
2023-08-07 15:36   ` Jonny Grant
2023-08-09 10:16     ` Alejandro Colomar
2023-08-09 10:39       ` Jonny Grant
2023-08-10  3:25         ` G. Branden Robinson [this message]
2023-08-13 23:52           ` Jonny Grant

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=20230810032558.bkottjfi47b2mi2j@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=alx@kernel.org \
    --cc=jg@jguk.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.