From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Info: Console Vs GUI difference? Date: Fri, 01 Nov 2013 20:34:52 +0200 Message-ID: <83eh70as37.fsf@gnu.org> References: Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1383330920 6343 80.91.229.3 (1 Nov 2013 18:35:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 1 Nov 2013 18:35:20 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: "T.V. Raman" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 01 19:35:24 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VcJZ6-0006uE-8R for ged-emacs-devel@m.gmane.org; Fri, 01 Nov 2013 19:35:24 +0100 Original-Received: from localhost ([::1]:39471 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VcJZ5-0000QE-SG for ged-emacs-devel@m.gmane.org; Fri, 01 Nov 2013 14:35:23 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58260) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VcJYv-0000Q5-UJ for emacs-devel@gnu.org; Fri, 01 Nov 2013 14:35:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VcJYo-0006Fj-JY for emacs-devel@gnu.org; Fri, 01 Nov 2013 14:35:13 -0400 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:56425) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VcJYo-0006E0-BK for emacs-devel@gnu.org; Fri, 01 Nov 2013 14:35:06 -0400 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0MVL00J00KVMLB00@a-mtaout22.012.net.il> for emacs-devel@gnu.org; Fri, 01 Nov 2013 20:35:05 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MVL00J64KYFKV10@a-mtaout22.012.net.il>; Fri, 01 Nov 2013 20:35:04 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.172 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:164819 Archived-At: > Date: Fri, 1 Nov 2013 09:55:44 -0700 > From: "T.V. Raman" > > 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(# user-error ("Node has no Up")) > apply(ad-Advice-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.