Hi > On 12 nov 2008, at 03.20, Yee Keat Phuah wrote: > > Hi Anton, > > Have you tried using the jde-eclipse-compiler-server.el module > straight? I used that previously and I do not encounter the "hang > emacs for very strange reasons" as reported by the credmp.org article.
Just tried jde-eclipse-compiler-server.el, downloaded from: http://www.emacswiki.org/emacs/jde-eclipse-compiler-server.el With patch to fix classpath problem: http://osdir.com/ml/emacs.jdee/2007-12/msg00006.html > My only complain with that is that it will highlight/underline the > whole line of the error instead of only the parts that causes the > compilation error. I made a small .el file for my own to fix that. > > FYI, I use the first painfully slow but robust method > jde-ecj-flymake-init as stated in the jde-eclipse-compiler-server.el > module. Try that method first before moving in to the 2nd method, as > the 2nd method was giving me some problems as well because it uses the > same BSH session as JDE. > > Cheers, > Phuah Yee Keat With jde-ecj-flymake-init It seems to work just as well as before. But the problem still exists, after some kind of jde-error, in this case trying to invoke an ant target that doesn't exist, flymake will stop working. It still logs like before: %sstarting syntax check as more than 1 second passed since last change %sflymake is running: nil %sfile /Users/anton/Documents/skola/apjava/lab1/src/MyToolbox.java, init=jde-ecj-flymake-init Should "%sflymake is running: nil" be something else if it works correctly? I've seen it can still be nil at times when everything works fine... The trace from the error: Debugger entered--Lisp error: (error "Moved past last error") signal(error ("Moved past last error")) error("Moved past last %s" "error") compilation-next-error(1 nil 1) compilation-next-error-function(1 nil) next-error(1) jde-compile-finish-kill-buffer(#<buffer *compilation*> "exited abnormally with code 1\n") run-hook-with-args(jde-compile-finish-kill-buffer #<buffer *compilation*> "exited abnormally with code 1\n") #[(buf msg) "ÃÄ #Å" [buf msg compilation-finish-function run- hook-with-args jde-ant-build-hook nil] 4](#<buffer *compilation*> "exited abnormally with code 1\n") compilation-handle-exit(exit 1 "exited abnormally with code 1\n") compilation-sentinel(#<process compilation> "exited abnormally with code 1\n") Can you see anywhere in this trace that some process or something vital for flymake is killed? I've tried to follow the trace but can't find (don't understand) the problem. Could it have something to do with jde-compile-finish-kill-buffer? I appreciate any help I can get, really like flymake and would like it to work continuously, or in worst case I would at least be able to restart it in some other way than restarting emacs. Best Regards Anton ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ jdee-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jdee-users
