From: Dmitri Paduchikh <dpaduchikh@gmail.com>
To: emacs-devel@gnu.org
Cc: "T.V. Raman" <tv.raman.tv@gmail.com>
Subject: Re: Request: Use message instead of message_with_string for user visible output?
Date: Sun, 27 Oct 2013 01:47:19 +0600 [thread overview]
Message-ID: <87ob6byfug.fsf@dpaduchikh.invalid> (raw)
In-Reply-To: <CADkJX2gEMVVq2xsVpTFR+-UzFAN8qU7PF5k327dyMzFOENc0Vw@mail.gmail.com> (T. V. Raman's message of "Sat, 26 Oct 2013 09:33:39 -0700")
T.V. Raman wrote:
> Some useful hooks to add:
[...]
> 2. A pre-insert hook on self-insert-command -- right now I cant tell
> from the emacspeak end when self-insert-command bales out because
> the current context is read-only.
Just for the record, I have proposed on the Emacspeak list to use
command-error-function for speaking read-only errors. It seems to work
well with self-insert-command and other such cases.
For speaking undefined keys there is a solution using a little trickery
from ring-bell-function:
(defun my-speak-echo-area ()
(let ((msg (current-message)))
(if (> (length msg) 0)
(dtk-speak msg))))
(setq ring-bell-function
(lambda ()
(dtk-stop)
(emacspeak-auditory-icon 'warn-user)
(if (eq this-command nil)
(run-with-idle-timer 0 nil 'my-speak-echo-area))))
Of course, it would be nice if some uniform solution existed.
--
With best regards
Dmitri Paduchikh
next prev parent reply other threads:[~2013-10-26 19:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-26 16:11 Request: Use message instead of message_with_string for user visible output? T.V. Raman
2013-10-26 16:21 ` Eli Zaretskii
2013-10-26 16:33 ` T.V. Raman
2013-10-26 19:47 ` Dmitri Paduchikh [this message]
2013-10-27 22:07 ` T.V. Raman
2013-10-28 2:06 ` Richard Stallman
2013-10-28 8:04 ` Jarek Czekalski
2013-10-28 18:53 ` Johan Bockgård
2013-10-29 1:27 ` T.V. Raman
2013-10-29 1:26 ` T.V. Raman
2013-10-26 17:16 ` Drew Adams
2013-10-26 18:41 ` Stefan Monnier
2013-10-27 22:03 ` T.V. Raman
2013-10-29 20:54 ` Stefan Monnier
2013-10-30 9:17 ` T.V. Raman
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=87ob6byfug.fsf@dpaduchikh.invalid \
--to=dpaduchikh@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=tv.raman.tv@gmail.com \
/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.