[ESS] drop empty help buffers

[Rodney Sparapani]

Martin Maechler wrote:
> that was fast.
>
> IIRC the  previous  default was quite on purpose:
>
> It's not only for a non-existing command that you get a bogous help buffer,
> and in some of other such cases, the user should be able to see and
> read what the bogous buffer contains.
> (and also note that error messages by in other languages than English,
> so you can't just grep for the
> kind of error message,...)
>
> Martin
>   
Well, the buffer contains...
No documentation for 'foo' in specified packages and libraries:
you could try '??foo'

And ??foo gives...
No documentation for '?foo' in specified packages and libraries:
you could try '???foo'

What can you learn from that?  With t as the default; it just says
"No documentation" in the mini-buffer.  What am I missing?

-- 
Rodney Sparapani, PhD  Center for Patient Care and Outcomes Research
Sr. Biostatistician               http://www.mcw.edu/pcor
4 wheels good, 2 wheels better!   Medical College of Wisconsin (MCW)
WWLD?:  What Would Lombardi Do?   Milwaukee, WI, USA