From: наб <nabijaczleweli@nabijaczleweli.xyz>
To: discuss@mandoc.bsd.lv
Subject: Forwarding arguments with \\$@ to the end of a mdoc macro invocation explodes if given ;
Date: Sun, 7 Jul 2024 18:54:46 +0200 [thread overview]
Message-ID: <t24bwwffagipvk4syqybh377bmafrcqrndwzgcoxgamq3avimz@tarta.nabijaczleweli.xyz> (raw)
[-- Attachment #1: Type: text/plain, Size: 1737 bytes --]
mandoc from 2022-10-26 and from 20 minutes ago agree on the following:
Given:
.de St-p1003.1-2024
.Tn \%IEEE No Std 1003.1-2024 Pq Dq Tn \%POSIX Ns .1 \\$@
..
then
.St-p1003.1-2024
.St-p1003.1-2024 ,
.St-p1003.1-2024 .
all work as expected.
But
.St-p1003.1-2024 ;
causes -Tlint to produce
ERROR: incomplete escape sequence: \$\&
ERROR: argument number is not numeric: \$\&
and formats as
STANDARDS
IEEE Std 1003.1-2024 (“POSIX.1”). Fl zqvFs, unit - suffixed. Ar lines
and. Ar bytes,. Fl - pid,. Fl - max - unchanged - stats,. Fl - retry, and
more than one. Ar file are extensions, originating_the GNU system. With.
Fl r,. Fl c is an extension, originating_the. Bx.. Xr sleep 1 Ns - style
suffixes for. Fl s are extensions.. Fl f is not required^detect
truncations (and is only strictly required^work for regular files and
&c. The parser is completely exploded. Fl zqvFs and everything forward
is underlined. This is fixed by the next .Sh.
Bookworm mandoc (1.14.6-1+b1) instead -Tlints as
ERROR: argument number is not numeric: \$\
and formats as
STANDARDS
IEEE Std 1003.1-2024 (“POSIX.1 &”). Fl zqvFs, unit - suffixed. Ar lines
and. Ar bytes,. Fl - pid,. Fl - max - unchanged - stats,. Fl - retry, and
more than one. Ar file are extensions, originating_the GNU system. With.
Fl r,. Fl c is an extension, originating_the. Bx.. Xr sleep 1 Ns - style
suffixes for. Fl s are extensions.. Fl f is not required^detect
&c. The parser is completely exploded. Fl zqvFs and everything forward
is underlined. This is fixed by the next .Sh.
All punctuation works as expected under groff.
Best,
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2024-07-07 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 16:54 наб [this message]
2024-07-07 17:01 ` наб
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=t24bwwffagipvk4syqybh377bmafrcqrndwzgcoxgamq3avimz@tarta.nabijaczleweli.xyz \
--to=nabijaczleweli@nabijaczleweli.xyz \
--cc=discuss@mandoc.bsd.lv \
/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;
as well as URLs for NNTP newsgroup(s).