Re: bug: closing of *compilation* buffer

Mon, 11 Nov 2002 07:31:29 -0800

The compilation buffer *vanishing* is a nice feature, except when running Ant tasks other than "compile".  Trying to see the output of a *run* (or other task), requires you to switch to the compilation buffer after it vanishes to view the output.  Which of course eats cycles.
 
Jeff
 
----- Original Message -----
Sent: Monday, November 11, 2002 9:38 AM
Subject: Re: bug: closing of *compilation* buffer

Michal Ceresna <[EMAIL PROTECTED]> writes:

You need to customize the variable jde-compile-finish-hook, and remove the
function jde-compile-finish-kill-buffer.  This will stop causing the
compilation buffer to vanish after a successful compilation.

Javier
> Hello,
>
> I usually organize the buffers as follows:
>
> +++++++++++
> +____+____+
> +____+____+
> +++++++++++
> +_________+
> +++++++++++
>
> the upper two buffers contain java sources, the lower
> one is the *compilation*.
>
> In last jdee versions, that I've tried (jde-2.2.9beta12,
> jde-2.2.9-stable) after calling jde-compile (C-c C-v C-c)
> in an upper buffer, the lower buffer always vanishes:
>
> +++++++++++
> +____+____+
> +____+____+
> +____+____+
> +____+____+
> +++++++++++
>
> So far I've been using jde-2.2.9beta9.1 where it worked fine.
>
> Linux Debian/unstable
> GNU Emacs 21.2.2
> JDEE 2.2.9
> eieio-0.17
> elib-1.0
> semantic-1.4
> speedbar-0.14beta4
>
> best wishes,
> Michal
> --
> Michal Ceresna, DBAI, TU Wien
>

--
Javier S. Lopez                
[EMAIL PROTECTED]            Forum Systems, Inc.
(781) 788-4206                  95 Sawyer St., Suite 110,
http://www.forumsys.com         Waltham, MA 02453

Reply via email to