From: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>
Subject: run-hooks vs. run-mode-hooks.
Date: Wed, 25 May 2005 14:28:00 +0200 [thread overview]
Message-ID: <874qcro5gv.fsf@xs4all.nl> (raw)
Can somebody confirm that this change is correct?
Lute.
Index: src/eval.c
===================================================================
RCS file: /cvsroot/emacs/emacs/src/eval.c,v
retrieving revision 1.238
diff -C4 -r1.238 eval.c
*** src/eval.c 8 May 2005 16:30:13 -0000 1.238
--- src/eval.c 25 May 2005 12:25:23 -0000
***************
*** 2291,2306 ****
static Lisp_Object run_hook_with_args P_ ((int, Lisp_Object *,
enum run_hooks_condition));
DEFUN ("run-hooks", Frun_hooks, Srun_hooks, 0, MANY, 0,
! doc: /* Run each hook in HOOKS. Major mode functions use this.
Each argument should be a symbol, a hook variable.
These symbols are processed in the order specified.
If a hook symbol has a non-nil value, that value may be a function
or a list of functions to be called to run the hook.
If the value is a function, it is called with no arguments.
If it is a list, the elements are called, in order, with no arguments.
Do not use `make-local-variable' to make a hook variable buffer-local.
Instead, use `add-hook' and specify t for the LOCAL argument.
usage: (run-hooks &rest HOOKS) */)
(nargs, args)
--- 2291,2309 ----
static Lisp_Object run_hook_with_args P_ ((int, Lisp_Object *,
enum run_hooks_condition));
DEFUN ("run-hooks", Frun_hooks, Srun_hooks, 0, MANY, 0,
! doc: /* Run each hook in HOOKS.
Each argument should be a symbol, a hook variable.
These symbols are processed in the order specified.
If a hook symbol has a non-nil value, that value may be a function
or a list of functions to be called to run the hook.
If the value is a function, it is called with no arguments.
If it is a list, the elements are called, in order, with no arguments.
+ Major modes should not use this function directly to run their mode
+ hook; they should use `run-mode-hooks' instead.
+
Do not use `make-local-variable' to make a hook variable buffer-local.
Instead, use `add-hook' and specify t for the LOCAL argument.
usage: (run-hooks &rest HOOKS) */)
(nargs, args)
next reply other threads:[~2005-05-25 12:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 12:28 Lute Kamstra [this message]
2005-05-26 5:59 ` run-hooks vs. run-mode-hooks Richard Stallman
2005-05-27 0:58 ` Katsumi Yamaoka
2005-05-27 1:40 ` Lute Kamstra
2005-05-27 3:32 ` Katsumi Yamaoka
2005-05-27 8:01 ` Juanma Barranquero
2005-05-27 16:07 ` Stefan Monnier
2005-05-27 16:45 ` Drew Adams
2005-05-27 23:37 ` Juanma Barranquero
2005-05-27 14:20 ` Richard Stallman
2005-05-27 15:12 ` Lute Kamstra
2005-05-27 21:43 ` Miles Bader
2005-05-27 23:48 ` Katsumi Yamaoka
2005-05-30 6:45 ` Katsumi Yamaoka
2005-05-31 4:17 ` Richard Stallman
2005-05-28 11:52 ` 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=874qcro5gv.fsf@xs4all.nl \
--to=lute.kamstra.lists@xs4all.nl \
/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).