summaryrefslogtreecommitdiff
path: root/makevarescape.sed
diff options
context:
space:
mode:
authorG. Branden Robinson <g.branden.robinson@gmail.com>2020-09-03 22:56:11 +1000
committerG. Branden Robinson <g.branden.robinson@gmail.com>2020-09-03 23:16:42 +1000
commitc39eb01b7772493f5461ef006308adeea4d1ff44 (patch)
tree057e65eb5d57864c0e1cc1908f7a96013b06777d /makevarescape.sed
parent5cc546e12ff17ee276bb8671b1d325bed17139e2 (diff)
downloadgroff-git-c39eb01b7772493f5461ef006308adeea4d1ff44.tar.gz
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.
Diffstat (limited to 'makevarescape.sed')
-rw-r--r--makevarescape.sed10
1 files changed, 5 insertions, 5 deletions
diff --git a/makevarescape.sed b/makevarescape.sed
index 814b0f811..2baa50c2d 100644
--- a/makevarescape.sed
+++ b/makevarescape.sed
@@ -1,9 +1,9 @@
s/\\/\\\\e/g
s/ /\\\\ /g
-s/"/\\\\(dq/g
-s/'/\\\\(aq/g
+s/"/\\\\[dq]/g
+s/'/\\\\[aq]/g
s/-/\\\\&/g
-s/\^/\\\\(ha/g
-s/`/\\\\(ga/g
-s/~/\\\\(ti/g
+s/\^/\\\\[ha]/g
+s/`/\\\\[ga]/g
+s/~/\\\\[ti]/g
s|[^ ]/\+|&\\\\:\\\\%|g