Re: checkdoc-batch.el v.3

[Stefan Monnier <monnier@iro.umontreal.ca>]

>>> This spot of code runs M-x checkdoc in "batch" style, giving a report of
>>> problems instead of going through interactively fixing them.
>> This sounds desirable.
> If you pass a prefix argument to checkdoc-current-buffer, and a couple other
> functions, it logs all the messages to a buffer.

I know.  That's pretty much the only way I use checkdoc explicitly.
Note that it may still not list all problems (it seems that if there are
problems in the general file layout (e.g. missing trailer) it doesn't
move on to further things).

>> I generally like checkdoc, but it's too much in-your-face for my taste.
> I have found that once code is clean, checkdoc doesn't complain.  If it does
> I fix the code and it stops complaining.  If you work constantly in
> non-compliant code, this would indeed be a pain.

I want to turn it on unconditionally.  That means it should just be
a nag, but not a pain, if you don't care to follow its advice.
BTW, I often don't follow its advice, and other times I do but it
doesn't notice/understand it.

>> - solve the problem you mention that rejecting one suggestion can make
>> you miss subsequent ones.
> Using the log mode I mentioned above solves this.

I don't think it does completely.


        Stefan