Info: Console Vs GUI difference?

[T.V. Raman]

Hi Stefan --

Traced down command-error-function a bit further -- and here is
what I see:

If you add your own hook to command-error-function, Emacs appears
to mysteriously call normal-top-level after calling your custom
error handler -- At least that is what I see if I stick a
backtrace call inside an advice fragment to message.

The present show-stopper for using command-error-function in
emacspeak is that that "back to top level"  message  is echoed to
the echo area -- I can silence that message from emacspeak, but
it still shows in the echo area visually.

Here is what I have for the handler:
(defun emacspeak-error-handler  (data  context  calling-function)
  "Emacspeak custom error handling function."
  (tts-with-punctuations
   'all
   (dtk-speak
    (format "%s %s"
            (error-message-string data)
            (or context " ")))))

-- 
Best Regards,
--raman


On 11/1/13, Stefan Monnier <address@hidden> wrote:
>> hear about an alternative -- note that I suspect
>> command-error-function might run into the same issue --
>
> I don't think so: command-error-function will be called if and only if
> the normal (non-emacspeak) code would display a message, whereas
> advising `signal' leads to the problems you see, where some signals are
> "normal occurrences" that don't lead to any user-visible message because
> they get caught and handled by a `condition-case'.
>
>
>         Stefan
>