bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #54537] [PATCH] om.tmac: Add block brackets to avoid a warning abou


From: Bjarni Ingi Gislason
Subject: [bug #54537] [PATCH] om.tmac: Add block brackets to avoid a warning about unbalanced .ie
Date: Sun, 4 Nov 2018 16:32:20 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0

Follow-up Comment #2, bug #54537 (project groff):

  I can't reproduce the warning with the "om.tmac" file
 ("test-groff -z om.tmac"), but with a shorter version:


.nr #TOC 1
.nr #LIST_OF_FIGURES 1
.nr #LIST_OF_TABLES 1
.nr #LIST_OF_EQUATIONS 1
.nr #DOC_LEAD 1
.nr #SAVED_DOC_LEAD 1
.
.    if \n[#SAVED_DOC_LEAD] \{\
.       if \
(\n[#TOC]=0)&\
(\n[#LIST_OF_FIGURES]=0)&\
(\n[#LIST_OF_TABLES]=0)&\
(\n[#LIST_OF_EQUATIONS]=0) \
.          ie !\n[#DOC_LEAD]=\n[#SAVED_DOC_LEAD] .nr #RERUN_TRAPS 1
.          el .nr #SKIP_TRAPS 1
.    \}

  "test-groff -z <file>" produces:

troff: prof.block:16: warning: unbalanced .el request


  I find using blocks a better practice, is more future proof, lines
(including comments) can be added, removed from the block, without
disturbing, destroying the skeleton, or adding block delimiters.

  Blocks also help the compiler, interpreter to process the code with
certainty (simpler rules).

  The eye reads physical lines, although the interpreter, compiler can
just get one single line to process.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]