bug#139: describe-key vs. widget red tape

[Drew Adams]

> I went with `describe-widget' for the name of the command, but have no 
> preference over the name, so if someone suggests something better, I'm OK 
> with it.

Coming late to this party.  Apologies if
this question/comment is irrelevant or has
already been addressed.

IIUC, `C-h k' would still not offer any help
for a button click.  If I misunderstand about
that please let me know, and skip the rest of
this message.

---

It may be fine/appropriate to _also_ have
a separate help command for this (button
actions), e.g., so you can bind it to a
separate key.

But can/should we not try to also integrate
this help with `C-h k'? 

`C-h k' is for mouse-button actions as well
as keyboard keys.  From a user point of
view I'd expect `C-h k' to tell me about
any mouse or keyboard action I use.

Not having `C-h k' help with button actions
has long been a noticeable lacuna.

We already let `C-h k' tell you about both
down and up events for a click.  Why should
a user not expect that s?he can follow
`C-h k' with a click on a button and get the
expected help about what that button does
when you click it?