Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.groff.bug > #1997 > unrolled thread

[bug #59030] some warnings still emitted with

Back to article view | Back to gnu.groff.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  [bug #59030] some warnings still emitted with Dave <INVALID.NOREPLY@gnu.org> - 2020-08-28 05:02 -0400

#1997 — [bug #59030] some warnings still emitted with

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.

    _______________________________________________________

Reply to this item at:

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

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

[toc] | [standalone]

Back to top | Article view | gnu.groff.bug

csiph-web