From: Drew Adams <drew.adams@oracle.com>
To: Thien-Thi Nguyen <ttn@gnu.org>, Barry OReilly <gundaetiapo@gmail.com>
Cc: emacs-devel@gnu.org
Subject: RE: [RFC] Editing Lisp through changing indentation
Date: Fri, 19 Jul 2013 08:58:23 -0700 (PDT) [thread overview]
Message-ID: <565b040d-fb4e-4302-9537-9beea2bf4248@default> (raw)
In-Reply-To: <877ggm3nu3.fsf@zigzag.favinet>
FWIW, I agree with what TTN said, including the encouragement
to continue.
For me, it's the paren/structure that takes precedence, and
the indentation that follows. I use TAB and C-M-q, among
other things, to see whether I messed up parentheses.
FWIW2, you might also be interested in a gimmick that Franz
Lisp used to have (before it moved to Common), and perhaps
some other Lisps:
A right bracket, `]', acted as a super right paren, being
equivalent to sufficient right parens to close up the
outermost open list. E.g.,
(foo (bar 1 (2 3) ((a . b) (c (d (e . f]
was equivalent to
(foo (bar 1 (2 3) ((a . b) (c (d (e . f))))))
It was mainly a typing convenience, IIRC, i.e., for
interactive use, but people did just leave the brackets in
files also (IIRC).
Another possibility (and this might have been available too;
I don't recall) would be for typing `]' to insert the right
number of right parens, instead of just inserting a `]' and
having that be interpreted as the right number of right
parens.
(I don't recall that being available, but even if it were I
suspect that most fans of `]' would have preferred to see
the `]' and be able to delete it as a single char etc.)
Such a super-paren might be considered a convenience by some,
but I never made much use of it, and I certainly don't miss it.
It is most useful, IIRC, in a REPL, i.e., interactively, where
you might not have the ability to TAB or C-M-q to fix up
indentation and see what's what wrt parens.
(Common Lisp takes a smarter view of naturally paired
delimiter chars such as `[', `]', realizing that they are
rare and that Lisp users often make use of them when defining
new languages or language constructs. But then, Common Lisp
has reader macros... It's poor cousin Emacs Lisp does not.)
next prev parent reply other threads:[~2013-07-19 15:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 3:23 [RFC] Editing Lisp through changing indentation Barry OReilly
2013-07-19 9:23 ` Thien-Thi Nguyen
2013-07-19 15:58 ` Drew Adams [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-28 21:19 Barry OReilly
2013-08-29 0:14 ` Stefan Monnier
2013-08-29 19:50 ` Barry OReilly
2013-08-29 20:04 ` Stefan Monnier
2013-08-29 20:40 ` Barry OReilly
2013-08-29 22:14 ` Stefan Monnier
2013-08-29 22:30 ` Andreas Schwab
2013-08-29 22:39 ` Stefan Monnier
2013-08-29 22:49 ` Barry OReilly
2013-08-30 2:23 ` Stefan Monnier
2013-08-30 2:48 ` Barry OReilly
2013-08-30 3:24 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=565b040d-fb4e-4302-9537-9beea2bf4248@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=gundaetiapo@gmail.com \
--cc=ttn@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.