From: David Kastrup <dak@gnu.org>
Cc: Lennart Borgman <lennart.borgman.073@student.lu.se>,
miles@gnu.org, emacs-devel@gnu.org
Subject: Re: unhelpful menu keybinding notes
Date: Mon, 17 Apr 2006 10:46:55 +0200 [thread overview]
Message-ID: <85slocpp1c.fsf@lola.goethe.zz> (raw)
In-Reply-To: <u4q0szj9r.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 17 Apr 2006 11:41:20 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Mon, 17 Apr 2006 10:19:56 +0200
>> From: Lennart Borgman <lennart.borgman.073@student.lu.se>
>> CC: Miles Bader <miles@gnu.org>, emacs-devel@gnu.org
>>
>> > Also, please note that, at least by default on GUI displays, these
>> > menu items don't invoke the same functions as C-w and M-w (because
>> > x-win.el turns on menu-bar-enable-clipboard).
>> >
>> Would it help if they invoked the same functions? Could we not fix that?
>
> ??? They invoke different functions for a reason, please see the
> source of the respective functions on menu-bar.el. In other words,
> this is a deliberate feature. Are you suggesting to turn it off?
I guess he'd rather use the same function which discriminates by some
other means between the two uses.
Alternatively, one could put explicit keyboard help strings into the
menus (or have some property for that purpose on the function?). One
might assume that the people with actual "<cut>", "<paste>", "<copy>"
keys would still try using them without being prompted for them.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2006-04-17 8:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 3:36 unhelpful menu keybinding notes Miles Bader
2006-04-17 7:10 ` Lennart Borgman
2006-04-17 7:28 ` Eli Zaretskii
2006-04-17 8:19 ` Lennart Borgman
2006-04-17 8:41 ` Eli Zaretskii
2006-04-17 8:46 ` David Kastrup [this message]
2006-04-17 15:50 ` Drew Adams
2006-04-17 16:29 ` Stefan Monnier
2006-04-17 16:57 ` Drew Adams
2006-04-18 1:42 ` Richard Stallman
2006-04-18 1:42 ` Richard Stallman
2006-04-17 19:11 ` Lennart Borgman
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=85slocpp1c.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman.073@student.lu.se \
--cc=miles@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).