From: Richard Stallman <rms@gnu.org>
Cc: kfogel@red-bean.com, emacs-devel@gnu.org
Subject: Re: [PATCH] allow function values for `enable-local-eval'
Date: Thu, 4 Jul 2002 01:06:45 -0600 (MDT) [thread overview]
Message-ID: <200207040706.g6476jR05459@aztec.santafe.edu> (raw)
In-Reply-To: <5xk7odesic.fsf@kfs2.cua.dk> (storm@cua.dk)
;;; eval: (put 'ediff-defvar-local 'lisp-indent-hook 'defun)
;;; eval: (put 'ediff-with-current-buffer 'lisp-indent-hook 1)
;;; eval: (put 'ediff-with-current-buffer 'edebug-form-spec '(form body))
I don't think `put' should be a safe-local-eval-function, but maybe
it is ok to allow 'edebug-form-spec in addition to 'lisp-indent-hook ?
It is ok, but meanwhile there is now a way to specify these things in
the macro definition. Maybe we should change this to use that mechanism
instead.
Kifer, would you like to do that? Is there a difficulty with doing
that?
** The `defmacro' form may contain declarations specifying how to
indent the macro in Lisp mode and how to debug it with Edebug. The
syntax of defmacro has been extended to
(defmacro NAME LAMBDA-LIST [DOC-STRING] [DECLARATION ...] ...)
DECLARATION is a list `(declare DECLARATION-SPECIFIER ...)'. The
declaration specifiers supported are:
(indent INDENT)
Set NAME's `lisp-indent-function' property to INDENT.
(edebug DEBUG)
Set NAME's `edebug-form-spec' property to DEBUG. (This is
equivalent to writing a `def-edebug-spec' for the macro.
next prev parent reply other threads:[~2002-07-04 7:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E17NLww-0005Cn-00@floss>
2002-06-28 17:41 ` [PATCH] allow function values for `enable-local-eval' Richard Stallman
[not found] ` <87u1nnnqlp.fsf@floss.i-did-not-set--mail-host-address--so-shoot-me>
2002-06-29 0:55 ` Kim F. Storm
2002-06-29 22:22 ` Richard Stallman
2002-06-30 21:37 ` Kim F. Storm
2002-07-01 14:10 ` Richard Stallman
2002-07-01 21:26 ` Kim F. Storm
2002-07-02 19:46 ` Richard Stallman
2002-07-02 20:11 ` Stefan Monnier
2002-07-02 21:49 ` Kim F. Storm
2002-07-04 7:07 ` Richard Stallman
2002-07-04 15:28 ` Stefan Monnier
2002-07-04 19:38 ` Kim F. Storm
2002-07-04 18:46 ` Stefan Monnier
2002-07-04 21:58 ` Kim F. Storm
2002-07-05 1:26 ` Miles Bader
2002-07-05 13:39 ` Kai Großjohann
2002-07-04 19:36 ` Kim F. Storm
2002-07-05 22:05 ` Richard Stallman
2002-07-02 21:20 ` Kim F. Storm
2002-07-04 7:06 ` Richard Stallman [this message]
2002-07-04 15:13 ` Stefan Monnier
2002-07-05 10:48 ` Richard Stallman
2002-07-03 1:28 ` Kevin Ryde
2002-06-29 22:22 ` Richard Stallman
[not found] ` <877kkhlmgw.fsf@floss.i-did-not-set--mail-host-address--so-shoot-me>
2002-07-01 14:10 ` 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=200207040706.g6476jR05459@aztec.santafe.edu \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.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 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).