>>>>> "Brad" == Brad Giaccio <[EMAIL PROTECTED]> writes:
Brad> Alright I'm not sure what is going on here. I tried something
Brad> simple started up xemacs went to a java buffer moved my point
Brad> over "System" typed C-c C-v C-h, I see starting bsh, then as
Brad> usual I get the End of Stream error. When bsh starts I see
Brad> BeanShell 0.96 beta - by Pat Niemeyer ([EMAIL PROTECTED]) (list
Brad> "java.lang.System") bsh %
Brad> meaning the call eventually got processed and it found it. Now
Brad> with both buffers visible I try again. and I get Cannot find
Brad> documentation for System but nothing ever happens in bsh. It
Brad> is like it never tries to call it again.So I try a different
Brad> word, and it comes back equally as quicklly. Any thoughts on
Brad> what to do here I'm running xemacs21.0 on solaris.
Brad> I don't know that you need my .emacs, but I'm not using
Brad> project files just my .emacs and yes I did set the
Brad> javadoc-dirs through customize.
Well you shouldnt see anything in the bsh shell. Although this
buffer is being used to evaluate things its being done in the
background as it were, with all the content being whiped away by the
JDE as it were.
Id suggest that you try the following. Into the *scratch* buffer
type
(bsh-eval-r "jde.util.JdeUtilities.getQualifiedName( \"System\" );" )
and evaluate this (put point after the close bracket, and type
C-x C-e). You should get ( "java.lang.System" ) in the minibuffer
(plus all the stuff about starting bsh, and loading mule-util the
first time).
If you dont then the problem is between the
interprocess communication between emacs, and bsh. I dont know how to
fix that but at least you'll know where the problem is.
The "cannot find documentation" is coming from the lisp. This
doesnt entirely tally with the idea that the problem is bsh, which I
would expect to give a "Cannot find System" error, rather than cant
find documentation. I suggest you therefore evaluate this in *scratch*
(jde-help-get-javadoc "java.lang.System" )
which is the function which works out where the documentation
file is. When I evaluate it I get
"f:/zips/docs.zip/api/java/lang/System.html"
in the documentation. Clearly it will vary for you. It may
even be nil if emacs cant find the file, and again we're a little
closer to the problem.
Phil
