From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: rustom Newsgroups: gmane.emacs.help Subject: Re: catching parenthesis errors in elisp Date: Fri, 12 Jun 2009 05:25:33 -0700 (PDT) Organization: http://groups.google.com Message-ID: <029be122-b0a6-426c-ac48-18e970009a97@r31g2000prh.googlegroups.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=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1244811041 18314 80.91.229.12 (12 Jun 2009 12:50:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 12 Jun 2009 12:50:41 +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:50:39 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 1MF6DO-00070f-AD for geh-help-gnu-emacs@m.gmane.org; Fri, 12 Jun 2009 14:50:38 +0200 Original-Received: from localhost ([127.0.0.1]:57411 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MF6DN-00040t-So for geh-help-gnu-emacs@m.gmane.org; Fri, 12 Jun 2009 08:50:37 -0400 Original-Path: news.stanford.edu!newsfeed.stanford.edu!postnews.google.com!r31g2000prh.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 25 Original-NNTP-Posting-Host: 220.225.70.2 Original-X-Trace: posting.google.com 1244809534 26068 127.0.0.1 (12 Jun 2009 12:25:34 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Fri, 12 Jun 2009 12:25:34 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: r31g2000prh.googlegroups.com; posting-host=220.225.70.2; posting-account=mBpa7woAAAAGLEWUUKpmbxm-Quu5D8ui User-Agent: G2/1.0 X-HTTP-Via: 1.1 PT-PROXY1, 1.1 PT-PROXY2 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729), gzip(gfe), gzip(gfe) Original-Xref: news.stanford.edu gnu.emacs.help:169974 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:65201 Archived-At: On Jun 12, 5:06=A0pm, 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