From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Enhancements to "minor-mode-map-alist" functionality.
Date: Mon, 15 Apr 2002 08:34:51 -0400 [thread overview]
Message-ID: <200204151234.g3FCYq500838@rum.cs.yale.edu> (raw)
In-Reply-To: 5xbscnb2hh.fsf@kfs2.cua.dk
> The fundamental problem is that some modes (like viper and cua) makes
> some quite fundamental changes to the way some of the standard keys
> works [cua remaps C-c and C-x depending on the current state of the
> mark (and other conditions), while viper operates in command or insert
> mode].
BTW: some code in keyboard.c does something very much like function-key-map,
except in a hard-coded way (drop down-mouse events if they're unbound,
turn doube-clicks into single clicks if unbound, turn upper case into
lower case if unbound, my own local code has added down-modifier
and up-modifier events (I wanted to see if we could get a behavior
similar to Windows' Alt-TAB thingy which requires catching the up-Alt
event) and has correspondingly added code to drop those modifiers
if they're not bound, ...).
I was thinking of adding some kind of predicate binding, halfway
between normal bindings and default bindings. Something like
(define-key function-key-map [uppercase-p] 'map-to-lowercase)
where uppercase-p is a function that takes an event and returns a boolean.
In your case maybe you could save some keymap handling by doing something like
(define-key cua-mode-map [conditional-control-x] 'cua-cut)
where conditional-control-x returns non-nil iff the event is C-x and
the mark is active. Or maybe in your specific case we could more
simply reuse something existing:
(define-key cua-mode-map [?\C-x]
'(menu-item "cut" 'cua-cut :enable mark-active))
Making this work might be a simple matter of a few lines in get_keyelt.
Stefan
next prev parent reply other threads:[~2002-04-15 12:34 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 22:56 Enhancements to "minor-mode-map-alist" functionality Kim F. Storm
2002-04-11 22:43 ` Stefan Monnier
2002-04-12 9:31 ` Kim F. Storm
2002-04-12 13:20 ` Kim F. Storm
2002-04-12 18:46 ` Stefan Monnier
[not found] ` <5xofgoobzr.fsf@kfs2.cua.dk>
[not found] ` <200204122021.g3CKLh217680@rum.cs.yale.edu>
2002-04-14 22:32 ` Kim F. Storm
2002-04-16 20:18 ` Richard Stallman
2002-04-16 22:34 ` Kim F. Storm
2002-04-18 18:46 ` Richard Stallman
2002-04-18 23:07 ` Kim F. Storm
2002-04-19 13:43 ` Stefan Monnier
2002-04-19 15:36 ` Kim F. Storm
2002-04-19 14:46 ` Stefan Monnier
2002-04-21 17:46 ` Kim F. Storm
2002-04-22 9:28 ` Stefan Monnier
2002-04-22 15:15 ` Kim F. Storm
2002-04-19 18:42 ` Richard Stallman
2002-04-19 22:05 ` Kim F. Storm
2002-04-20 17:27 ` Richard Stallman
2002-04-21 11:08 ` Kim F. Storm
2002-04-22 7:47 ` Richard Stallman
2002-04-22 13:53 ` Kim F. Storm
2002-04-22 22:36 ` Richard Stallman
2002-04-23 10:58 ` Kim F. Storm
2002-04-22 22:36 ` Richard Stallman
2002-04-23 11:02 ` Kim F. Storm
2002-04-24 17:55 ` Richard Stallman
2002-04-26 13:44 ` Kim F. Storm
2002-04-27 22:41 ` Richard Stallman
2002-04-29 9:17 ` Kai Großjohann
2002-04-30 5:18 ` Richard Stallman
2002-04-30 21:25 ` Kim F. Storm
2002-05-01 7:14 ` Richard Stallman
2002-05-01 17:37 ` Kim F. Storm
2002-04-14 23:11 ` Kim F. Storm
2002-04-12 18:20 ` Stefan Monnier
2002-04-12 21:05 ` Kim F. Storm
2002-04-12 20:30 ` Stefan Monnier
2002-04-12 22:08 ` Kim F. Storm
2002-04-13 19:05 ` Richard Stallman
2002-04-13 19:05 ` Richard Stallman
2002-04-13 23:30 ` Kim F. Storm
2002-04-15 12:34 ` Stefan Monnier [this message]
2002-04-17 16:03 ` Richard Stallman
2002-04-15 21:54 ` Richard Stallman
2002-04-15 23:55 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200204151234.g3FCYq500838@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--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 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.