all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "T.V. Raman" <tv.raman.tv@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: post-self-insert-hook and last-command:
Date: Sun, 27 May 2012 07:38:04 -0700	[thread overview]
Message-ID: <CADkJX2jRfJUieF3suzv4qmivQoMFLJgRL_7nbJS=ktJ=dDV7kg@mail.gmail.com> (raw)
In-Reply-To: <jwvmx4t7p7e.fsf-monnier+emacs@gnu.org>

Stehane, will try this-command -- not clear which calls cause the
chatter, but with the new code installed, emacs chatters more
than it used to as it loads my .emacs.  Since this is a
substantial change in how emacspeak has done things over 18
years, I suspect it'll take some testing.

The electric commands are already advised to speak, and I'm
leaving those advice fragments in place.
-- 
Best Regards,
--raman

-- 
Best Regards,
--raman


On 5/27/12, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> emacspeak-self-insert-command.  It all works (almost) -- except
>> that the speech feedback is called in situations other than  when
>> the user executes self-insert-command. The usual emacspeak
>> technique of advising has never worked for this case since
>> self-insert-command is a builtin.
>
> I wonder which calls to self-insert-command are problematic.
>
>> (eq last-command self-insert-command)
>
> Why last-command rather than this-command?
> But note that if you test this-command, you'll miss most of the
> electric-foo commands (which don't use post-self-insert-hook but
> instead define new commands that then call self-insert-command).
>
>
>         Stefan
>



      reply	other threads:[~2012-05-27 14:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-26 23:20 post-self-insert-hook and last-command: T.V. Raman
2012-05-27 13:03 ` Stefan Monnier
2012-05-27 14:38   ` T.V. Raman [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='CADkJX2jRfJUieF3suzv4qmivQoMFLJgRL_7nbJS=ktJ=dDV7kg@mail.gmail.com' \
    --to=tv.raman.tv@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.