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

[Mauro Aranda <maurooaranda@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Lars Ingebrigtsen <larsi@gnus.org>
>> Cc: jidanni@jidanni.org,  139@debbugs.gnu.org
>> Date: Mon, 30 Sep 2019 09:40:07 +0200
>>
>> > If the action of the button is not clear from the button's label, it
>> > should have a help-echo string which describes that.
>>
>> What the button does may be clear, but it can be somewhat convoluted to
>> determine precisely what function is going to end up being run.  (This
>> is for introspection/debugging purposes.)
>
> I'm not sure introspection/debugging was what the OP had in mind, but
> we could perhaps bind something like M-mouse-3 on a button to produce
> that information.  It wouldn't be easy, though, given how well the
> widget library hides that.

I took a look.  Perhaps we could start with something like the attached?
The file defines a command for describing the actions associated to a
widget.  One common indirection is that a widget's action might be to
tell its parent to run its action, so I tried to solve that indirection.

To test it, load it, put point on a widget and then type:
M-x widget-describe-actions

If that's a good start, I'm willing to work on this feature request.

Best regards,
Mauro.

[-- Attachment #2: Type: text/html, Size: 1629 bytes --]