From: Joe Fineman <joe_f@verizon.net>
To: help-gnu-emacs@gnu.org
Subject: Re: catching parenthesis errors in elisp
Date: Fri, 12 Jun 2009 21:04:57 -0400 [thread overview]
Message-ID: <ufxe5gczq.fsf@verizon.net> (raw)
In-Reply-To: b439949c-f7e4-40e4-949a-dc12aadb535e@k19g2000prh.googlegroups.com
I always enter parens in matching pairs. Combined with the use of C-j
for new lines, which makes paren errors conspicuous thru wrong
indentation, that pretty much eliminates such errors in writing defuns
ab initio.
However, in *revising* defuns it is often necessary to insert & delete
parens singly, and that can lead to an insidious kind of error (I have
made it several times in the last few days): an extra paren at the end
of the defun. That is indetectable thru indentation & does not
obstruct evaling it from within (C-M-x), but will cause an abort the
next time the .emacs or Commands.el file is loaded as a whole. The
best preventive I have found is to put point after the final paren &
look for a match; but you have to remember to do it.
--
--- Joe Fineman joe_f@verizon.net
||: Christians & Marxists think suffering must mean something. :||
prev parent reply other threads:[~2009-06-13 1:04 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
2009-06-13 2:47 ` Barry Margolin
2009-06-13 6:43 ` rustom
2009-06-13 1:04 ` Joe Fineman [this message]
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=ufxe5gczq.fsf@verizon.net \
--to=joe_f@verizon.net \
--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.