summaryrefslogtreecommitdiffstatshomepage
path: root/TODO
diff options
context:
space:
mode:
authorIngo Schwarze <schwarze@openbsd.org>2011-01-10 03:43:47 +0000
committerIngo Schwarze <schwarze@openbsd.org>2011-01-10 03:43:47 +0000
commit8b2891b502ff415c363420b6f4238ec3561efd97 (patch)
tree0599d5e8c5399a1c669ed5ecc8300a9a5c99caca /TODO
parent79203b6f23c30a1e56eeb19c73f2dc08be416e0c (diff)
downloadmandoc-8b2891b502ff415c363420b6f4238ec3561efd97.tar.gz
mandoc-8b2891b502ff415c363420b6f4238ec3561efd97.tar.zst
mandoc-8b2891b502ff415c363420b6f4238ec3561efd97.zip
some minor issues reported by brad@
Diffstat (limited to 'TODO')
-rw-r--r--TODO17
1 files changed, 16 insertions, 1 deletions
diff --git a/TODO b/TODO
index 21ff7f34..8ae44be5 100644
--- a/TODO
+++ b/TODO
@@ -1,6 +1,6 @@
************************************************************************
* Official mandoc TODO.
-* $Id: TODO,v 1.74 2011/01/09 18:45:46 schwarze Exp $
+* $Id: TODO,v 1.75 2011/01/10 03:43:47 schwarze Exp $
************************************************************************
************************************************************************
@@ -27,6 +27,9 @@
- pod2man expects `tr' to be implemented for \*(-- to work
+- implement `rm' - it is easy to do and used in the pod2man preamble
+ reminded by brad@ Sun, Jan 09, 2011 at 09:45:58PM -0500
+
- fix bad block nesting involving multiple identical explicit blocks
see the OpenBSD mdoc_macro.c 1.47 commit message
@@ -170,6 +173,18 @@
found while talking to Chris Bennett
************************************************************************
+* error reporting issues
+************************************************************************
+
+- .fi without preceding .nf need not be an ERROR,
+ a warning is sufficient; occurs in all postfix manuals
+ reported by brad@ Sun, Jan 09, 2011 at 09:45:58PM -0500
+
+- downgrade "ERROR: macro requires body argument(s)" to WARNING
+ for the typical man(7) cases, it keeps confusing people
+ reminded by brad@ Sun, Jan 09, 2011 at 09:45:58PM -0500
+
+************************************************************************
* performance issues
************************************************************************