unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: call1 (Vrun_hooks, ...) instead of Frun_hooks?
Date: Wed, 07 Apr 2010 20:36:45 -0600	[thread overview]
Message-ID: <hpjfft$a7u$1@dough.gmane.org> (raw)
In-Reply-To: <4BBD31C9.6070405@censorshipresearch.org>

Daniel Colascione wrote:
> In minibuf.c, why is it
> 
>  call1 (Vrun_hooks, Qminibuffer_setup_hook)
> 
> instead of Frun_hooks(1, &Qminibuffer_setup_hook) ?

 From eval.c:


/* This holds either the symbol `run-hooks' or nil.
    It is nil at an early stage of startup, and when Emacs
    is shutting down.  */

Lisp_Object Vrun_hooks;

-- 
Kevin Rodgers
Denver, Colorado, USA





      reply	other threads:[~2010-04-08  2:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08  1:30 call1 (Vrun_hooks, ...) instead of Frun_hooks? Daniel Colascione
2010-04-08  2:36 ` Kevin Rodgers [this message]

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='hpjfft$a7u$1@dough.gmane.org' \
    --to=kevin.d.rodgers@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 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).