From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: pjb@informatimago.com (Pascal J. Bourguignon) Newsgroups: gmane.emacs.help Subject: Re: catching parenthesis errors in elisp Date: Fri, 12 Jun 2009 14:24:09 +0200 Organization: Anevia SAS Message-ID: <7cljnxzlli.fsf@pbourguignon.anevia.com> References: <89aa42c7-bfc9-43de-b844-882b9db0ef77@p6g2000pre.googlegroups.com> <9879b6b4-b81f-43f3-92cf-fc22ae5bc90c@u9g2000prd.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1244810976 18130 80.91.229.12 (12 Jun 2009 12:49:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 12 Jun 2009 12:49:36 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Jun 12 14:49:31 2009 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MF6CJ-0006bV-H2 for geh-help-gnu-emacs@m.gmane.org; Fri, 12 Jun 2009 14:49:31 +0200 Original-Received: from localhost ([127.0.0.1]:56913 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MF6CI-0001zd-T5 for geh-help-gnu-emacs@m.gmane.org; Fri, 12 Jun 2009 08:49:30 -0400 Original-Path: news.stanford.edu!newsfeed.stanford.edu!postnews.google.com!news4.google.com!proxad.net!feeder1-2.proxad.net!cleanfeed1-b.proxad.net!nnrp15-1.free.fr!not-for-mail Original-Newsgroups: gnu.emacs.help Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAQMAAABtzGvEAAAABlBMVEUAAAD///+l2Z/dAAAA oElEQVR4nK3OsRHCMAwF0O8YQufUNIQRGIAja9CxSA55AxZgFO4coMgYrEDDQZWPIlNAjwq9 033pbOBPtbXuB6PKNBn5gZkhGa86Z4x2wE67O+06WxGD/HCOGR0deY3f9Ijwwt7rNGNf6Oac l/GuZTF1wFGKiYYHKSFAkjIo1b6sCYS1sVmFhhhahKQssRjRT90ITWUk6vvK3RsPGs+M1RuR mV+hO/VvFAAAAABJRU5ErkJggg== X-Accept-Language: fr, es, en X-Disabled: X-No-Archive: no User-Agent: Gnus/5.101 (Gnus v5.10.10) Emacs/22.2 (gnu/linux) Cancel-Lock: sha1:NGE4ZGJiNjdlZDUyYWYyZGYyNjgzMDYzN2YxY2Y4NzUyOTAxOGQ1NA== Original-Lines: 24 Original-NNTP-Posting-Date: 12 Jun 2009 14:24:09 MEST Original-NNTP-Posting-Host: 88.170.236.224 Original-X-Trace: 1244809449 news-1.free.fr 7866 88.170.236.224:50562 Original-X-Complaints-To: abuse@proxad.net Original-Xref: news.stanford.edu gnu.emacs.help:169973 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:65200 Archived-At: rustom writes: > Ive *not* written this lisp. What makes you think that our advices applies only on lisp code YOU would have written? Obviously we apply them to OUR OWN code, not on YOUR code! > All did (or tried to do) was take some existing lisp and change it a > bit here and there -- mostly nothing more than changing some strings. Start again from the beginning. 1- download and load paredit. Evaluate (add-hook 'emacs-lisp-mode-hook 'paredit-mode) 2- Open the original emacs lisp file again. 3- Edit carefully with the help of paredit. Paredit also manages strings so you cannot insert or remove a stray double-quote. -- __Pascal Bourguignon__