[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #60862] grog(1) documents limitation with invalid example
From: |
Dave |
Subject: |
[bug #60862] grog(1) documents limitation with invalid example |
Date: |
Wed, 30 Jun 2021 14:06:01 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Firefox/45.0 |
URL:
<https://savannah.gnu.org/bugs/?60862>
Summary: grog(1) documents limitation with invalid example
Project: GNU troff
Submitted by: barx
Submitted on: Wed 30 Jun 2021 01:05:59 PM CDT
Category: Utilities
Severity: 2 - Minor
Item Group: Documentation
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release: None
_______________________________________________________
Details:
src/utils/grog/grog.1.man
<http://git.savannah.gnu.org/cgit/groff.git/tree/src/utils/grog/grog.1.man?id=b0de53c923bfd77191157f6caacff984e8ca5e82#n246>
states:
grog does not parse roff control structures (the "if", "ie", and "el"
requests) nor groff's "while". Thus the input
.if t .PS
.if t .PE
will not, for example, cause grog to infer use of the pic(1) preprocessor.
This may be valid to point out in general, but the specific example is not:
pic will also not recognize those lines as begin and end markers. pic
requires that the .PS and .PE be at the start of the line, without so much as
a space between the dot and the macro name.
Thus, pic will not preprocess lines set off as in the example above, so grog
is actually correct to not output the -p option based on them.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?60862>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bug #60862] grog(1) documents limitation with invalid example,
Dave <=