From: "T.V. Raman" <tv.raman.tv@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Request: Use message instead of message_with_string for user visible output?
Date: Sat, 26 Oct 2013 09:33:39 -0700 [thread overview]
Message-ID: <CADkJX2gEMVVq2xsVpTFR+-UzFAN8qU7PF5k327dyMzFOENc0Vw@mail.gmail.com> (raw)
In-Reply-To: <83wql0f1ej.fsf@gnu.org>
Am happy to see you add features for emacspeak:-)
Some useful hooks to add:
1. A hook that is called when information is echoed to the
message area --- it might get chatty if it always talked.
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.
--
--
On 10/26/13, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Sat, 26 Oct 2013 09:11:41 -0700
>> From: "T.V. Raman" <tv.raman.tv@gmail.com>
>>
>> Emacspeak produces all its spoken feedback via advice --- so in
>> general, output that gets done purely through the C layer ends up
>> by-passing the advice layer.
>
> We could have special hooks to support Emacspeak and its likes,
> without moving everything to Lisp.
>
> Advice IMO is a kludgey way to get features which are missing in the
> infrastructure; if large and important (to some) packages such as
> Emacspeak need features that are missing, it is better to add such
> features than to rely on kludges forever.
>
next prev parent reply other threads:[~2013-10-26 16:33 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 [this message]
2013-10-26 19:47 ` Dmitri Paduchikh
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=CADkJX2gEMVVq2xsVpTFR+-UzFAN8qU7PF5k327dyMzFOENc0Vw@mail.gmail.com \
--to=tv.raman.tv@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.