From: "Drew Adams" <drew.adams@oracle.com>
To: <help-gnu-emacs@gnu.org>
Subject: RE: Overriding self-insert-command doesn't work
Date: Mon, 12 Mar 2007 19:04:41 -0700 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICIEICDLAA.drew.adams@oracle.com> (raw)
In-Reply-To: <87hcsquuny.fsf@localhorst.mine.nu>
> > if you know ways other than advising to change the definition
> > of self-insert-command transpararently then I'm all ears.
>
> (define-key map [remap self-insert-command] #'my-version-of-self-insert)
>
> or add some function to `after-change-functions'. The first one
> requires emacs 22 (AFAIK).
I use this, which works for various Emacs versions:
(if (fboundp 'command-remapping)
(define-key map (vector 'remap old) new)
(substitute-key-definition old new map)))
next prev parent reply other threads:[~2007-03-13 2:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-10 16:56 Overriding self-insert-command doesn't work spamfilteraccount
2007-03-12 17:23 ` Robert Thorpe
2007-03-12 18:30 ` spamfilteraccount
2007-03-12 19:30 ` David Hansen
2007-03-13 2:04 ` Drew Adams [this message]
2007-03-13 1:25 ` Barry Margolin
2007-03-14 14:17 ` Robert Thorpe
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=DNEMKBNJBGPAOPIJOOICIEICDLAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@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.
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).