bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #63011] troff/input.cpp: wrong(?) warning from "do_overstrike"


From: Bjarni Ingi Gislason
Subject: [bug #63011] troff/input.cpp: wrong(?) warning from "do_overstrike"
Date: Sun, 4 Sep 2022 09:15:50 -0400 (EDT)

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

                 Summary: troff/input.cpp: wrong(?) warning from
"do_overstrike"
                 Project: GNU troff
               Submitter: bjarniig
               Submitted: Sun 04 Sep 2022 01:15:49 PM UTC
                Category: Core
                Severity: 3 - Normal
              Item Group: Warning/Suspicious behaviour
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Sun 04 Sep 2022 01:15:49 PM UTC By: Bjarni Ingi Gislason <bjarniig>
Subject: troff/input.cpp: wrong(?) warning from "do_overstrike"

File: src/roff/troff/input.cpp

Bug #63002 shows how a newline is a valid delimiter (taken from
paragraph "5.5.3 Escapes" in "groff.info" but is not recommended).

Example

.pl 10v
Overstriking \o
\'o
next word.

GNU groff version 1.22.4 issues no warning, but git HEAD does:

troff: backtrace: file 'prof.overstriking':3
troff:prof.overstriking:3: warning: missing closing delimiter in
overstrike escape sequence (got newline)








    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]