unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>
Cc: emacs-devel@gnu.org
Subject: Re: Lisp indentation.
Date: Sun, 13 Mar 2005 14:23:15 +0100	[thread overview]
Message-ID: <87psy31xz0.fsf@xs4all.nl> (raw)
In-Reply-To: <jwvfyz3p9vh.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 10 Mar 2005 14:43:34 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

[...]

> I'd say they should be set in the `declare' part of the definition
> of the macro.  See the definition of `when' or `unless' for
> examples.  Unless it's common to edit code that uses the macro while
> the macro itself is not loaded, in which case it might be worthwhile
> to put the `put' in some other file like lisp-mode.el.

Actually, there is a problem with using declare to specify
indentation.  Some macro's like `eval-when-compile' are defined upon
startup, because loadup.el loads the file in which they are defined.
If (put ... 'lisp-indent-function ...) is used to specify indentation,
then that is executed during startup as well.  However, if (declare
(indent ...)) is used to specify indentation, then the macro is
defined during startup, but its lisp-indent-property will not be set.

[I guess, this is why there is a (put 'when 'lisp-indent-function 1)
in lisp-mode.el, even though the definition of when in subr.el uses
(declare (indent 1)).]

(declare (debug ...)) has the same problem wrt the edebug-form-spec
property.

This should probably be fixed somehow, or else documented.

Lute.

  parent reply	other threads:[~2005-03-13 13:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-10 18:26 Lisp indentation Lute Kamstra
2005-03-10 19:43 ` Stefan Monnier
2005-03-11  1:29   ` Lute Kamstra
2005-03-12 17:40     ` Lute Kamstra
2005-03-13 13:23   ` Lute Kamstra [this message]
2005-03-13 13:51     ` Stefan Monnier
2005-03-13 16:29       ` Lute Kamstra
2005-03-14 12:58         ` Stefan Monnier
2005-03-14 13:55           ` Lute Kamstra
2005-03-14  3:00     ` Richard Stallman

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=87psy31xz0.fsf@xs4all.nl \
    --to=lute.kamstra.lists@xs4all.nl \
    --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).