[bug #66040] [troff] no longer warns about unrecognized .hcode input

[Dave]

Follow-up Comment #8, bug #66040 (group groff):

[comment #6 comment #6:]
> [comment #5 comment #5:]
> > The special character \['e] in the second line is still
> > rejected even after being assigned a code in the first.
> 
> I noticed that too.  I think it's a bug.  I'm working on it.

I mean, sure, that could be called a bug... but why would it be a bug that the
special character is unrecognized only on its second appearance?  Why
shouldn't it just be recognized in any .hcode invocation?  And as it happens,
that suggestion (bug #42870) was filed ten years ago--and its fixing would
make .hcode's behavior simple to use and simple to document, whereas allowing
it only in some cases complicates both of those.

> The part I'm griefed about is "(not a special character escape sequence)".

It's griefworthy but it's not inaccurate.  Overturning it is #42870's life
goal.


    _______________________________________________________

Reply to this item at:

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

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

signature.asc
Description: PGP signature