[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: catching parenthesis errors in elisp
From: |
rustom |
Subject: |
Re: catching parenthesis errors in elisp |
Date: |
Fri, 12 Jun 2009 23:43:39 -0700 (PDT) |
User-agent: |
G2/1.0 |
On Jun 13, 7:47 am, Barry Margolin <bar...@alum.mit.edu> wrote:
> 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).
>
Giorgos suggestion of using syntax coloring and yours of re-indenting
and re-checking are what I am trying (before hearing Pascal and
redoing it with paredit)
Are there some settings/modes to make white-space diffs standout
better?
- Re: catching parenthesis errors in elisp, (continued)
- 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, Pascal J. Bourguignon, 2009/06/12
Re: catching parenthesis errors in elisp, Joe Fineman, 2009/06/12