[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: catching parenthesis errors in elisp
From: |
Giorgos Keramidas |
Subject: |
Re: catching parenthesis errors in elisp |
Date: |
Fri, 12 Jun 2009 18:32:27 +0300 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.0.94 (berkeley-unix) |
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.
- catching parenthesis errors in elisp, rustom, 2009/06/12
- Re: catching parenthesis errors in elisp, Pascal J. Bourguignon, 2009/06/12
- Re: catching parenthesis errors in elisp, Thien-Thi Nguyen, 2009/06/12
- Re: catching parenthesis errors in elisp, Thierry Volpiatto, 2009/06/12
- Re: catching parenthesis errors in elisp, Tim X, 2009/06/12
- Re: catching parenthesis errors in elisp, Xah Lee, 2009/06/12
- Re: catching parenthesis errors in elisp, Joe Fineman, 2009/06/12