From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from localhost (mandoc.bsd.lv [local]) by mandoc.bsd.lv (OpenSMTPD) with ESMTPA id d684b26c for ; Wed, 25 Dec 2019 08:21:03 -0500 (EST) Date: Wed, 25 Dec 2019 08:21:03 -0500 (EST) X-Mailinglist: mandoc-source Reply-To: source@mandoc.bsd.lv MIME-Version: 1.0 From: schwarze@mandoc.bsd.lv To: source@mandoc.bsd.lv Subject: mandoc: distinction between .Vt and .Va X-Mailer: activitymail 1.26, http://search.cpan.org/dist/activitymail/ Content-Type: text/plain; charset=utf-8 Message-ID: Log Message: ----------- distinction between .Vt and .Va Modified Files: -------------- mandoc: TODO Revision Data ------------- Index: TODO =================================================================== RCS file: /home/cvs/mandoc/mandoc/TODO,v retrieving revision 1.298 retrieving revision 1.299 diff -LTODO -LTODO -u -p -r1.298 -r1.299 --- TODO +++ TODO @@ -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" -- To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv