From: наб <nabijaczleweli@nabijaczleweli.xyz>
To: discuss@mandoc.bsd.lv
Subject: Re: Forwarding arguments with \\$@ to the end of a mdoc macro invocation explodes if given ;
Date: Sun, 7 Jul 2024 19:01:32 +0200 [thread overview]
Message-ID: <jjirilpuu63w7zafk3tdcmmvxaqwsnajc4njc5vlr4u6lpbiul@tarta.nabijaczleweli.xyz> (raw)
In-Reply-To: <t24bwwffagipvk4syqybh377bmafrcqrndwzgcoxgamq3avimz@tarta.nabijaczleweli.xyz>
[-- Attachment #1: Type: text/plain, Size: 633 bytes --]
Nope, that's not it actually, all punctuation works.
I didn't realise that this is the only file where had eqn delims on.
Are you ready?
.de St-p1003.1-2024
.Tn \%IEEE No Std 1003.1-2024 Pq Dq Tn \%POSIX Ns .1 \\$@
..
.EQ
delim @@
.EN
.St-p1003.1-2024
produces
ERROR: incomplete escape sequence: \$\&
ERROR: argument number is not numeric: \$\&
(and the other one on older mandoc).
Because rather than parsing \$@ correctly as "all arguments",
eqn somehow sees this (I don't even think it should under normal troff?)
and tries consuming @...@, and replaces it with the rendered output of \&.
Thus, I think, \$\&?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-07-07 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 16:54 наб
2024-07-07 17:01 ` наб [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=jjirilpuu63w7zafk3tdcmmvxaqwsnajc4njc5vlr4u6lpbiul@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).