From: "Lennart Borgman" <lennart.borgman@gmail.com>
To: "Richard Riley" <rileyrgdev@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: learning Emacs Lisp
Date: Tue, 11 Nov 2008 11:14:50 +0100 [thread overview]
Message-ID: <e01d8a50811110214l3aa44884ked96800d76552672@mail.gmail.com> (raw)
In-Reply-To: <gfbgu7$1km$4@registered.motzarella.org>
On Tue, Nov 11, 2008 at 9:48 AM, Richard Riley <rileyrgdev@gmail.com> wrote:
>> That darn old emacs again ! Seriously this has more to do with lisp in
>> general than specifically with elisp. I doubt you'd find any _one_ serious
>> programmer or author in the whole lisp community who proposes this kind of
>> style ( each closing paren on a seperate line ).
>
> You will notice that I did not propose it. I said the standard is hard
> for me to read as someone who is not an eLisp magician. I still do not
> understand (other than the reasons I postulated about above) why it is
> as it is. I find it very hard to indent and match (ok, emacs helps with
> matching brackets), but would find it very difficult to read from a
> printout for example. But this is more my lack of experience
> possibly. All hindrances can become less so with experience. But would
> aligned brackets really hurt anyone? I dont think so. It is convention
> (and convention is a good thing at times) which has the style as it
> is. Or?
I think that most elisp programmers will look at the indentation when
reading the code on paper. You can compare with python where only the
indentation matters. I do not like that, but the combination of
indentation (for the eyes) and parenthesis (for the parser) seems very
good to me.
next prev parent reply other threads:[~2008-11-11 10:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 15:21 Grouping related buffers Corey Foote
2008-11-10 16:43 ` Tassilo Horn
2008-11-10 17:24 ` Corey Foote
2008-11-10 18:05 ` learning Emacs Lisp [was: Grouping related buffers] Drew Adams
[not found] ` <mailman.9.1226340315.26697.help-gnu-emacs@gnu.org>
2008-11-10 18:27 ` learning Emacs Lisp Richard Riley
2008-11-10 19:22 ` Tassilo Horn
2008-11-10 19:48 ` Drew Adams
[not found] ` <mailman.17.1226345002.26697.help-gnu-emacs@gnu.org>
2008-11-10 19:36 ` Richard Riley
2008-11-10 20:59 ` Niels Giesen
2008-11-10 21:24 ` Richard Riley
2008-11-11 4:07 ` Xah
2008-11-12 0:24 ` B. T. Raven
2008-11-12 3:32 ` Xah
2008-11-11 6:49 ` Wei Weng
2008-11-11 18:58 ` Niels Giesen
2008-11-11 4:56 ` Andreas Politz
2008-11-11 8:48 ` Richard Riley
2008-11-11 9:57 ` Andreas Politz
2008-11-11 10:14 ` Lennart Borgman [this message]
[not found] ` <mailman.58.1226398497.26697.help-gnu-emacs@gnu.org>
2008-11-11 10:34 ` Richard Riley
2008-11-11 10:43 ` Juanma Barranquero
2008-11-11 11:04 ` Richard Riley
2008-11-11 11:17 ` Juanma Barranquero
2008-11-10 18:26 ` Grouping related buffers Drew Adams
[not found] ` <mailman.0.1226335408.26697.help-gnu-emacs@gnu.org>
2008-11-13 13:09 ` Stefan Kamphausen
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=e01d8a50811110214l3aa44884ked96800d76552672@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=rileyrgdev@gmail.com \
/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.