[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[groff] 01/07: makevarescape.sed: Use for \[] special characters.

From: G. Branden Robinson
Subject: [groff] 01/07: makevarescape.sed: Use for \[] special characters.
Date: Sat, 5 Sep 2020 16:06:00 -0400 (EDT)

gbranden pushed a commit to branch master
in repository groff.

commit c39eb01b7772493f5461ef006308adeea4d1ff44
Author: G. Branden Robinson <>
AuthorDate: Thu Sep 3 22:56:11 2020 +1000

    makevarescape.sed: Use for \[] special characters.
    The only man page we have that doesn't enter compatibility mode (neqn)
    also doesn't use any sed-substituted patters where characters replaced
    by a \[] special character escape form are likely to be used.
    The @g@ command prefix is the main avenue for intrusion, but I think it
    improbable that many people are going to include apostrophes, double
    quotes, carets, grave accents, or tildes in the command prefix; some or
    all of these will pick fights with the shell and require quoting that we
    don't represent in man page text anyway.
    On top of that, neqn is largely a stub page.
    If it's a problem, the better fix is to simply make neqn switch out of
    compatibility mode like all our other man pages.
 makevarescape.sed | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/makevarescape.sed b/makevarescape.sed
index 814b0f8..2baa50c 100644
--- a/makevarescape.sed
+++ b/makevarescape.sed
@@ -1,9 +1,9 @@
 s/ /\\\\ /g
 s|[^ ]/\+|&\\\\:\\\\%|g

reply via email to

[Prev in Thread] Current Thread [Next in Thread]