A trigger was an output from my "man"-script with argument "mg"
:10: warning: unbalanced .el request
(NB. Line number is wrong, because ...)
Another script showed more:
/usr/share/groff/1.22.3/tmac/mdoc/doc-common:690: backtrace: string `Dd'
/usr/share/groff/1.22.3/tmac/andoc.tmac:49: back
Bjarni Ingi Gislason wrote:
An: groff@gnu.org
Datum: 06.03.2015 22:57
Betreff: [Groff] Lack of professionalism, thinking, education, understanding,
wisdom, consequences, [references] ...
> A trigger was an output from my "man"-script with argument "mg"
>
> :10: warning: unbalanced .el
Bjarni Ingi Gislason wrote:
> I did not see at first anything wrong, there are two left curly
> brackets and two right ones. Each "ie" and "el" has a one line
> argument or a block, but the code is FLAT, there is NO STRUCTURE
> visible.
There is indeed no indentation in the installed
/usr/loc
Hi Bjarni,
wow! That's a rant for change. I like it. Most of what you say
makes quite some sense. As with most good rants, there are some
exceptions where you overstate your case.
Oh, btw., nice to meet you, this is the author of that chunk of code
speaking... :-)
These are the points where
> 1. While explicit braces for blocks indeed reduce the risk to
> introduce future errors by adding requests, adding redundant
> braces makes the code longer, more deeply indented, and sometimes
> harder to read, [...]
And, perhaps most important: It makes execution slower! Contrary
