Lars Ingebrigtsen writes: > Mauro Aranda writes: > >>> Could this also be extended to button.el buttons? >> >> I think so. I'll think how to put it all together and come back with a >> patch. (Will be busy the next few days, but perhaps by the weekend I'll >> be able to send it) > > Great! Find in the attached patch my idea to implement this. I wrote a command, describe-actions, so the user does not have to care if the element to describe is either a button, a widget, or whatever. And then, the libraries that define this kind of elements should add themselves to `describe-actions-functions'. Then I implemented the functions for the button.el buttons and the widgets. There are some things I would like to ask: - I would like to put an initial value of nil to `describe-actions-functions', and let each library add the function to this list. Is it OK to use `with-eval-after-load' here? Is there another way? - I put an autoload cookie in `seq-find', in order to use it in `describe-actions'. Is it OK? Please review the patch and send any suggestions for improvement. If accepted, I'll write the documentation needed for the NEWS file and the manual. Best regards, Mauro.