all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: Advising forward-char not working properly
Date: Mon, 23 Jun 2003 16:53:36 +0900 (JST)	[thread overview]
Message-ID: <200306230753.QAA28076@etlken.m17n.org> (raw)
In-Reply-To: <87znk9w8h6.fsf@zamazal.org> (message from Milan Zamazal on Mon, 23 Jun 2003 09:36:53 +0200)

In article <87znk9w8h6.fsf@zamazal.org>, Milan Zamazal <pdm@zamazal.org> writes:

>>>>>>  "RS" == Richard Stallman <rms@gnu.org> writes:
>             When I advise the function forward-char or backward-char,
>         the advice is not invoked if the function is called via its key
>         binding.

RS>  These functions are executed directly in many cases.

> It's quite suspicious to me why invoking a command through `C-f' behaves
> differently than calling it via `M-x forward-char'.  I'm not saying it's
> a bug, but I wish Emacs were less mysterious :-|.
    
Long ago, when Gerd implemented the new display engine, I
did some test to check the effect of those special handling
of forward-char, backward-char, and self-insert-command.  As
far as I remember, the result was that I couldn't see any
merit in those special handlings.  But, what I did was to
keep pressing C-f and C-b in the TUTORIAL buffer while
making the auto repeating ratio of the keyboard as fast as
possible.  As they are interactive commands and my machine
was a rather fast one, this test is not that reliable.  But
at least, there's a possibility that we no longer need those
special handling.

How about disabling those codes and see if users really
complain or not?

---
Ken'ichi HANDA
handa@m17n.org

      reply	other threads:[~2003-06-23  7:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-13 10:02 Advising forward-char not working properly Milan Zamazal
2003-06-14 12:29 ` Richard Stallman
2003-06-23  7:36   ` Milan Zamazal
2003-06-23  7:53     ` Kenichi Handa [this message]

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=200306230753.QAA28076@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=bug-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.
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.