From 9560859789a0ab85ae8d0a0a6cb58c2609c89663 Mon Sep 17 00:00:00 2001
From: Ingo Schwarze <schwarze@openbsd.org>
Date: Wed, 25 Dec 2019 13:20:33 +0000
Subject: distinction between .Vt and .Va

---
 TODO | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

(limited to 'TODO')

diff --git a/TODO b/TODO
index a1f841f0..277e0599 100644
--- a/TODO
+++ b/TODO
@@ -1,6 +1,6 @@
 ************************************************************************
 * Official mandoc TODO.
-* $Id: TODO,v 1.298 2019/12/22 13:52:35 schwarze Exp $
+* $Id: TODO,v 1.299 2019/12/25 13:20:33 schwarze Exp $
 ************************************************************************
 
 Many issues are annotated for difficulty as follows:
@@ -588,6 +588,11 @@ are mere guesses, and some may be wrong.
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629161
   also Branden Robinson 18 Dec 2019 00:59:52 +1100
 
+- Can the distinction between .Vt and .Va be made stricter,
+  recommending .Vt extern char * Ns Va optarg ; ?
+  What about the block macro properties of .Vt in the SYNOPSIS?
+  zeurkous 25 Dec 2019 08:48:36 +0100
+
 - .Cd # arch1, arch2 in section 4 pages:
   find better way to indicate multiple architectures, maybe:
   allow .Dt vgafb 4 "macppc sparc64"
-- 
cgit v1.2.3