Gary <[email protected]> writes: > Thanks. Yes, that fixes the EmacsW32 problem. I'll see if I can debug > into the problem in my other emacs tomorrow, but meanwhile the > backtrace is: > > Debugger entered--Lisp error: (error "Process bsh not running") > process-send-string(#<process bsh> > "jde.util.CompileServer.compile(new String[] > > {\"/home/gary/src/learn-jdee/src/One.java\",\"-classpath\",\"/home/gary/src/learn-jdee/src;/home/gary/src/learn-jdee/src/C:\\Programme\\Java\\jre1.5.0_12\\lib\\ext\\QTJava.zip\"});\n")
> (Just quickly looking at that, it isn't something to do with the mixed > cygwin and Windows paths, is it? I wouldn't expect Java to understand > /home/gary/... for example. Have I forgotten to configure something?) You can't expect W32 Java to understand cygwin paths, no. In general, mixin cygwin and "normal" W32 applications is a Pandora's box of special cases and brokenness. You're probably better off scrapping cygwin emacs and using EmacsW32 exclusively. :( Either that, or switch to Linux on the desktop. :) In any case: Your real problem is that the bsh process isn't starting. Try looking at the contents of the *JDEE bsh* buffer; that may give you some hints. -- Espen Wiborg <[email protected]> - Veritas vos liberabit Thermodynamics in a nutshell: 1st Law: You can't win. (Energy is conserved) 2nd Law: You can't break even. (Entropy) 0th Law: You can't even quit the game. (Closed systems) -- C.P. Snow ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ jdee-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jdee-users
