[bug #59030] some warnings still emitted with

[Dave]

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

Summary: some warnings still emitted with
Project: GNU troff
Submitted by: barx
Submitted on: Fri 28 Aug 2020 03:48:39 AM CDT
Category: None
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release: None

_______________________________________________________

Details:


$ echo .nr .g 4 | groff-latest -Ww
troff: <standard input>:1: error: can't write read-only register





_______________________________________________________

Reply to this item at:

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

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

[Dave]

Follow-up Comment #1, bug #59030 (project groff):

Apparently hitting an accidental "return" with the cursor in the summary field
tells savannah "Submit this now!" no matter how few fields are populated.

The summary was to have read, "some warnings still emitted with all warnings
turned off".

The body was to have read:


$ echo .nr .g 4 | groff -Ww

troff: <standard input>:1: error: can't write read-only register

-Ww is supposed to silence all warnings, but doesn't.

Why would this one need to be silenced, you wonder? Isn't trying to assign to
a read-only register something the user should just correct?

As it turns out, using the .g register to distinguish GNU groff from Heirloom
troff is not as straightforward as it should be, because Heirloom has a "groff
compatibility mode" that sets .g to 1. What _is_ different between them,
however, is that Heirloom lets you assign to .g, whereas groff (as the example
above shows) does not. So this is a reliable test to see which troff you're
running; however, it generates an unsilenceable warning in groff.