Subject: bug#31803: Problems in chroot.2, ln.1, test.1, [.1

From: Paul Eggert <[email-masked]>
Date: Thu, 14 Jun 2018 12:09:08 -0700

On 06/13/2018 09:09 PM, Eric S. Raymond wrote:
> I think [\& would be better.  I have to quote-strip while parsing
> synopsis sections, so there's an order-of-operations issue there
> that's best avoided.

OK, I installed the attached. Though in hindsight I wonder, can't 
doclifter see that the brackets are bolded, and so are literals instead 
of being metanotation? (Can't hurt to ask...)

>From b500b8fedede73394be3f49d14cd3b667d091d1a Mon Sep 17 00:00:00 2001
From: Paul Eggert <[email-masked]>
Date: Thu, 14 Jun 2018 12:04:57 -0700
Subject: [PATCH] doc: port test.1 to doclifter

* man/test.x: Use \& instead of quoting (Bug#31803).
---
 man/test.x | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/man/test.x b/man/test.x
index a7aaf2c82..0adc35fee 100644
--- a/man/test.x
+++ b/man/test.x
@@ -6,14 +6,14 @@ test \- check file types and compare values
 .br
 .B test
 .br
-.\" Quote the square brackets to help doclifter (Bug#31803).
-.B "["
+.\" \& tells doclifter the brackets are literal (Bug#31803).
+.B [\&
 .I EXPRESSION
-.B "]"
+.B ]\&
 .br
-.B "[ ]"
+.B "[\& ]\&"
 .br
-.B "["
+.B [\&
 .I OPTION
 [DESCRIPTION]
 .\" Add any additional description here
-- 
2.17.1