Re: bytecomp: doc string wider than 80 spurious warnings are back

[Eli Zaretskii]

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Fri, 29 Sep 2023 07:16:37 -0700
> Cc: emacs-devel@gnu.org
> 
> I don't feel very strongly about this, and can see myself going either
> way:
> 
> - On the one hand, the benefits of this warning are clear.
> 
> - On the other, one could argue that this is a tad too opinionated a
>   default for the byte-compiler.

We added quite a few of warnings on master, which to me says we are
actively trying to discover and warn about more problems.  Why would
we handle this particular warning differently?

> I personally wouldn't object to a patch that disabled these warnings by
> default, as long as we kept them enabled in our tree.  But that's me.

I tried to explain in another message that this has non-trivial
downsides.

> BTW, I'm curious why people find these particular warnings so intrusive,
> and not the checkdoc defaults, which I personally find both more
> opinionated and more noisy (e.g. when `checkdoc--argument-missing-flag'
> is t, entire docstrings turns red in `flymake-mode').

Agreed.  And we do ask packages to pass checkdoc before they are
accepted.