unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: William Case <billlinux@rogers.com>
To: EMACS List <help-gnu-emacs@gnu.org>
Subject: elisp beginner's parens question ??
Date: Thu, 26 Apr 2007 13:23:20 -0400	[thread overview]
Message-ID: <1177608200.3158.62.camel@CASE> (raw)

Hi;

I am working my way through the tutorial.  First, complements to whoever
wrote it.
I don't know if it has been updated in the last two years, or if I have
picked up enough to understand the very basic subject matter it deals
with, but my first try two and a half years ago left me completely
baffled.  This time through at a slow and steady pace -- everything is
clear.

Secondly, I have some questions about debugging parenthesis errors.

I had the following practice function which was giving me debug errors.
It has been fixed so I am not asking for a solution.

( ... ( ... " ..." ( ... })) 
		     ^ error.

However my questions are these:

When I used check-parens, the cursor stopped on the first left paren
whether the error was later tested on the last, second last or third
last right parens. 

Why is this? I can see a situation with far more than three parens that
would take more than a few seconds to chase down the error.  Is there or
can there be check-parens that shows which grouping has the wrong parens
or needs one added?
There didn't seem to be any distinction between a double quotes error
and a parenthesis error? 

The question that flows from the above is how does the interpreter nest
parens?
Does the outside right and left parens go with, say, a basic defun
declaration, and then work its way inwards? Or, does it just count the
number of left parens and compare it with the number of right?

Do you have any mental tips or tricks you use to check the parens
balance when you get an error that you can pass on to a newbie like me?

-- 
Regards Bill

             reply	other threads:[~2007-04-26 17:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26 17:23 William Case [this message]
     [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
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

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=1177608200.3158.62.camel@CASE \
    --to=billlinux@rogers.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).