From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: \s with arbitrary arg delimiters
Date: Wed, 12 May 2021 03:35:16 -0500 (EST) [thread overview]
Message-ID: <c2a9824bdcfb10f5@mandoc.bsd.lv> (raw)
Log Message:
-----------
\s with arbitrary arg delimiters
Modified Files:
--------------
mandoc:
TODO
Revision Data
-------------
Index: TODO
===================================================================
RCS file: /home/cvs/mandoc/mandoc/TODO,v
retrieving revision 1.311
retrieving revision 1.312
diff -LTODO -LTODO -u -p -r1.311 -r1.312
--- TODO
+++ TODO
@@ -121,6 +121,10 @@ are mere guesses, and some may be wrong.
some can possibly be supported
kamil at netbsd 12 Nov 2020 17:27:09 +0100 + reply
+- \s with arbitrary arg delimiters as already supported for other escapes
+ found following jmc@'s mail 28 Apr 2021 18:31:41 +0100
+ loc * exist * algo * size * imp *
+
--- missing mdoc features ----------------------------------------------
- .Sh and .Ss should be parsed and partially callable, see groff_mdoc(7)
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2021-05-12 8:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c2a9824bdcfb10f5@mandoc.bsd.lv \
--to=schwarze@mandoc.bsd.lv \
--cc=source@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).