Gnus development mailing list
 help / color / mirror / Atom feed
From: Steve Youngs <sryoungs@bigpond.net.au>
Subject: Re: loading gnus creates *Group* buffer
Date: Thu, 08 Jan 2004 09:24:23 +1000	[thread overview]
Message-ID: <microsoft-free.87hdz7gx5k.fsf@eicq.dnsalias.org> (raw)
In-Reply-To: <q67wu83e9vd.fsf@L75001820.us.ray.com> (Steven E. Harris's message of "Wed, 07 Jan 2004 13:17:58 -0800")


[-- Attachment #1.1: Type: text/plain, Size: 1296 bytes --]

|--==> "SEH" == Steven E Harris <seh@panix.com> writes:

  SEH> 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?

  SEH> I use a Gnus built from CVS and stored under ~/usr/local, so I
  SEH> don't have the Gnus package installed. If I start up XEmacs
  SEH> without loading Gnus explicitly, it doesn't know the functions
  SEH> `gnus' or `gnus-no-server.'

This is because the directory is getting added to the load-path
_after_ XEmacs processes the autoloads.

  SEH> Does auto-autoloads.el provide these functions?

Yes.

  SEH> I do add ~/usr/local/lib/xemacs/site-packages/lisp/gnus to my
  SEH> load-path in one of my init files, and that directory does
  SEH> contain auto-autoloads.el as you intended. Maybe I'm adding
  SEH> this directory to my load-path too late to work in concert with
  SEH> the autoload mechanism.

Yes.  And you wouldn't be able to add that directory to your load-path
soon enough because XEmacs processes the autoloads _before_ it loads
your `user-init-file'.  But don't worry, there are a few things that
you could do to work around it...

Solution #1:
-----------

[-- Attachment #1.2: Type: application/x-emacs-lisp, Size: 415 bytes --]

[-- Attachment #1.3: Type: text/plain, Size: 1133 bytes --]

----

Solution #2:
-----------
When building Gnus...

./configure \
  --infodir=/home/you/.xemacs/site-packages/info \
  --with-lispdir=/home/you/.xemacs/site-packages/lisp/gnus \
  --with-etcdir=/home/you/.xemacs/site-packages/etc/gnus

This will install Gnus under ~/.xemacs/site-packages/ and you won't
have to add anything to your load-path because that directory is one
of the ones that XEmacs searches automatically.
----

Solution #3:
-----------
When building XEmacs...

./configure \
  --package-path=/home/you/usr/local/lib/xemacs/site-packages
----

Solution #4:
-----------
Install Gnus to the default location
(/usr/local/lib/xemacs/site-packages) by _not_ specifying any
directory related configure options.  You won't have to add any
directories to your load-path with this solution either.

Obviously, this solution requires write access to that directory.
----

HTH.

-- 
|---<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 --]

  reply	other threads:[~2004-01-07 23:24 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 [this message]
2004-01-08  1:56       ` Istvan Marko
2004-01-08 23:11         ` Steven E. Harris
2004-01-08 23:57         ` Steve Youngs
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.87hdz7gx5k.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).