From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: .ce .if .B crash reported by espie@, and one other bug
Date: Sat, 9 Nov 2019 12:09:45 -0500 (EST) [thread overview]
Message-ID: <8d0769f72cda14c0@mandoc.bsd.lv> (raw)
Log Message:
-----------
.ce .if .B crash reported by espie@, and one other bug
Modified Files:
--------------
mandoc:
TODO
Revision Data
-------------
Index: TODO
===================================================================
RCS file: /home/cvs/mandoc/mandoc/TODO,v
retrieving revision 1.295
retrieving revision 1.296
diff -LTODO -LTODO -u -p -r1.295 -r1.296
--- TODO
+++ TODO
@@ -33,6 +33,14 @@ Obviously, as the issues have not been s
are mere guesses, and some may be wrong.
************************************************************************
+* crashes
+************************************************************************
+
+- .ce .if n .B two crashes because "return (*roffs[t].sub)" bypasses
+ the "high level macros abort .ce" safeguard in roff_parseln()
+ reported by espie@ in textproc/fstrcmp
+
+************************************************************************
* missing features
************************************************************************
@@ -385,6 +393,11 @@ are mere guesses, and some may be wrong.
and render them with <a class="Xr" href=...>
https://github.com/Debian/debiman/issues/15
loc * exist * algo ** size ** imp **
+
+- space characters can end up in href= attributes, for example coming
+ from the first .Xr argument (where they make no sense, but still);
+ does this affect other characters, other source macros...?
+ Jackson Pauls 29 Aug 2017 16:56:27 +0100
- The tables used to render the three-part page headers actually force
the width of the <body> to the max-width given for <html>.
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2019-11-09 17:09 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=8d0769f72cda14c0@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).