From: Steve Youngs <sryoungs@bigpond.net.au>
Subject: Re: loading gnus creates *Group* buffer
Date: Fri, 09 Jan 2004 09:57:16 +1000 [thread overview]
Message-ID: <microsoft-free.87isjmf0yr.fsf@eicq.dnsalias.org> (raw)
In-Reply-To: <m3r7ybfbis.fsf@zsu.sush.org> (Istvan Marko's message of "Wed, 07 Jan 2004 17:56:59 -0800")
[-- Attachment #1: Type: text/plain, Size: 1947 bytes --]
|--==> "IM" == Istvan Marko <mi-gnus@imarko.dhs.org> writes:
IM> "Steven E. Harris" <seh@panix.com> writes:
>>Steve Youngs <sryoungs@bigpond.net.au> writes:
>>
>>>Why isn't your Gnus autoloading? Back in October last year I tweaked
>>>the build so `auto-autoloads.el' & `custom-load.el' are created when
>>>building with XEmacs. Isn't it working for you?
>>
>>I use a Gnus built from CVS and stored under ~/usr/local, so I don't
>>have the Gnus package installed. If I start up XEmacs without loading
>>Gnus explicitly, it doesn't know the functions `gnus' or
>>`gnus-no-server.' Should it? Does auto-autoloads.el provide these
>>functions?
IM> (require 'gnus-load) ; setup the gnus autoloads
In XEmacs, this shouldn't be needed because of auto-autoloads.el which
is loaded automatically at XEmacs start (providing it is in the
default load-path).
Another thing to consider...
(insert-file-contents (locate-library "gnus-load.el"))
(provide 'gnus-load)
;;; Local Variables:
;;; version-control: never
;;; no-byte-compile: t
;;; no-update-autoloads: t
;;; End:
;;; gnus-load.el ends here
It isn't going to load much. :-) Yes, I did this intentionally. The
best way to load Gnus in XEmacs is to have it installed in a default
package path [1], and then do nothing except start XEmacs.
Footnotes:
[1] In search order:
~/.xemacs/site-packages
~/.xemacs/mule-packages
~/.xemacs/xemacs-packages
<emacs-roots>/lib/xemacs/site-packages [2]
<emacs-roots>/lib/xemacs/mule-packages
<emacs-roots>/lib/xemacs/xemacs-packages
[2] This is the default if you don't give configure any path options
when building Gnus.
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| Ashes to ashes, dust to dust. |
| The proof of the pudding, is under the crust. |
|------------------------------<sryoungs@bigpond.net.au>---|
[-- Attachment #2: Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2004-01-08 23:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 3:07 Katsumi Yamaoka
2004-01-07 3:10 ` Lars Magne Ingebrigtsen
2004-01-07 3:14 ` Katsumi Yamaoka
2004-01-07 16:10 ` Steven E. Harris
2004-01-07 19:52 ` Steve Youngs
2004-01-07 21:17 ` Steven E. Harris
2004-01-07 23:24 ` Steve Youngs
2004-01-08 1:56 ` Istvan Marko
2004-01-08 23:11 ` Steven E. Harris
2004-01-08 23:57 ` Steve Youngs [this message]
2004-01-09 0:26 ` Steven E. Harris
2004-01-09 2:39 ` Steve Youngs
2004-01-11 21:41 ` Kai Grossjohann
2004-01-11 22:59 ` Steve Youngs
2004-01-11 23:17 ` Steven E. Harris
2004-01-12 0:00 ` Steve Youngs
2004-01-12 1:33 ` Steven E. Harris
2004-01-12 4:21 ` Steve Youngs
2004-01-12 17:40 ` Steven E. Harris
2004-01-12 22:25 ` Steve Youngs
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=microsoft-free.87isjmf0yr.fsf@eicq.dnsalias.org \
--to=sryoungs@bigpond.net.au \
/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).