RE: doc string of dired-do-kill-lines, "killing" lines in Dired

[Drew Adams]

>     No. I explained what is unclear and how to make it clear. 
>     This time, I prefer to teach how to fish than to dish out
>     the fish & chips.
> 
> Are you claiming that it is in general more helpful just to report a
> problem than to report it and fix it?

Are you jumping wildly to presumptuous conclusions?

I claimed nothing in general. Or in particular, for that matter - I claimed
nothing at all. I said _this time_ (not in general) and I said _I prefer_. I
said nothing about being more helpful. I said nothing about why I prefer
that action this time.

However, wrt helpfulness and reporting problems: (1) Reporting a problem
(usually) _is_ helping. QA is an important part of production (of anything);
it shouldn't be undervalued. (2) In this case, I didn't just report the
problem. And I didn't just say "use this text instead" with no explanation.
I indicated what is wrong, why, and how to fix it.

And yes, if you're looking for a generality here, sometimes pointing out why
something is wrong and how to fix it is more help in the long run than just
fixing it. If only because the world is larger and lasts longer than any
individual contributor, all of whom are, alas, mortal. And, yes, there is
still a "sometimes" in that generality.

Explaining what is wrong and how to fix it can serve as an example that
helps to avoid and fix similar future problems. That is as true of
documentation as of coding or anything else.