From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org, Ingo Schwarze <schwarze@openbsd.org>
Subject: Re: [PATCH] man2/: SYNOPSIS: Use SY/YS
Date: Sun, 1 Dec 2024 22:45:20 +0100 [thread overview]
Message-ID: <20241201214520.7ugsotknjsxicqdv@devuan> (raw)
In-Reply-To: <20241201205127.s25mc3wwsbazd2f4@illithid>
[-- Attachment #1: Type: text/plain, Size: 1611 bytes --]
Hi Branden,
On Sun, Dec 01, 2024 at 02:51:27PM -0600, G. Branden Robinson wrote:
> You can go ahead and use the second argument to `SY` now--older groffs
> (and other formatters) won't complain about it.[1]
Hmmm. Actually, groff <= 1.23.0 is bad: it doesn't print $2. See
below.
Cheers,
Alex
alx@devuan:~/tmp/groff$ cat foo.man
.TH a s d f
.SH Name
f \- oo
.SH Foo
.SY f (
.B void);
.YS
alx@devuan:~/tmp/groff$ groff --version | head -n1
GNU groff version 1.22.4
alx@devuan:~/tmp/groff$ groff -man -Tutf8 ./foo.man
a(s) a(s)
Name
f - oo
Foo
f void);
f d a(s)
alx@devuan:~/tmp/groff$ dpkg -l mandoc | grep mandoc
ii mandoc 1.14.6-1+b1 amd64 BSD manpage compiler toolset
alx@devuan:~/tmp/groff$ mandoc -man -Tutf8 ./foo.man
a(s) a(s)
Name
f - oo
Foo
f (
void);
f d a(s)
alx@devuan:~/tmp/groff$ ssh www
alx@www:~$ cd /tmp/
alx@www:/tmp$ /usr/bin/groff --version | head -n1
GNU groff version 1.23.0
alx@www:/tmp$ /usr/bin/groff -man -Tutf8 ./foo.man
a(s) a(s)
Name
f - oo
Foo
f void);
f d a(s)
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-12-01 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-24 21:10 [PATCH] man2/: SYNOPSIS: Use SY/YS Alejandro Colomar
2024-12-01 20:51 ` G. Branden Robinson
2024-12-01 21:45 ` Alejandro Colomar [this message]
2024-12-01 23:39 ` 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=20241201214520.7ugsotknjsxicqdv@devuan \
--to=alx@kernel.org \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=schwarze@openbsd.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