Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: autoload variables
Date: Tue, 14 Nov 2006 16:24:36 +0900	[thread overview]
Message-ID: <b4m64di8p8r.fsf@jpl.org> (raw)
In-Reply-To: <b4my7qe8tww.fsf@jpl.org>

>>>>> In <b4my7qe8tww.fsf@jpl.org> Katsumi Yamaoka wrote:

>>> +;;;###autoload(when (fboundp 'custom-autoload) (custom-autoload 'gnus-select-method "gnus"))

[...]

> `custom-autoload' is not available in Emacs 21 and XEmacs 21.4.
> I'll look for another way...

Er, that might be a stupid talk.  `(fboundp 'custom-autoload)'
means that we don't need to mind even if those who use old Emacs
cannot do `customize-variable' before loading Gnus, doesn't it?
If so, could you commit the new autoload?

In addition to this, it seems good to add `custom-autoload' to
lpath.el to silence old Emacsen:

--8<---------------cut here---------------start------------->8---
--- lpath.el~	2006-06-06 06:18:34 +0000
+++ lpath.el	2006-11-14 07:19:44 +0000
@@ -10,7 +10,7 @@
   (mapcar (lambda (var) (unless (boundp var) (set var nil))) args))
 
 (maybe-fbind '(Info-directory
-	       Info-menu create-image display-graphic-p
+	       Info-menu create-image custom-autoload display-graphic-p
 	       display-time-event-handler find-coding-system find-image
 	       image-size image-type-available-p insert-image
 	       make-mode-line-mouse-map make-network-process make-temp-file
--8<---------------cut here---------------end--------------->8---

Regards,



  reply	other threads:[~2006-11-14  7:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-13 11:27 Katsumi Yamaoka
2006-11-13 19:08 ` Reiner Steib
2006-11-14  1:31   ` Katsumi Yamaoka
2006-11-14  5:43     ` Katsumi Yamaoka
2006-11-14  7:24       ` Katsumi Yamaoka [this message]
2006-11-14 17:04         ` Reiner Steib

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=b4m64di8p8r.fsf@jpl.org \
    --to=yamaoka@jpl.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).