From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Barry Margolin Newsgroups: gmane.emacs.help Subject: Re: catching parenthesis errors in elisp Date: Fri, 12 Jun 2009 22:47:09 -0400 Organization: A noiseless patient Spider Message-ID: References: <89aa42c7-bfc9-43de-b844-882b9db0ef77@p6g2000pre.googlegroups.com> <9879b6b4-b81f-43f3-92cf-fc22ae5bc90c@u9g2000prd.googlegroups.com> <029be122-b0a6-426c-ac48-18e970009a97@r31g2000prh.googlegroups.com> NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1244864448 21827 80.91.229.12 (13 Jun 2009 03:40:48 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 13 Jun 2009 03:40:48 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Jun 13 05:40:42 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 1MFK6g-0002fC-PT for geh-help-gnu-emacs@m.gmane.org; Sat, 13 Jun 2009 05:40:39 +0200 Original-Received: from localhost ([127.0.0.1]:47791 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MFK6g-0002vS-Ad for geh-help-gnu-emacs@m.gmane.org; Fri, 12 Jun 2009 23:40:38 -0400 Original-Path: news.stanford.edu!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!newsgate.cistron.nl!newsgate.news.xs4all.nl!194.109.133.84.MISMATCH!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!feeder.news-service.com!feeder.motzarella.org!news.motzarella.org!motzarella.org!news.eternal-september.org!barmar.motzarella.org!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 41 Original-X-Trace: news.eternal-september.org U2FsdGVkX1/DGHd7Tu6mpwu0J+qR44Z0nf9Gl2SdeajTEVH/U0ojJHARebyYfHcOOt0nnr4hh47aAQaqz81EGvWbW6V/o2dxX3Bg6SH5vri+5EHykQFuptBk3dos2LXvHw1kFmrGnwc= Original-X-Complaints-To: abuse@eternal-september.org Original-NNTP-Posting-Date: Sat, 13 Jun 2009 02:47:10 +0000 (UTC) X-Auth-Sender: U2FsdGVkX19820XCgqCSa9durVJjD2YhZmeIe4MhIsA= Cancel-Lock: sha1:PP+UrTcHSzt+w1AFnpCAbLqhNYM= User-Agent: MT-NewsWatcher/3.5.3b3 (Intel Mac OS X) Mail-Copies-To: nobody Original-Xref: news.stanford.edu gnu.emacs.help:170004 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:65233 Archived-At: In article <029be122-b0a6-426c-ac48-18e970009a97@r31g2000prh.googlegroups.com>, rustom wrote: > On Jun 12, 5:06 pm, rustom wrote: > > > > Ive *not* written this lisp. > > 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. > > > > I should mention that now that error has gone -- in the sense that I'm > not getting scan errors and mismatch paren errors. > > But the way it is behaving (or unbehaving) I conclude that large > sections of it have 'disappeared' into a string most likely. > > I should also mention here what I did to 'get rid' of the error. > The function giving the paren error I moved into a new file > There I found that the culprit seemed to be a large let* -- moved it > to a second file > Voila! No check-paren errors (no changes on my part other than the C-M- > k and C-y done to move sexps around) > > Moved file 2 back into file 1 where it was pulled out; then file1 back > into the original. > No check-paren errors ; no load errors. > > I find this weird Re-indent the new file, and then diff it against the original that you modified. Look for places where the change to a line is the amount of indentation. That suggests a parenthesis problem right before that (unless the intent of your change was to nest a block of code within something new). -- Barry Margolin, barmar@alum.mit.edu Arlington, MA *** PLEASE post questions in newsgroups, not directly to me *** *** PLEASE don't copy me on replies, I'll read them in the group ***