From: Barry Margolin <barmar@alum.mit.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: Overriding self-insert-command doesn't work
Date: Mon, 12 Mar 2007 21:25:40 -0400 [thread overview]
Message-ID: <barmar-F555DA.21254012032007@comcast.dca.giganews.com> (raw)
In-Reply-To: 1173724258.067960.37960@s48g2000cws.googlegroups.com
In article <1173724258.067960.37960@s48g2000cws.googlegroups.com>,
"spamfilteraccount@gmail.com" <spamfilteraccount@gmail.com> wrote:
> On Mar 12, 6:23 pm, "Robert Thorpe" <rtho...@realworldtech.com> wrote:
> >
> > The command "self-insert-command" is inbuilt to Emacs. It is part of
> > the static binary executable and is called directly by other parts of
> > that executable. Changing it cannot change this version.
>
> That's not very nice, is it? Regardless of whether it's built-in,
> implemented in C, it should behave as a proper lisp symbol. I don't
> see why built-in functions should have to call the internal
> implementation of self-insert-command directly rather than invoking
> the function in the symbol's function slot.
>
> Isn't it a bug?
When C functions call other C functions they use the normal C linker,
they don't go through the Lisp interpreter.
It would be possible for them to do this, but it would require extra
coding and would probably have performance implications.
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
next prev parent reply other threads:[~2007-03-13 1:25 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
2007-03-13 1:25 ` Barry Margolin [this message]
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=barmar-F555DA.21254012032007@comcast.dca.giganews.com \
--to=barmar@alum.mit.edu \
--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).