From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Emacs Devel <emacs-devel@gnu.org>
Subject: Doc string for run-hooks
Date: Sat, 05 Jan 2008 20:03:10 +0100 [thread overview]
Message-ID: <477FD46E.5000807@gmail.com> (raw)
I believe I suggested something like this change to the doc string a
year ago. Was not that accepted? (Not entirely sure. It has not been
entered in CVS.)
===================================================================
RCS file: /cvsroot/emacs/emacs/src/eval.c,v
retrieving revision 1.276
diff -u -r1.276 eval.c
--- src/eval.c 21 Jan 2007 04:18:16 -0000 1.276
+++ src/eval.c 18 Feb 2007 19:58:07 -0000
@@ -2493,18 +2493,20 @@
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.
+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 should be a list of functions. The functions in the
+list are called in order, with no arguments.
+
+A hook symbols' value can also be a single function which
+`run-hooks' calls. But this usage is obsolete.
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)
int nargs;
reply other threads:[~2008-01-05 19:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=477FD46E.5000807@gmail.com \
--to=lennart.borgman@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.