[bug #61935] [troff] \k not ignored after \c

[G. Branden Robinson]

URL:
  <https://savannah.gnu.org/bugs/?61935>

                 Summary: [troff] \k not ignored after \c
                 Project: GNU troff
            Submitted by: gbranden
            Submitted on: Wed 26 Jan 2022 04:41:05 PM UTC
                Category: Core
                Severity: 3 - Normal
              Item Group: Incorrect behaviour
                  Status: Confirmed
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None

    _______________________________________________________

Details:

Heirloom Doctools nroff and Unix V7 nroff both ignore \k escape
sequences after the output line continuation escape sequence \c.

According to our documentation, we do too, but we really don't.


 -- Escape: \c
 -- Register: \n[.int]
     '\c' continues an output line.  Anything on the input line after it
     is ignored except '\R', which works as usual.  In contrast to
     '\<RET>', a line after '\c' is treated as a new input line, so a
     control character is recognized at its beginning.  The visual
     results depend on whether filling is enabled; see *note
     Manipulating Filling and Adjustment::.


Either we should document our difference from the AT&T lineage,
or change GNU troff to work as documented.

The above description also does not consider \" or \# escape
sequences.





    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61935>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/