From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: tagging issues from weerd@ regarding hyphens
Date: Fri, 1 Oct 2021 03:59:08 -0500 (EST) [thread overview]
Message-ID: <c2aaea52077129f9@mandoc.bsd.lv> (raw)
Log Message:
-----------
tagging issues from weerd@ regarding hyphens
Modified Files:
--------------
mandoc:
TODO
Revision Data
-------------
Index: TODO
===================================================================
RCS file: /home/cvs/mandoc/mandoc/TODO,v
retrieving revision 1.319
retrieving revision 1.320
diff -LTODO -LTODO -u -p -r1.319 -r1.320
--- TODO
+++ TODO
@@ -68,6 +68,11 @@ are mere guesses, and some may be wrong.
but watch out for regressions in the high-level parsers
maybe it should not even remove comments? - consider T{\"
+- tag.c, tag_put() should not put ASCII_HYPH into the tag file,
+ which happens when the tag contains "-" on the input side
+ weerd@ 28 Sep 2021 12:44:07 +0200
+ loc * exist * algo * size * imp ***
+
************************************************************************
* missing features
@@ -301,6 +306,12 @@ are mere guesses, and some may be wrong.
this may be feasible using fts_set(FTS_FOLLOW)
mail to sternenseemann 19 Aug 2021 19:11:50 +0200
loc * exist ** algo ** size * imp **
+
+- tag.c, tag_put() and callers like man_validate.c, check_tag()
+ should not mistake "\-" as a word-ending escape sequence but
+ instead translate it to plain "-" in the tag name
+ weerd@ 28 Sep 2021 12:44:07 +0200
+ loc ** exist * algo * size * imp ***
- -T man does not handle eqn(7) and tbl(7)
Stephen Gregoratto 16 Feb 2020 01:28:07 +1100
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2021-10-01 8:59 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=c2aaea52077129f9@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).