From: Visuwesh <visuweshm@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55393@debbugs.gnu.org
Subject: bug#55393: describe-keymap: suggest symbol at point
Date: Fri, 13 May 2022 12:05:42 +0530 [thread overview]
Message-ID: <87h75u0wjl.fsf@gmail.com> (raw)
In-Reply-To: <83fslene7p.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 13 May 2022 09:23:06 +0300")
[வெள்ளி மே 13, 2022] Eli Zaretskii wrote:
>> From: Visuwesh <visuweshm@gmail.com>
>> Date: Fri, 13 May 2022 09:35:25 +0530
>>
>> describe-keymap differs from other describe-* commands in that it does
>> not suggest the symbol at point which always annoyed me. This patch
>> makes describe-keymap consider the symbol at point first.
>>
>> [ I hope it is okay to use if-let family of macros in these files now? ]
>
> Yes, but I think a cleaner solution would be to do this kind of stuff
> in the 'interactive' form of describe-keymap, instead of this
> subroutine. The DWIM-ish operation of describe-SOMETHING commands is
> better done there, because it doesn't really belong to non-interactive
> invocations.
>
> Thanks.
The 'interactive' form of describe-keymap uses this function. I don't
see this function being used anywhere else either.
next prev parent reply other threads:[~2022-05-13 6:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 4:05 bug#55393: describe-keymap: suggest symbol at point Visuwesh
2022-05-13 5:24 ` Visuwesh
2022-05-13 6:23 ` Eli Zaretskii
2022-05-13 6:35 ` Visuwesh [this message]
2022-05-13 6:51 ` Eli Zaretskii
2022-05-13 7:42 ` Visuwesh
2022-05-13 12:06 ` Eli Zaretskii
2022-05-13 12:47 ` Visuwesh
2022-05-15 5:26 ` Eli Zaretskii
2022-05-15 5:48 ` Visuwesh
2022-05-15 6:19 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h75u0wjl.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=55393@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.