From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: help-gnu-emacs@gnu.org
Subject: Re: catching parenthesis errors in elisp
Date: Fri, 12 Jun 2009 11:57:26 +0200 [thread overview]
Message-ID: <873aa5rczd.fsf@ambire.localdomain> (raw)
In-Reply-To: <b439949c-f7e4-40e4-949a-dc12aadb535e@k19g2000prh.googlegroups.com> (rustom's message of "Fri, 12 Jun 2009 00:05:58 -0700 (PDT)")
() rustom <rustompmody@gmail.com>
() Fri, 12 Jun 2009 00:05:58 -0700 (PDT)
Any suggestions on how to catch such errors?
Here are some suggestions, to catch the error:
- before it happens, do cut/paste by sexps;
- as it happens, see mic-paren.el;
- after it happens, try M-x check-parens RET.
thi
next prev parent reply other threads:[~2009-06-12 9:57 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 [this message]
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
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=873aa5rczd.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--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).