Gnus development mailing list
 help / color / mirror / Atom feed
From: Steve Youngs <sryoungs@bigpond.net.au>
Subject: Re: loading gnus creates *Group* buffer
Date: Mon, 12 Jan 2004 14:21:42 +1000	[thread overview]
Message-ID: <microsoft-free.87ptdpre3t.fsf@eicq.dnsalias.org> (raw)
In-Reply-To: <83r7y6lzlo.fsf@torus.sehlabs.com> (Steven E. Harris's message of "Sun, 11 Jan 2004 17:33:55 -0800")

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

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

  > Steve Youngs <sryoungs@bigpond.net.au> writes:
  >> Seems to work fine here.

  > It looks like you made ~/.xemacs/site-packages/lisp/gnus a symlink
  > rather than making ~/.xemacs/site-packages a symlink 

Only because I was too lazy to create the proper hierarchy at the
other end of the link.  It wouldn't make any difference, though.

  > Just to make sure we're talking about the same thing, I have:

  >   ~/.xemacs/site-packages/lisp/gnus

  >     symlinked to

  >   ~/usr/local/lib/xemacs/site-packages/lisp/gnus

  > The latter contains a working Gnus installation built from a recent
  > CVS snapshot. auto-autoloads.el(c) is there.

  > When I start up XEmacs as xemacs -q, I get

For reasons that I'm not sure of, when you start XEmacs like that you
won't get the package directories under $HOME/.xemacs in your
load-path. 

Try again, loading XEmacs normally.

  > $ file /home/seh/.xemacs/site-packages/lisp/gnus
  > => bash: file: command not found

That's Cygwin for ya.

  > Could this be a Cygwin problem? 

Oh, how I'd love to say "yes" here, alas, I honestly don't know
because I have never had anything to do with Cygwin.  It sits on top
of Windoze, so it is bound to be poorly designed and bug-ridden. :-)

  > Is there a variable (besides the obvious load-path) that I can
  > inspect to see if XEmacs includes ~/.xemacs/site-packages as part
  > of its initial path to find these autoload files?

 $ xemacs -debug-paths -kill > ~/xemacs-full-paths.out 2>&1

Whatever paths that XEmacs knows about on a normal start up will be in
~/xemacs-full-paths.out.

 $ xemacs -q -debug-paths -kill > ~/xemacs-q-paths.out 2>&1

Will tell you the paths that XEmacs knows about when started with
'-q'. 

OK, now I have to ask the question... Why don't you just install Gnus
to the default location?  Or configure Gnus to install under
~/.xemacs/site-packages ?

-- 
|---<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  4:21 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 [this message]
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.87ptdpre3t.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).