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

[G. Branden Robinson]

Follow-up Comment #1, bug #61935 (project groff):

Unix V7 nroff:


New Boot, known devices are hp ht rk rl rp tm vt 
: rl(0,0)rl2unix
mem = 177856
# Restricted rights: Use, duplication, or disclosure
is subject to restrictions stated in your contract with
Western Electric Company, Inc.
Thu Sep 22 08:30:25 EDT 1988

login: dmr
$ nroff
foo\c\ka
bar\kb\c
.tm \na
0
.tm \nb
72
foobar



Heirloom Doctools nroff:


$ ./bin/nroff | cat -s
foo\c\ka
bar\kb\c
.tm \na
.tm \nb
0
72
foobar



GNU troff:


$ ./build/test-groff -Tutf8 -b -ww | cat -s
foo\c\ka
bar\kb\c
.tm \na
.tm \nb
72
72
foobar



I have a suspicion that "everything" in our docs is much too
broad.  After looking at _src/roff/troff/{env,input}.cpp_, I
suspect that what is really meant is "everything that doesn't
get converted into an output node", which unfortunately is not
illuminating terminology with which to teach the meaning of the
notoriously slippery, but essential, `\c` escape sequence to
novice *roff users.

`\}` after `\c` bears looking at as well.

I tested with groff Git HEAD, but I'm betting this behavior goes
all the way back.


    _______________________________________________________

Reply to this item at:

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

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