From: Lars Ingebrigtsen <larsi@gnus.org>
To: Mauro Aranda <maurooaranda@gmail.com>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
139@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#139: describe-key vs. widget red tape
Date: Fri, 11 Oct 2019 20:57:57 +0200 [thread overview]
Message-ID: <87lftrm7nu.fsf@gnus.org> (raw)
In-Reply-To: <CABczVwcqHE8X7t7NHHkHeVmxtroT6pRBUBP8gGLY3P8syuwfKQ@mail.gmail.com> (Mauro Aranda's message of "Fri, 11 Oct 2019 11:38:13 -0300")
Mauro Aranda <maurooaranda@gmail.com> writes:
> I finally found some time to keep working on this.
>
> I reworked the patch with the useful suggestion from Basil. I think I
> addressed all the points raised, and that the patch looks much better
> now. 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.
I think this looks great. It just needs a NEWS entry and a mention in
the Emacs (or Elisp?) manual (somewhere close to where describe-function
etc is documented).
And as Drew says, we should consider hooking this up to `C-h k' when on
a button/widget, perhaps.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-11 18:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 19:25 describe-key vs. widget red tape jidanni
2019-09-30 5:56 ` bug#139: " Lars Ingebrigtsen
2019-09-30 7:31 ` Eli Zaretskii
2019-09-30 7:40 ` Lars Ingebrigtsen
2019-09-30 8:25 ` Eli Zaretskii
2019-09-30 10:54 ` Mauro Aranda
2019-09-30 10:55 ` Mauro Aranda
2019-09-30 14:57 ` Lars Ingebrigtsen
2019-09-30 20:06 ` Mauro Aranda
2019-10-01 12:29 ` Lars Ingebrigtsen
2019-10-05 14:06 ` Mauro Aranda
2019-10-06 0:39 ` Basil L. Contovounesios
2019-10-07 1:55 ` Lars Ingebrigtsen
2019-10-08 13:04 ` Mauro Aranda
2019-10-11 14:38 ` Mauro Aranda
2019-10-11 15:23 ` Drew Adams
2019-10-11 18:57 ` Lars Ingebrigtsen [this message]
2020-08-07 11:16 ` Lars Ingebrigtsen
2020-08-07 11:38 ` Lars Ingebrigtsen
2020-10-31 1:32 ` bug#139: Still can't figure out what the command I used is called 積丹尼 Dan Jacobson
2020-10-31 2:55 ` Thien-Thi Nguyen
2020-10-31 10:33 ` 積丹尼 Dan Jacobson
2021-01-19 18:30 ` bug#139: describe-key vs. widget red tape Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lftrm7nu.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=139@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=jidanni@jidanni.org \
--cc=maurooaranda@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).