[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #60862] grog(1) documents limitation with invalid example
|
From: |
G. Branden Robinson |
|
Subject: |
[bug #60862] grog(1) documents limitation with invalid example |
|
Date: |
Thu, 1 Jul 2021 13:07:43 -0400 (EDT) |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 |
Update of bug #60862 (project groff):
Status: Confirmed => Fixed
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #2:
commit 3ed8e933f494c18755edf05ee887f1c032289aec
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date: Thu Jul 1 21:59:06 2021 +1000
[grog]: Simplify parsing.
* src/utils/grog/grog.pl: Simplify parsing. Dave Kemper pointed out
that preprocessors like pic(1) use pretty unsophisticated *roff
parsing to determine where to perform their textual replacements. My
enhancements to support input line continuation and cope with brace
escapes were thus overengineered. Remove them.
- Drop scalars `is_continued_line` and `logical_line`.
(do_line): Stop performing logical line concatenation and detecting
input line continuation. Perform operations on `line` instead of
`logical_line`. Stop removing brace escapes.
* src/utils/grog/grog.1.man (Limitations): Update discussion.
Fixes <https://savannah.gnu.org/bugs/?60862>. Thanks, Dave!
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?60862>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/