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

[-- Attachment #1: Type: text/plain, Size: 1904 bytes --]

* Steven E Harris <seh@panix.com> writes:

  > Steve Youngs <sryoungs@bigpond.net.au> writes:
  >> Why don't you just install Gnus to the default location?

  > For years, I was running an XEmacs in a location that I didn't have
  > write permission to, so I got in the habit of keeping my local
  > packages (including Gnus CVS builds) under my home directory. I chose
  > ~/usr/local/ as the root to feed to the Gnus 'configure' script and it
  > came up with ~/usr/local/lib/xemacs/site-packages as the root for
  > Gnus.

OK, that's fair enough.

  >> Or configure Gnus to install under ~/.xemacs/site-packages ?

  > Well, now I'd consider doing that, but I jumped in on this thread
  > because I didn't know about these special directories under ~/.xemacs
  > that would enable the autoload behavior. You explained how they're
  > supposed to work, and I've been trying to convince myself (and you in
  > the process) that these directories are not inspected with my current
  > Cygwin XEmacs 21.4.13. It's a good idea. I just wished it worked here.

I'm at a loss.  It should _just work_.  I'll see if I can find the
answer for you, but in the meantime just use this...

(let* ((gnusdir (file-name-as-directory
		 (expand-file-name 
		  "usr/local/lib/xemacs/site-packages/lisp/gnus"
		  (getenv "HOME"))))
       (autos (expand-file-name "auto-autoloads.elc" gnusdir))
       (customs (expand-file-name "custom-load.elc" gnusdir)))
  (setq load-path (push gnusdir load-path))
  (when (file-exists-p autos)
    (load-file autos))
  (when (file-exists-p customs)
    (load-file customs)))

And keep installing Gnus in the way/place you are used to.

-- 
|---<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-12 22:25 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
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 [this message]

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.87eku4reh7.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).