Gnus development mailing list
 help / color / mirror / Atom feed
From: NAKAJI Hiroyuki <nakaji@jp.freebsd.org>
To: ding@gnus.org
Subject: Re: void-function gnus-make-local-hook
Date: Tue, 12 Oct 2010 10:12:34 +0900	[thread overview]
Message-ID: <8662x8uscd.fsf@jimmy.4407.kankyo-u.ac.jp> (raw)
In-Reply-To: <b4m7hhtgobe.fsf@jpl.org> (Katsumi Yamaoka's message of "Fri, 08 Oct 2010 16:01:57 +0900")

>>>>> In <b4m7hhtgobe.fsf@jpl.org> 
>>>>>	Katsumi Yamaoka <yamaoka@jpl.org> wrote:
> NAKAJI Hiroyuki wrote:
> > I updated Emacs trunk and Gnus CVS head, and got an error, when
> > starting Gnus.

> > Debugger entered--Lisp error: (void-function gnus-make-local-hook)
> [...]

> Weird.  It's been existing in gnus-util.el for all the time
> because this function is necessary for XEmacs 21.4:

> (defalias 'gnus-make-local-hook (if (featurep 'xemacs)
>                                     'make-local-hook
>                                   'ignore))

Oops. My Gnus CVS tree is about half year old.

In my gnus-util.el got by 'cvs update -dP', it is:

;; The LOCAL arg to `add-hook' is interpreted differently in Emacs and
;; XEmacs.  In Emacs we don't need to call `make-local-hook' first.
;; It's harmless, though, so the main purpose of this alias is to shut
;; up the byte compiler.
(defalias 'gnus-make-local-hook
  (if (eq (get 'make-local-hook 'byte-compile)
          'byte-compile-obsolete)
      'ignore                           ; Emacs
    'make-local-hook))                  ; XEmacs

And, I don't know why, this returns "make-local-hook".

Retrieved gnus.git trunk and all work well. Thanks!
-- 
NAKAJI Hiroyuki



  reply	other threads:[~2010-10-12  1:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-08  6:45 NAKAJI Hiroyuki
2010-10-08  7:01 ` Katsumi Yamaoka
2010-10-12  1:12   ` NAKAJI Hiroyuki [this message]
2010-10-12  5:52     ` Steinar Bang
2010-10-13  2:45       ` NAKAJI Hiroyuki

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=8662x8uscd.fsf@jimmy.4407.kankyo-u.ac.jp \
    --to=nakaji@jp.freebsd.org \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).