Re: catching parenthesis errors in elisp

[rustom]

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?