>When I use 'jde-import-find-and-import' in ECB with a compile window, the >prompt window that asks for clarification pops up in the compilation buffer. >This is fine. But then, it doesn't have an idea where to put the import >statement. Is there a setting in JDE/ECB that I can tweak to correct this?
Hmm, not easy i think. After taking a short look into the efc.el library of JDEE i saw that thsi library is not very flexible, i.e. it calls for example `delete-window' after calling efc-dialog-ok or efc-dialog-cancel. JDEE expects not running in another window-layout than the typical Emacs-layout where things like completion, help, compile etc...opens a new window at the bottom, display their stuff and are intended to be delete after use. efc.el seems to expect this too. IMHO not very flexible but on the other side i must admit i currently do not know any other and better and more flexible solution which allows correct working with every window-layout and therefore also with layouts which contain a durable window where all stuff like compile-output, help and also efc-dialogs are displayed. Such a window must not be deleted after efc-dialog-ok or efc-dialog-cancel. But how to achieve this goal?? If you use ECB without a compile-window all should work well but this is of course not the optimal solution. ECB advices currently already delete-window and other window-function so they work correct with ECB. Maybe ECB should try to be smart here: If delete-window is called for the compile-window then it does nothing, means it does not delete the window but behaves to the caller of delete-window as if the window has been deleted.... I must try this....maybe this could be a way to make ECB and JDEE working better in combination........................................ Klaus >Recreate Problem: >1. emacs -q >2. setup loadpaths >3. load jde, ecb >3. find asdf.java >4. customize ecb-layout to use a compilation window. >5. ecb-activate. >6. With "adsf.java" in edit window, and focus in same window, do >`jde-import-find-and-import' >7. Import "ParseException" class, choose any of the choices, click "ok" >8. Now the import statement is in my scratch buffer.
