Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Knauel <knauel@informatik.uni-tuebingen.de>
Subject: Gnus 5.8.3 installation question
Date: 05 Feb 2000 09:29:47 +0100	[thread overview]
Message-ID: <m3ln50gih0.fsf@thor.dynip.com> (raw)


Hi,

I have an installation of Gnus 5.6.45 for my XEmacs (RedHat Linux 6.1) 
that works fine. However, I would like to upgrade to 5.8.3.

After doing a "make install" things tend to become strange. ;) I moved 
my old lisp/gnus directory to some place where XEmacs won't find it
and put the following lines into my ~/.emacs:

(setq load-path (cons (expand-file-name "/usr/local/gnus/lisp") load-path))
(setq debug-on-error t)

After statint XEmacs and typing M-x gnus this happens:

Signaling: (void-function gnus) gnus() #<compiled-function nil
"...(49)" [toolbar-news-use-separate-frame gnus frame-live-p
toolbar-news-frame make-frame toolbar-news-frame-plist add-hook
gnus-exit-gnus-hook #<compiled-function nil "...(18)" ... 2>
select-frame framep frame-iconified-p deiconify-frame raise-frame] 3
935138 nil>() call-interactively(toolbar-gnus) #<compiled-function nil
"...(27)" [toolbar-news-reader toolbar-news-commands-alist command
error "Unkown news reader %s" call-interactively eval] 4 935183 nil>()
call-interactively(toolbar-news)
release-and-activate-toolbar-button(#<buttonup-event button1up>)
call-interactively(release-and-activate-toolbar-button)

Well, it seems that I simply don't have these functions, I did a fgrep 
on my lisp-dir... Where do I get them? Or is there something wrong
with my XEmacs? ;) Thanks in advance!

Ciao,
     Eric
-- 
E-Mail: knauel@informatik.uni-tuebingen.de  eric@macnews.de
  http://www-pu.informatik.uni-tuebingen.de/users/knauel



                 reply	other threads:[~2000-02-05  8:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=m3ln50gih0.fsf@thor.dynip.com \
    --to=knauel@informatik.uni-tuebingen.de \
    /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).