From: Alan Mackenzie<none@example.invalid>
Subject: Re: inferior-lisp mode indenting problem
Date: Fri, 15 Aug 2003 10:29:08 +0000 [thread overview]
Message-ID: <klcihb.r5.ln@acm.acm> (raw)
In-Reply-To: m3ekznkeap.fsf@defun.localdomain
Jesper Harder <harder@myrealbox.com> wrote on Fri, 15 Aug 2003 01:30:38 +0200:
> Lowell <lkirsh@cs.ubc.ca> writes:
>> The auto-indenting of 'if' clauses in inferior-lisp mode is not
>> working properly. It does:
>>
>>
>> (if test
>> then
>> else)
> This is the way `if' should be indented in Lisp.
This is the way that `if' _is_ indented in Emacs Lisp. This is helpful
in separating the `then' (which is a single form) from the `else' (which
is several forms).
But what does _should_ mean here? Who says? What's the authority?
--
Alan Mackenzie (Munich, Germany)
Email: aacm@muuc.dee; to decode, wherever there is a repeated letter
(like "aa"), remove half of them (leaving, say, "a").
next prev parent reply other threads:[~2003-08-15 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 22:29 inferior-lisp mode indenting problem Lowell
2003-08-14 23:30 ` Jesper Harder
2003-08-15 0:21 ` John Paul Wallington
2003-08-15 0:33 ` John Paul Wallington
2003-08-15 10:29 ` Alan Mackenzie [this message]
2003-08-15 13:33 ` Jesper Harder
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=klcihb.r5.ln@acm.acm \
--to=none@example.invalid \
/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).