From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: dedup issues
Date: Fri, 20 Apr 2018 09:03:02 -0500 (EST) [thread overview]
Message-ID: <7efeefe8a392616f@fantadrom.bsd.lv> (raw)
Log Message:
-----------
dedup issues
Modified Files:
--------------
mandoc:
TODO
Revision Data
-------------
Index: TODO
===================================================================
RCS file: /home/cvs/mandoc/mandoc/TODO,v
retrieving revision 1.250
retrieving revision 1.251
diff -LTODO -LTODO -u -p -r1.250 -r1.251
--- TODO
+++ TODO
@@ -363,9 +363,11 @@ are mere guesses, and some may be wrong.
--- HTML issues --------------------------------------------------------
-- duplicate names generate duplicate href="#..." attributes
+- duplicate names generate duplicate href="#..." anchor attributes
possibly use "#..._<N>" suffixes?
Jakub Klinkovsky <j dot l dot k at gmx dot com> 3 Oct 2017 21:23:36 +0200
+ see also the thread: gre(4): Rename duplicate sections
+ up to 20 Apr 2018 15:27:33 +0200
- format ".IP *" etc. as <ul> rather than <dl>
https://github.com/Debian/debiman/issues/67
@@ -466,6 +468,9 @@ are mere guesses, and some may be wrong.
************************************************************************
* warning issues
************************************************************************
+
+- warn about duplicate .Sh/.Ss heads
+ gre(4): Rename duplicate sections 20 Apr 2018 15:27:33 +0200
- style message about macros inside .Bd -literal and .Dl, in particular
font changing macros like .Cm, .Ar, .Fa (from the mdoclint TODO)
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2018-04-20 14:03 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=7efeefe8a392616f@fantadrom.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).