From: Didier Verna <didier@xemacs.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: The type of gnus-ignored-from-addresses
Date: Wed, 25 Apr 2007 12:04:59 +0200 [thread overview]
Message-ID: <muxodlc22ic.fsf@uzeb.lrde.epita.fr> (raw)
In-Reply-To: <b4mlkgg98zt.fsf@jpl.org> (Katsumi Yamaoka's message of "Wed\, 25 Apr 2007 17\:03\:02 +0900")
Katsumi Yamaoka <yamaoka@jpl.org> wrote:
>> But gnus-util is a special case because it doesn't 'require
>> any other part of Gnus[1]; it's really a utility library.
>
> I don't think so.
>
> ;;; gmm-utils.el --- Utility functions for Gnus, Message and MML
> ;;; gnus-util.el --- utility functions for Gnus
> ;;; mm-util.el --- Utility functions for Mule and low level things
Again, you're not very clear. OK, so there are 3 special cases.
Are you suggesting that gnus-orify-regexp would be better placed in
gmm-utils (since both Message and Gnus could use it) ?
>> Sorry, I don't understand this paragraph. Are you suggesting
>> that I put an autoload cookie on gnus-orify-regexp instead of
>> requiring gnus-util ? That would only merely delay the time of
>> loading gnus-util.
>
> No. I'd suggest replacing `(require 'gnus-util)' with:
>
> (eval-and-compile
> (autoload 'gnus-orify-regexp "gnus-util")
> )
>
> The most suitable place to put it seems to be around the 1777th
> line in message.el. You will see a lot of autoloads there.
I agree, but see above though.
--
Read the Jazz Blog !! http://jazzblog.didierverna.com
Didier Verna, didier@lrde.epita.fr, http://www.lrde.epita.fr/~didier
EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (1) 44 08 01 85
94276 Le Kremlin-Bicêtre, France Fax.+33 (1) 53 14 59 22 didier@xemacs.org
next prev parent reply other threads:[~2007-04-25 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 13:50 Didier Verna
2007-04-24 23:49 ` Katsumi Yamaoka
2007-04-25 7:21 ` Didier Verna
2007-04-25 8:03 ` Katsumi Yamaoka
2007-04-25 10:04 ` Didier Verna [this message]
2007-04-25 11:10 ` Katsumi Yamaoka
2007-04-26 20:39 ` Reiner Steib
2007-04-27 4:00 ` Miles Bader
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=muxodlc22ic.fsf@uzeb.lrde.epita.fr \
--to=didier@xemacs.org \
--cc=ding@gnus.org \
--cc=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).