Re: bsh-compilation-buffer error message upon starting emacs

Sunnan <[email protected]> Wed, 23 May 2007 11:45:02 +0200
Newsgroups gmane.emacs.jdee
Message-ID <[email protected]>
On 5/22/07, Carlos Konstanski <[email protected]> wrote:
> On Tue, 22 May 2007, Sunnan wrote:
> > Hi, I'm using jde and everything worked fine, but I must've borked it
> > somehow and I  don't know how to trouble shoot. Any idea on where to
> > start looking? This is what I get when starting emacs.
> >
> > An error has occurred while loading `/home/sunnan/.emacs':
> >
> > error: "Given parent class bsh-compilation-buffer is not a class"
> > n
>
> Go into your /usr/share/emacs/site-lisp directory as root, and then
> run:
>
> grep -nr -e 'bsh-compilation-buffer' *
>
> You'll find that jde-compile.el, beanshell.el, and jde.el contain this
> text.  Something is calling into this code from your .emacs file.
>
> Do you have the emacs debugger turned on?  Or can you launch emacs
> with the --debug-init switch?  A backtrace would be helpful here.

This is all I get:
Debugger entered--Lisp error: (error "Given parent class
bsh-compilation-buffer is not a class")
  signal(error ("Given parent class bsh-compilation-buffer is not a class"))
  error("Given parent class %s is not a class" bsh-compilation-buffer)
  eieio-defclass(jde-compile-server-buffer (bsh-compilation-buffer)
nil ("Compiler server buffer."))
  require(jde-compile)
  eval-buffer(#<buffer  *load*<2>> nil "jmaker" nil t)
  load-with-code-conversion("/home/sunnan/Program/elisp/jmaker.el"
"jmaker" nil t)
  require(jmaker)
  eval-buffer(#<buffer  *load*> nil "~/.emacs" nil t)
  load-with-code-conversion("/home/sunnan/.emacs" "~/.emacs" t t)

So I figure that commenting out
(require 'jmaker)
(require 'jde-eclipse-compiler-server)
in my .emacs would let me start emacs. The weird thing is that doing
that, and then re-requiring them after I've started emacs and loaded
jde-mode works.

So I added (require 'jde) and now everything works again!
Thanks for getting me started!
(You know, it actually says "Start Emacs with the `--debug-init'
option to view a complete error backtrace"... I feel pretty dumb now.)