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 17:41:43 +0200 [thread overview]
Message-ID: <87zm4teseg.fsf@ambire.localdomain> (raw)
In-Reply-To: mailman.2602.1177682661.7795.help-gnu-emacs@gnu.org
() William Case <billlinux@rogers.com>
() Fri, 27 Apr 2007 09:58:10 -0400
(That could just be a beginners lack of correct
search criteria.)
it's ok to look all over the place for the source code, as long
as you eventually find it: <http://www.gnu.org/software/emacs/>.
can then move a new fact from "memorized" to "known" and its
there in my head pretty much for good.
sometimes it's fun let the known fade, as well.
bound 'show-paren-mode' to S-F4 to toggle 'show-paren-mode' on
and off. It helps me to visually check each expression and
sub-expression for balanced parens.
personally, when writing code, i use M-( C-M-o CODE M-) for the
first time (recursively ;-). after that, C-M-k, C-M-t and other
sexp-oriented stuff. in this way, balance is never lost, and no
checking is required. i find M-^ and the following useful, too:
(global-set-key "\C-c_" 'raise-sexp)
i chose underscore because raising a child "buries" the parent.
but don't take my word on it, just ask any parent!
thi
next prev parent reply other threads:[~2007-04-27 15:41 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
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 [this message]
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=87zm4teseg.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).