From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: help-gnu-emacs@gnu.org
Subject: Re: elisp beginner's parens question ??
Date: Fri, 27 Apr 2007 11:59:40 +0200 [thread overview]
Message-ID: <878xcef88j.fsf@ambire.localdomain> (raw)
In-Reply-To: mailman.2572.1177641875.7795.help-gnu-emacs@gnu.org
() William Case <billlinux@rogers.com>
() Thu, 26 Apr 2007 22:38:24 -0400
What I was really asking was how the interpreter or emacs uses
parenthesis or how parenthesis are nested. Put another way, I was
trying to develop for myself a minds eye view of how check-parens
works.
i share this desire, and did this to get a quick (10sec) overview:
C-h f check-parens RET ; what do you do?
C-x o TAB ; where do you do it?
RET ; how do you do it?
[ogle ogle]
from this i see that one of the funcs called is `scan-sexps' and there
is also some kind of error handling.
Does check-parens just count left parens and compare that to the
number of right parens to find an error, or does it actually examine
nested parens pairs and work inword (or outward) ?
it uses `scan-sexps' and handles errors that `scan-sexps' throws. these
are things i didn't know before starting this message, and will probably
forget a few moments after C-c C-c, but the method for re-knowing is
what is important. perhaps that is the mental tip you seek.
thi
next prev parent reply other threads:[~2007-04-27 9:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2563.1177608564.7795.help-gnu-emacs@gnu.org>
2007-04-26 19:31 ` elisp beginner's parens question ?? Thien-Thi Nguyen
2007-04-27 2:38 ` William Case
[not found] ` <mailman.2572.1177641875.7795.help-gnu-emacs@gnu.org>
2007-04-27 2:58 ` Robert D. Crawford
2007-04-27 5:43 ` William Case
2007-04-27 9:59 ` Thien-Thi Nguyen [this message]
2007-04-27 13:58 ` William Case
[not found] ` <mailman.2602.1177682661.7795.help-gnu-emacs@gnu.org>
2007-04-27 15:41 ` Thien-Thi Nguyen
2007-04-27 18:01 ` William Case
2007-04-27 21:22 ` Dieter Wilhelm
2007-04-26 17:23 William Case
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=878xcef88j.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).