Gnus development mailing list
 help / color / mirror / Atom feed
From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Problem with the latest CVS build
Date: 06 Dec 1999 10:48:27 -0500	[thread overview]
Message-ID: <ltln78yss4.fsf@asfast.com> (raw)
In-Reply-To: Gunnar Evermann's message of "06 Dec 1999 10:33:54 +0000"

Gunnar Evermann <ge204@eng.cam.ac.uk> writes:

> Lloyd Zusman <ljz@asfast.com> writes:
> 
> > Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> > 
> > > Lloyd Zusman <ljz@asfast.com> writes:
> > > 
> > > > [ ... ]
> > > 
> > > Why don't you install the normal Gnus package and then add the CVS
> > > Gnus?  Just put the CVS Gnus directory first in load-path, and Bob
> > > will be your uncle.
> > 
> > I have done exactly that, but the standard building procedure that
> > gets downloaded with CVS doesn't know about my normal load path, and
> > it can't find mailheader in the load path that *it* tries to use.
> 
> 
> strange, can you post the output of something like:
>   xemacs -batch -q -no-site-file -eval '(print load-path)' | tr ' ' '\n' | grep gnus
> 
> 
> I get:
> "/home/tigger3/ge204/.xemacs/xemacs-packages/lisp/pgnus-cvs/"
> "/tools/emacs/lib/xemacs/xemacs-packages/lisp/gnus/"

I get this:


Yes, no output.  That's because there's nothing Gnus-like in my
load-path.  And now I think I understand what Kai Großjohann meant
when he said (above) to "... install the normal Gnus package ...".  He
did *not* mean to simply install Gnus-5.8.x in my local area that gets
pointed to the `load-path' that I set in my `.emacs', which is what I
have been doing for over a year.  What he *did* mean was to do an
official XEmacs package installation of the Gnus package.  I'm pretty
sure that once I do this, I'll have what I need in my load-path when I
do the CVS build ... correct?

So ... in order for the CVS build to work, the standard XEmacs Gnus
package that it replaces has to be installed, and at least one file
that was explicitly removed from the CVS build (namely
`mailheader.el') needs to be referenced from the standard Gnus build
that the CVS build is supposed to supersede.

But something seems wrong about this: what happens once the CVS build
finally becomes the official Gnus build?  Then, there won't be any
`mailheader.el' anywhere, which means that Gnus as written today wouldn't
work under XEmacs ... right?

So therefore, either `mailheader.el' needs to become part of the CVS
build once again, or else it has to become part of some other
installable XEmacs package, or else Gnus needs to be rewritten so as
not to need `mailheader.el' at all.


But anyway, thanks very much.  Your question about `load-path' helped
me to see what I have to do to get my CVS working for the short term.


> [ ... ]

-- 
 Lloyd Zusman
 ljz@asfast.com


  reply	other threads:[~1999-12-06 15:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-04  8:12 Daniel Pittman
1999-12-04  8:31 ` Lars Magne Ingebrigtsen
1999-12-04  8:40   ` Daniel Pittman
1999-12-04  9:02     ` Shenghuo ZHU
1999-12-04 11:18       ` Mike Fabian
1999-12-04 13:27       ` William M. Perry
1999-12-05  0:21         ` Dave Love
1999-12-05  0:19       ` Dave Love
1999-12-05  1:45       ` Lloyd Zusman
1999-12-05  8:38         ` Hans de Graaff
1999-12-05 18:28           ` Lloyd Zusman
1999-12-05 18:41             ` Lloyd Zusman
1999-12-05 21:02               ` Hans de Graaff
1999-12-06 17:44                 ` Hrvoje Niksic
1999-12-06 19:13             ` Jan Vroonhof
     [not found]             ` <ltr9h1s01u.fsf@ <byhfhvubli.fsf@urysohn.math.ethz.ch>
1999-12-07  8:20               ` Hrvoje Niksic
1999-12-07 12:27             ` Jan Vroonhof
1999-12-05 22:58         ` Kai Großjohann
1999-12-05 23:03           ` Lloyd Zusman
1999-12-05 23:24           ` Lloyd Zusman
1999-12-06 10:33             ` Gunnar Evermann
1999-12-06 15:48               ` Lloyd Zusman [this message]
1999-12-06 22:42                 ` Kai Großjohann

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=ltln78yss4.fsf@asfast.com \
    --to=ljz@asfast.com \
    /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).