From: Amos Gouaux <amos+lists.ding@utdallas.edu>
Subject: Re: Autoloads no longer working?
Date: Sun, 05 May 2002 10:22:31 -0500 [thread overview]
Message-ID: <m2662262mg.fsf@utdallas.edu> (raw)
In-Reply-To: <Pine.GSO.4.44.0204301041070.10476-100000@spartacus.utdallas.edu> (amos+lists.ding@utdallas.edu's message of "Tue, 30 Apr 2002 10:58:11 -0500 (CDT)")
>>>>> On Tue, 30 Apr 2002 10:58:11 -0500 (CDT),
>>>>> lists ding <amos> (ld) writes:
ld> On Tue, 23 Apr 2002, Andreas Fuchs wrote:
>> Actually, I noticed that these happen before the ~/.gnus gets loaded: I
>> only get these messages:
>>
>> ,----
>> | Loading gnus...
>> | eval: Symbol's function definition is void: mm-guess-mime-charset
>> `----
Surely I'm not the only one to run CVS Gnus with CVS Emacs, right?
Do y'all replace the gnus that's bundled with Emacs? Then again, I
don't recall encountering this difficulty before. Anyway, this
seems to allow me to fiddle with beta yet leave the bundled alone.
Maybe there's a better way to do this? I'm concerned that I may
not be unloading everything I need to, or maybe unloading too
much. Perhaps gnus-load.el should have an option to do an unload
of each feature it encounters while gnus-load.el is being built?
(add-to-list 'load-path
(expand-file-name "~/elisp/apps/gnus/lisp/"))
(add-to-list 'Info-default-directory-list
(expand-file-name "~/elisp/apps/gnus/texi/"))
(dolist (feature features)
(if (string-match "^\\(gnus-\\|nn\\|mm-\\|mml-\\|rfc\\|message\\)"
(symbol-name feature))
(unload-feature feature 'force)))
(require 'gnus-load)
Hmm... this still isn't quite right. When I tried to post I got:
Sending...
message-send-mail: Symbol's function definition is void: mml-buffer-substring-no-properties-except-hard-newlines
Maybe this will work after load-library of mml....
next prev parent reply other threads:[~2002-05-05 15:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 10:05 Andreas Fuchs
2002-04-23 13:43 ` Kai Großjohann
2002-04-23 15:04 ` Andreas Fuchs
2002-04-23 15:29 ` Kai Großjohann
2002-04-24 15:54 ` Andreas Fuchs
2002-04-24 16:08 ` Paul Jarc
2002-04-24 18:21 ` Kai Großjohann
2002-04-25 10:24 ` Andreas Fuchs
2002-04-26 3:01 ` Manoj Srivastava
2002-04-26 8:11 ` Andreas Fuchs
2002-04-26 9:57 ` Manoj Srivastava
2002-04-26 13:00 ` Andreas Fuchs
2002-04-26 13:32 ` Kai Großjohann
2002-04-26 13:56 ` Andreas Fuchs
2002-04-26 15:01 ` Kai Großjohann
2002-04-26 16:53 ` Andreas Fuchs
2002-04-26 18:22 ` Kai Großjohann
2002-04-27 16:14 ` Andreas Fuchs
2002-04-26 17:11 ` Harry Putnam
2002-04-27 22:59 ` Paul Jarc
2002-04-28 12:07 ` Kai Großjohann
2002-04-28 17:43 ` Paul Jarc
2002-04-26 8:12 ` Andreas Fuchs
2002-04-26 9:48 ` Kai Großjohann
2002-04-26 8:23 ` Kai Großjohann
2002-04-26 9:32 ` Manoj Srivastava
2002-04-30 15:58 ` amos+lists.ding
2002-04-30 19:45 ` Amos Gouaux
2002-05-05 15:22 ` Amos Gouaux [this message]
2002-05-05 15:39 ` Kai Großjohann
2002-05-05 21:45 ` Amos Gouaux
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=m2662262mg.fsf@utdallas.edu \
--to=amos+lists.ding@utdallas.edu \
/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).