unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: egnarts-ms <egnartsms@gmail.com>
To: Emacs-devel@gnu.org
Subject: Re: indentation of functions inside flet
Date: Fri, 20 Jan 2012 06:37:55 -0800 (PST)	[thread overview]
Message-ID: <33174731.post@talk.nabble.com> (raw)
In-Reply-To: <jwvfwfao449.fsf-monnier+emacs@gnu.org>



Stefan Monnier wrote:
> 
>> So it would be nice if Lisp mode indented such function definitions like
>> defuns.  I wonder, has anyone cared about this before me (I'm sure
>> someone
>> has) and are there any improvements to the Lisp mode available ?
> 
> It would be nice if CL macros were indented better, I agree.
> Note that the way to do it is to put the bulk of the code in cl(-*).el and
> only change lisp-mode.el so as to provide hooks that CL needs.
> 
> 
>         Stefan
> 

Basically, what is wrong with the current indentation mechanism is its
short-sightedness.

We have a possibility to specify how to indent macro forms, by attaching
"lisp-indent-function" property to macro symbols, usually with (declare
(indent ...)) declaration.  But the key moment is this: indentation analysis
is limited to only the immediate enclosing list.  Once we want to indent at
some point, we find out what is the innermost containing sexp, then we take
its car and analyze it.  So the car of immediate parent fully determines the
indentation pattern.  No further upward search is performed.

For most cases this behavior is perfectly OK, but, as we see, for
"flet"-like forms this is not the case.
-- 
View this message in context: http://old.nabble.com/indentation-of-functions-inside-flet-tp33173596p33174731.html
Sent from the Emacs - Dev mailing list archive at Nabble.com.




  reply	other threads:[~2012-01-20 14:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-20 10:50 indentation of functions inside flet egnarts-ms
2012-01-20 14:13 ` Stefan Monnier
2012-01-20 14:37   ` egnarts-ms [this message]
2012-01-20 16:17     ` 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

  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=33174731.post@talk.nabble.com \
    --to=egnartsms@gmail.com \
    --cc=Emacs-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).