[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #64529] [ms] anomalous diagnostic for initial keep
From: |
Dave |
Subject: |
[bug #64529] [ms] anomalous diagnostic for initial keep |
Date: |
Tue, 8 Aug 2023 06:47:44 -0400 (EDT) |
URL:
<https://savannah.gnu.org/bugs/?64529>
Summary: [ms] anomalous diagnostic for initial keep
Group: GNU roff
Submitter: barx
Submitted: Tue 08 Aug 2023 05:47:42 AM CDT
Category: Macro ms
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: Tue 08 Aug 2023 05:47:42 AM CDT By: Dave <barx>
Reported by Doug McIlroy, some time ago
(http://lists.gnu.org/r/bug-groff/2011-02/msg00009.html). He discovered it in
1.20.1, but both examples produce essentially the same stderr in 1.23. In his
words:
In groff 1.20.1, -ms input that begins
.KF
.LP
draws a special diagnostic that says .LP "must be in top-level environment,
not `k', when first page is started"
But ... if you put a blank line before .KF,
.KF
.LP
.KE
you get a nonsense diagnostic: "KE without KS or KF".
Both diagnostics strike me as wrong. Why shouldn't a document begin with a
keep?
I met the problem in real life, while debugging pic input. The picture, which
was ultimately to be included in a bigger document via .PS <file, was
accompanied by a caption--thus it was bracketed by .KF/.KE.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?64529>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [bug #64529] [ms] anomalous diagnostic for initial keep,
Dave <=