From: Xah Lee <xahlee@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: catching parenthesis errors in elisp
Date: Fri, 12 Jun 2009 04:55:57 -0700 (PDT) [thread overview]
Message-ID: <89aa42c7-bfc9-43de-b844-882b9db0ef77@p6g2000pre.googlegroups.com> (raw)
In-Reply-To: b439949c-f7e4-40e4-949a-dc12aadb535e@k19g2000prh.googlegroups.com
On Jun 12, 12:05 am, rustom <rustompm...@gmail.com> wrote:
> Im hacking on a 700 line elisp function.
> While doing some (fairly mechanical) cut-paste operations it looks
> like either Ive got a parenthesis or a quote (most likely double quote
> but could also be single quote) error.
>
> Any suggestions on how to catch such errors?
here's some recommendation based on how i code elisp.
• never type single paren. I always type them in pairs. And never
delete one of them.
• use tree navigation to move between code.
• to delete or move parts of expression, select the whole expression,
cut & copy to move.
so, when i code in lisp, there is never ever unmatched parenthesis.
this method beats paren-edit mode.
the detail of my editing and setup is here:
• Tips For Editing Lisp Code With Emacs
http://xahlee.org/emacs/emacs_editing_lisp.html
to select current unit of sexp, i press one key, which is bound to
extend-selection, which is defined in my ergoemacs mode. The code is
shown here:
• A Text Editor Feature: Extend Selection By Semantic Unit
http://xahlee.org/emacs/syntax_tree_walk.html
Xah
∑ http://xahlee.org/
☄
next prev parent reply other threads:[~2009-06-12 11:55 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 [this message]
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=89aa42c7-bfc9-43de-b844-882b9db0ef77@p6g2000pre.googlegroups.com \
--to=xahlee@gmail.com \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).