Info: Console Vs GUI difference?

["T.V. Raman" <tv.raman.tv@gmail.com>]

With all due respect, I believe you're  wrong here -- that's not
the problem.  And it works correctly at the console.  When
running under X, the signal once raised, gets raised repeatedly
after every user command, and the backtrace shows that it's
coming from redisplay.

I coded up the emacspeak handler in a function that I then called
from the advice for clarity -- not sure how you conclude that
that is the cause of the problem ---

On 11/1/13, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Fri, 1 Nov 2013 09:55:44 -0700
>> From: "T.V. Raman" <tv.raman.tv@gmail.com>
>>
>> Found the backtrace:-)
>>
>> I  see that redisplay is triggering the bug -- but only under X.
>>
>> Once user-error has been triggered once in info, then the signal
>> is raised after * every user command * -- see output below from
>> the Messages buffer.
>> backtrace()
>>   emacspeak-speak-error-message(user-error "Node has no Up")
>>   ad-Advice-signal(#<subr signal> user-error ("Node has no Up"))
>>   apply(ad-Advice-signal #<subr signal> (user-error ("Node has no Up")))
>>   signal(user-error ("Node has no Up"))
>>   user-error("Node has no %s" "Up")
>
> That's your problem, right there: why does the function that advises
> 'signal' calls emacspeak-speak-error-message in this case?  It
> shouldn't, because this signal is supposed to be caught by whoever
> called Info-up.  Your advice simply disrupted the designed flow of
> control.
>