From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Lisp indentation.
Date: Thu, 10 Mar 2005 14:43:34 -0500 [thread overview]
Message-ID: <jwvfyz3p9vh.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87mztbmk6r.fsf@xs4all.nl> (Lute Kamstra's message of "Thu, 10 Mar 2005 19:26:20 +0100")
> In about 25% of the cases the lisp-indent-hook property is used to
> specify the desired indentation and in the remaining 75% of the cases,
> the lisp-indent-function property is used. Is the second preferred?
> (The docsting of the function lisp-indent-function suggest this.)
> Should occurrences of lisp-indent-hook be renamed to
> lisp-indent-function?
Yes, although there is no urgency.
> In most cases the indentation property is put on the symbol at the
> place the symbol is defined. Symbols that are defined in C get their
> indentation property in lisp/emacs-lisp/lisp-mode.el. There are
> however a few symbols that are defined in lisp elsewhere that get
> their lisp-indent-function property set in lisp-mode.el. For example
> save-selected-window, save-match-data, and with-current-buffer. Is
> there some policy wrt the place where the indentation property should
> be set?
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.
Stefan
next prev parent reply other threads:[~2005-03-10 19:43 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 [this message]
2005-03-11 1:29 ` Lute Kamstra
2005-03-12 17:40 ` Lute Kamstra
2005-03-13 13:23 ` Lute Kamstra
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=jwvfyz3p9vh.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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).