[bug #62042] groff: CHECKSTYLE: (incorrect) warning about blank lines inside .EX/.EE

[Alejandro Colomar]

Follow-up Comment #5, bug #62042 (project groff):


[comment #3 comment #3:]
> 
> [comment #2 comment #2:
> > Don't worry about that; I very well know it's "not" a literal mode.  You
taught me that a long time ago.  I haven't checked groff_man_style(7), though,
and don't know if it needs to be clearer to newcomers; but to me it is.
> 
> That's good.  I'd still welcome your feedback on the document as a whole. 
Though it's not ultra-short, and might take a bit of time to review.

Will do :-)

 
> > Are you sure you want to write programs as pure man(7)?
> 
> Well, no, I'm not sure--recall what I said about the CHECKSTYLE feature not
being designed.  It's there to scratch the itches I had in my long-term grind
to thoroughly revise the groff man page corpus.
> 
> I do know that I want these warnings even inside .EX/.EE sections in groff
man pages.

That makes sense.

What I'd like then, is to be able easily preclude some warnings.  I guess it's
possible, but would like you to confirm (and hopefully show an example).  For
example, for clang-tidy, I use:

$ cat etc/clang-tidy/config.yaml 
---
Checks: >
    *,
    -altera-id-dependent-backward-branch,
    -altera-unroll-loops,
    -bugprone-narrowing-conversions,
    -clang-analyzer-security.insecureAPI.DeprecatedOrUnsafeBufferHandling,
    -concurrency-mt-unsafe,
    -cppcoreguidelines-avoid-magic-numbers,
    -cppcoreguidelines-init-variables,
    -cppcoreguidelines-narrowing-conversions,
    -google-readability-braces-around-statements,
    -hicpp-braces-around-statements,
    -llvmlibc-restrict-system-libc-headers,
    -misc-no-recursion,
    -readability-braces-around-statements,
    -readability-function-cognitive-complexity,
    -readability-isolate-declaration,
    -readability-magic-numbers,

WarningsAsErrors: >
    *,
...


Something similar in a <etc/groff/tmac/checkstyle_exceptions.tmac> would be
nice.  Since maybe there are other things in level3  (or a hypothetical
level4) that I do want.  My typical usage of warnings is:  set them all, and
then remove those that cause noise.

    _______________________________________________________

Reply to this item at:

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

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