all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Giorgos Keramidas <keramida@ceid.upatras.gr>
To: help-gnu-emacs@gnu.org
Subject: Re: catching parenthesis errors in elisp
Date: Fri, 12 Jun 2009 18:32:27 +0300	[thread overview]
Message-ID: <8763f1bh84.fsf@kobe.laptop> (raw)
In-Reply-To: 029be122-b0a6-426c-ac48-18e970009a97@r31g2000prh.googlegroups.com

On Fri, 12 Jun 2009 05:25:33 -0700 (PDT), rustom <rustompmody@gmail.com> wrote:
>On Jun 12, 5:06 pm, rustom <rustompm...@gmail.com> 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.

FWIW, syntax highlighting helps a lot when you are looking for this sort
of error.  Try enabling font-lock-mode and skim through the function.
When you see large chunks of code highlighted with the colour of string
literals, it's often an indication of a missing quote or an extra quote.



  reply	other threads:[~2009-06-12 15:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12  7:05 catching parenthesis errors in elisp rustom
2009-06-12  9:57 ` Thien-Thi Nguyen
2009-06-12 10:18 ` Tim X
2009-06-12 11:02   ` rustom
2009-06-12 10:26 ` Thierry Volpiatto
2009-06-12 11:55 ` Xah Lee
2009-06-12 12:06   ` rustom
2009-06-12 12:24     ` Pascal J. Bourguignon
2009-06-12 12:25     ` rustom
2009-06-12 15:32       ` Giorgos Keramidas [this message]
2009-06-13  2:47       ` Barry Margolin
2009-06-13  6:43         ` rustom
2009-06-13  1:04 ` Joe Fineman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8763f1bh84.fsf@kobe.laptop \
    --to=keramida@ceid.upatras.gr \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.