[groff] 05/10: groff(7): Fix escape seq and copy mode omissions.

[G. Branden Robinson]

gbranden pushed a commit to branch master
in repository groff.

commit c1c7df074777c17d8edc16ae1e8de28c61a2f7d2
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Fri May 21 13:50:18 2021 +1000

    groff(7): Fix escape seq and copy mode omissions.
    
    * man/groff.7.man (Escape Sequences): Fix omission; an the escape
      character in an unrecognized escape sequence is not merely ignored;
      the sequence produces a warning diagnostic, albeit of a type that is
      disabled by default.
    
      (Escape Sequences/Escape short reference): Fix omissions; \# and \V
      are interpreted even in copy mode.
    
    Also relocate the paragraph about unrecognized escape sequences, lifting
    it from the short reference to the parent section.
    
    Drop paragraph about \( and \[ escape forms, redundant with material
    already in parent section.
---
 ChangeLog       |  9 +++++++++
 man/groff.7.man | 25 +++++++++++--------------
 2 files changed, 20 insertions(+), 14 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index c98cd64..0b4e5b5 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,14 @@
 2021-05-20  G. Branden Robinson <g.branden.robinson@gmail.com>
 
+       * man/groff.7.man (Escape Sequences): Fix omission; an
+       the escape character in an unrecognized escape sequence is not
+       merely ignored; the sequence produces a warning diagnostic,
+       albeit of a type that is disabled by default.
+       (Escape Sequences/Escape short reference): Fix omissions; \# and
+       \V are interpreted even in copy mode.
+
+2021-05-20  G. Branden Robinson <g.branden.robinson@gmail.com>
+
        * man/groff.7.man (Escape Sequences/Escape short reference): Fix
        errors in descriptions of \d, \r, \u escapes; they move in vees,
        not ems.
diff --git a/man/groff.7.man b/man/groff.7.man
index 71c5887..9b0c119 100644
--- a/man/groff.7.man
+++ b/man/groff.7.man
@@ -3043,6 +3043,15 @@ consult its documentation to learn of \[lq]safe\[rq] 
escapes or
 alternative facilities it provides to achieve the desired result.
 .
 .
+.P
+If the escape character is followed by a character that does not
+identify a defined operation,
+the escape character is ignored
+(producing a diagnostic of the \[lq]escape\[rq] warning type,
+which is not enabled by default)
+and the following character is processed normally.
+.
+.
 .\" ====================================================================
 .SS "Escape short reference"
 .\" ====================================================================
@@ -3051,32 +3060,20 @@ The escape sequences
 .esc e ,
 .esc . ,
 .esc \[dq] ,
+.esc # ,
 .esc $ ,
 .esc * ,
 .esc a ,
 .esc n ,
 .esc t ,
 .esc g ,
+.esc V ,
 and
 .escarg \& newline
 are interpreted even in copy mode.
 .
 .
 .P
-Escape sequences starting with
-.esc (
-or
-.esc [
-do not represent single character escape sequences, but introduce escape
-names with two or more characters.
-.
-.
-.P
-If a backslash is followed by a character that does not constitute a
-defined escape sequence, the backslash is silently ignored and the
-character maps to itself.
-.
-.
 .PD 0
 .
 .\" ========= comments =========