From: grischka <grishka@gmx.de>
To: drew.adams@oracle.com
Cc: emacs-devel@gnu.org
Subject: RE: Bikeshedding "user choice"
Date: Wed, 19 Jan 2011 22:51:29 +0100 [thread overview]
Message-ID: <4D375CE1.40003@gmx.de> (raw)
> I disagree that this is the right approach. I prefer that the set of keys for
> which pass-through is currently effective be explicit within Emacs, for users
> and Lisp.
>
> If each key for which we want pass-through has an Emacs binding that specifies
> this (pass-through), then it is clear to everyone what that key does in Emacs
> (it is handled by the OS). Likewise, for Stefan's alternative of using
> `w32-passthrough-events'.
What if I want Alt-f/e/o/... to activate menus "File/Edit/Options/..."
and also for all other menus that some package might possibly add?
Are you proposing that I need to define one "pass-through" for each
of "Alt-a..z", just in case?
Also what if some package thinks it wants to bind M-f in some local
map which I would't really care except that I do care that my menu
shortcut now stops working?
--- grischka
next reply other threads:[~2011-01-19 21:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 21:51 grischka [this message]
2011-01-19 23:27 ` Bikeshedding "user choice" Drew Adams
2011-01-20 18:18 ` grischka
-- strict thread matches above, loose matches on Subject: below --
2011-01-05 14:48 Bikeshedding go! Why is <M-f4> unbound? Deniz Dogan
2011-01-05 15:29 ` Óscar Fuentes
2011-01-05 17:11 ` Deniz Dogan
2011-01-05 17:30 ` Eli Zaretskii
2011-01-05 17:36 ` Deniz Dogan
2011-01-05 18:15 ` Óscar Fuentes
2011-01-09 22:00 ` Lennart Borgman
2011-01-10 1:01 ` Drew Adams
2011-01-12 13:53 ` Stuart Hacking
2011-01-12 15:01 ` Drew Adams
2011-01-12 15:54 ` Deniz Dogan
2011-01-12 20:32 ` Stefan Monnier
2011-01-12 20:42 ` Deniz Dogan
2011-01-13 2:42 ` Stefan Monnier
2011-01-13 3:59 ` Óscar Fuentes
2011-01-14 10:49 ` PJ Weisberg
2011-01-14 15:48 ` Stefan Monnier
2011-01-15 11:41 ` Lennart Borgman
2011-01-16 21:49 ` Drew Adams
[not found] ` <227F94B0AC1649C1A41082A24! 9921783@us.oracle! .com>
[not found] ` <227F94B0AC1649C1A41082A24!9921783@us.oracle!! .com>
[not found] ` <227F94B0AC1649C1A41082A24!9921783@us.oracle!! ! .com>
[not found] ` <227F94B0AC1649C1A41082A24! 9921783@us.oracle.com >
2011-01-17 8:32 ` Lennart Borgman
2011-01-17 18:22 ` Drew Adams
2011-01-17 18:36 ` Lennart Borgman
2011-01-17 19:02 ` Drew Adams
2011-01-18 3:20 ` Bikeshedding "user choice" Stephen J. Turnbull
2011-01-18 5:29 ` Drew Adams
2011-01-18 6:11 ` Stephen J. Turnbull
2011-01-18 17:45 ` Drew Adams
2011-01-19 4:59 ` Stephen J. Turnbull
2011-01-19 19:34 ` Drew Adams
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=4D375CE1.40003@gmx.de \
--to=grishka@gmx.de \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@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).