From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: font-lock and shell scripts: Raises redisplay errors in highlight pattern: Date: Fri, 14 Jul 2006 00:06:19 -0400 Message-ID: References: <17580.34248.381774.421717@localhost.localdomain> <17581.56473.552614.576371@localhost.localdomain> <17589.50995.201436.401539@localhost.localdomain> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1152850003 29567 80.91.229.2 (14 Jul 2006 04:06:43 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 14 Jul 2006 04:06:43 +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 06:06:40 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 1G1Ewk-0002YV-8U for ged-emacs-devel@m.gmane.org; Fri, 14 Jul 2006 06:06:34 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G1Ewj-0003qq-QL for ged-emacs-devel@m.gmane.org; Fri, 14 Jul 2006 00:06:33 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G1EwY-0003qb-Ll for emacs-devel@gnu.org; Fri, 14 Jul 2006 00:06:22 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G1EwX-0003qP-B5 for emacs-devel@gnu.org; Fri, 14 Jul 2006 00:06:21 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G1EwX-0003qL-6p for emacs-devel@gnu.org; Fri, 14 Jul 2006 00:06:21 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.52) id 1G1EyR-0002MY-FC for emacs-devel@gnu.org; Fri, 14 Jul 2006 00:08:19 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1G1EwV-0005uq-MV; Fri, 14 Jul 2006 00:06:19 -0400 Original-To: raman@users.sf.net In-reply-to: <17589.50995.201436.401539@localhost.localdomain> (raman@users.sf.net) 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:56987 Archived-At: 1) Might be marginally benefitial even for the mainstream emacs user to not have these errors raised and handled -- --- what variables in my sh-mode/font-lock environment should I look at to chase down and fix the cause of the error in the first place? (Note that I'm running with font-lock turned on at the highest level). If there is no good reason for this to signal an error, it would be cleaner to eliminate it. But first one has to track down what causes the error. One way to do that is using GDB with a breakpoint at Fsignal. Setting debug-on-signal might enable you to find the cause using the Lisp debugger. When (error ...) is called: Before-Advice: A) Check if there is a handler waiting to catch the error. B) If yes, do nothing; C) Else give the user auditory feedback. Unhandled errors do make a beep, which is auditory feedback. So what is the change that you propose?