From: storm@cua.dk (Kim F. Storm)
Cc: Chong Yidong <cyd@stupidchicken.com>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Tweak to key-description for menu bindings
Date: Wed, 02 Mar 2005 00:36:18 +0100 [thread overview]
Message-ID: <m3u0nvkkgd.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <x5y8d8j131.fsf@lola.goethe.zz> (David Kastrup's message of "Mon, 28 Feb 2005 13:55:30 +0100")
David Kastrup <dak@gnu.org> writes:
>> New:
>> Options=>Mule (Multilingual Environment)=>Set Coding Systems=>For Next Command
>>
>>
>> Shall I install this?
>
> My vote is "yes".
So far, only two votes in favour -- and one against.
> However, I would also want to suggest that such
> pretty-printed key sequences can, as some sort of a general principle,
> be passed to the kbd macro
Would be nice, but it is very hard to do.
Whereas kbd can easily parse <menu-bar> <bla> <bla> <bla> into a
vector [menu-bar bla bla bla], there is no easy way to parse Bla
This=>Bla That=>Bla Bla into the same vector without actually looking
up those strings in the keymaps -- and we don't currently have C-level
functions to do that, so we would have to implement a lot of the
keymap lookup code in Lisp to support that.
> to make a target for define-key, so that
> the developer can be spared having to switch on his brain as often as
> possible. I don't know how feasible this is as kbd is a macro, and
> the lookup could depend on the keymaps currently active or something.
This is addressed in the patch I posted yesterday:
If you enter C-h k <...select a menu item...> to look at a menu entry,
the resulting *Help* buffer contains a line
Menu binding: <menu-bar> <bla> <bla> <bla>
that the user-with-switched-off-brain can copy/paste into a kbd arg.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2005-03-01 23:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 14:35 tweak to apropos-command display Chong Yidong
2005-02-21 15:04 ` Kim F. Storm
2005-02-21 16:26 ` Chong Yidong
2005-02-21 15:14 ` Stefan
2005-02-21 16:36 ` Chong Yidong
2005-02-22 18:11 ` Richard Stallman
2005-02-22 20:36 ` Kevin Rodgers
2005-02-22 21:46 ` Kim F. Storm
2005-02-22 22:01 ` David Kastrup
2005-02-22 22:28 ` Kim F. Storm
2005-02-28 12:14 ` Tweak to key-description for menu bindings (was Re: tweak to apropos-command display) Kim F. Storm
2005-02-28 12:55 ` Tweak to key-description for menu bindings David Kastrup
2005-03-01 23:36 ` Kim F. Storm [this message]
2005-02-28 21:53 ` Tweak to key-description for menu bindings (was Re: tweak to apropos-command display) Richard Stallman
2005-02-28 22:47 ` Tweak to key-description for menu bindings Kim F. Storm
2005-02-22 22:13 ` tweak to apropos-command display Stefan Monnier
2005-02-22 22:31 ` Kim F. Storm
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=m3u0nvkkgd.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=rms@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 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).