Re: Compiler window deletion - UI question/suggestion

2005-04-06 Thread Jeff Peck
Your fix will help; it enables one to unset jde-compile-enable-kill-buffer
to avoid the killing of the window.
However; what I want (and i suspect other's do as well), is to kill the
buffer,
but: Leave the window in place!

That way, when i have two edit windows, and compile in one window,
the compile results will show briefly in the second window, and then
(when all goes well) that second window will revert to the previously
visible buffer!

That way you do it, compile will either:
   a) leave the compile output showing where the second edit window was
   b) close the second edit window.
Neither of which is my expectation/intent.

If everyone else only expects one window per frame, and really wants to
close
the second/temporary compile output window, then maybe we should
make creative use of save-window-excursion, to restore the configuration?


   (defun jde-compile-kill-buffer (buf)
 (kill-buffer buf))
  



Re: Compiler window deletion - UI question/suggestion

2005-04-06 Thread Raul Acevedo
On Wed, 2005-04-06 at 14:24 -0700, Jeff Peck wrote:

 If everyone else only expects one window per frame, and really wants to
 close
 the second/temporary compile output window, then maybe we should
 make creative use of save-window-excursion, to restore the configuration?

That's what I do.  Starting a compilation saves the window
configuration, and in the hook when the compilation is done, I restore
it.  I need to tweak it so it doesn't restore the window configuration
if I've switched buffers around too much, but the idea is the same.

Raul



Java-1.5 font-lock support?

2005-04-06 Thread jeff peck
Is there a version of Java font-lock that supports Java-1.5?
To so something reasonable with Generics and varargs (Object... args)
and other 1.5-isms?