From: "T.V. Raman" <tv.raman.tv@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Info: Console Vs GUI difference?
Date: Sat, 2 Nov 2013 08:35:35 -0700 [thread overview]
Message-ID: <CADkJX2iJHiwUGej1ttRXYzJa2jp9o2DnhFv_sX9L5SaWTPu_Jw@mail.gmail.com> (raw)
In-Reply-To: <jwvtxfxs4k1.fsf-monnier+emacs@gnu.org>
Hi Stefan,
My last attempt at using command-error-function -- appended below
-- only produces a "back to top level" message in all instances.
Once I can get this working, I'll make the advice on signal
conditional on older emacsuns --
(defun emacspeak-error-handler (data context calling-function)
"Emacspeak custom error handling function."
(dtk-speak
(format "%s %s"
(or context "")
(or
(get (car data) 'error-message)
""))))
(declaim (special command-error-function))
(add-function :before
command-error-function 'emacspeak-error-handler)
--
--
On 10/31/13, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> And speaking of aditional emacs hooks that would help emacspeak:
>
>> 1. A hook that I can use to catch read-only errors for typing
>> commands -- a hook here would be a clean solution because
>> independent of context, I mostly want to speak the same thing
>
>> 2. Less need to advice error/ and hopefully never to advice signal --
>> This one is harder because many emacs packages use signal and
>> error to signal conditions that should be communicated to the
>> average user.
>
> It seems from where I stand that both should be covered by
> command-error-function. So, maybe you should explain in more detail
> which part of command-error-function doesn't suit your need.
>
>
> Stefan
>
next prev parent reply other threads:[~2013-11-02 15:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 9:27 Info: Console Vs GUI difference? T.V. Raman
2013-10-30 12:35 ` Stefan Monnier
2013-10-30 21:46 ` T.V. Raman
2013-10-30 23:11 ` Stefan Monnier
2013-10-31 16:21 ` T.V. Raman
2013-10-31 18:02 ` Stefan Monnier
2013-10-31 22:14 ` T.V. Raman
2013-11-01 1:32 ` Stefan Monnier
2013-11-01 2:10 ` T.V. Raman
2013-11-01 12:23 ` Stefan Monnier
2013-11-01 16:55 ` T.V. Raman
2013-11-01 18:34 ` Eli Zaretskii
2013-11-01 20:24 ` T.V. Raman
2013-11-01 20:36 ` Eli Zaretskii
2013-11-02 0:17 ` T.V. Raman
2013-11-02 2:04 ` Stefan Monnier
2013-11-03 15:51 ` T.V. Raman
2013-11-03 19:02 ` Jarek Czekalski
2013-11-03 19:05 ` T.V. Raman
2013-11-03 21:19 ` Stefan Monnier
2013-11-04 3:10 ` Dmitri Paduchikh
2013-11-04 16:38 ` T.V. Raman
2013-11-02 7:04 ` Eli Zaretskii
2013-11-02 1:39 ` T.V. Raman
2013-11-02 8:06 ` Jarek Czekalski
2013-11-02 15:35 ` T.V. Raman [this message]
2013-11-02 15:56 ` Jarek Czekalski
2013-11-02 16:35 ` Dmitri Paduchikh
2013-11-02 20:46 ` T.V. Raman
2013-10-30 13:46 ` Jarek Czekalski
2013-10-30 21:45 ` T.V. Raman
2013-10-31 20:23 ` Richard Stallman
2013-11-01 7:37 ` Eli Zaretskii
2013-11-01 17:21 ` 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
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=CADkJX2iJHiwUGej1ttRXYzJa2jp9o2DnhFv_sX9L5SaWTPu_Jw@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).