From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: more info from John Gardner about ASCII control chars in roff(7)
Date: Tue, 1 Sep 2020 13:10:58 -0500 (EST) [thread overview]
Message-ID: <f200d2fc0a7d659b@mandoc.bsd.lv> (raw)
Log Message:
-----------
more info from John Gardner about ASCII control chars in roff(7) input
Modified Files:
--------------
mandoc:
TODO
Revision Data
-------------
Index: TODO
===================================================================
RCS file: /home/cvs/mandoc/mandoc/TODO,v
retrieving revision 1.304
retrieving revision 1.305
diff -LTODO -LTODO -u -p -r1.304 -r1.305
--- TODO
+++ TODO
@@ -99,6 +99,7 @@ are mere guesses, and some may be wrong.
later handling because they can for example be used in macro names.
So they may need handling after roff(7) processing.
pointed out by John Gardner 23 Jun 2020 18:28:08 +1000
+ more info from John Gardner 29 Jun 2020 19:54:04 +1000
loc ** exist ** algo ** size ** imp *
--- missing mdoc features ----------------------------------------------
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2020-09-01 18:11 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=f200d2fc0a7d659b@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).