From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "T. V. Raman" Newsgroups: gmane.emacs.devel Subject: Re: font-lock and shell scripts: Raises redisplay errors in highlight pattern: Date: Fri, 14 Jul 2006 06:00:50 -0700 Message-ID: <17591.38274.352202.751899@localhost.localdomain> References: <17580.34248.381774.421717@localhost.localdomain> <17581.56473.552614.576371@localhost.localdomain> <17589.50995.201436.401539@localhost.localdomain> Reply-To: raman@users.sf.net NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1152882102 20709 80.91.229.2 (14 Jul 2006 13:01:42 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 14 Jul 2006 13:01:42 +0000 (UTC) Cc: raman@users.sf.net, monnier@iro.umontreal.ca, storm@cua.dk, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 14 15:01:38 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1G1NIW-0007QE-Kd for ged-emacs-devel@m.gmane.org; Fri, 14 Jul 2006 15:01:36 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G1NIW-0006lg-8f for ged-emacs-devel@m.gmane.org; Fri, 14 Jul 2006 09:01:36 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G1NHx-0006ji-Uu for emacs-devel@gnu.org; Fri, 14 Jul 2006 09:01:02 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G1NHs-0006h2-2A for emacs-devel@gnu.org; Fri, 14 Jul 2006 09:00:58 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G1NHr-0006gw-LG for emacs-devel@gnu.org; Fri, 14 Jul 2006 09:00:55 -0400 Original-Received: from [206.18.177.51] (helo=alnrmhc11.comcast.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1G1NJo-00079O-3g; Fri, 14 Jul 2006 09:02:56 -0400 Original-Received: from labrador (c-67-180-167-124.hsd1.ca.comcast.net[67.180.167.124]) by comcast.net (alnrmhc11) with ESMTP id <20060714130050b1100o70v2e>; Fri, 14 Jul 2006 13:00:51 +0000 Original-Received: by labrador (Postfix, from userid 500) id 7E76B161C14F; Fri, 14 Jul 2006 06:00:50 -0700 (PDT) Original-To: rms@gnu.org In-Reply-To: X-Mailer: VM 7.19 under Emacs 22.0.50.64 x-attribution: tvr X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:57004 Archived-At: Unhandled errors do make a beep which is correct. But that is not sufficient for the user who is not looking at the display --- I need to say "why" it beeped. Also, very often I dont sit at my PC -- I sit somewhere outside with a wireless keyboard and speakers, and sadly the PC speaker beep only beeps at the PC -- not over the sound card. The latter is a bit esoteric I admit -- but for something like the vm mail reader signalling end of folder I really need more feedback than a beep. >>>>> "Richard" == Richard Stallman writes: Richard> 1) Might be marginally benefitial even for the Richard> mainstream emacs user to not have these errors Richard> raised and handled -- --- what variables in my Richard> sh-mode/font-lock environment should I look at to Richard> chase down and fix the cause of the error in the Richard> first place? (Note that I'm running with font-lock Richard> turned on at the highest level). Richard> Richard> If there is no good reason for this to signal an Richard> error, it would be cleaner to eliminate it. But Richard> first one has to track down what causes the error. Richard> One way to do that is using GDB with a breakpoint at Richard> Fsignal. Setting debug-on-signal might enable you Richard> to find the cause using the Lisp debugger. Richard> Richard> When (error ...) is called: Richard> Richard> Before-Advice: Richard> Richard> A) Check if there is a handler waiting to catch Richard> the error. B) If yes, do nothing; C) Else give the Richard> user auditory feedback. Richard> Richard> Unhandled errors do make a beep, which is auditory Richard> feedback. So what is the change that you propose? -- Best Regards, --raman Email: raman@users.sf.net WWW: http://emacspeak.sf.net/raman/ AIM: emacspeak GTalk: tv.raman.tv@gmail.com PGP: http://emacspeak.sf.net/raman/raman-almaden.asc Google: tv+raman IRC: irc://irc.freenode.net/#emacs