Hmmm,
I took a look at it again, and you're right...

It seems that there is more code being run after the
jde-mode-hook (that's where I do 
(remove-hook 'jde-ant-build-hook 'jde-compile-finish-kill-buffer)
that adds the function to the hook again.

What I do now is remove the hook from my project file
and that does work.

Hth,
Christian


> -----Ursprüngliche Nachricht-----
> Von: Raul Acevedo [mailto:[EMAIL PROTECTED]]
> Gesendet: Montag, 13. Januar 2003 22:07
> An: Schmitt, Christian (ext.)
> Betreff: AW: Buffer Kill
> 
> 
> That didn't seem to work...
> 
> Schmitt, Christian (ext.) wrote:
> 
>  > 
>  > -----Ursprüngliche Nachricht-----
>  > Von: Inger, Matthew [mailto:[EMAIL PROTECTED]]
>  > Gesendet: Freitag, 10. Januar 2003 19:14
>  > An: '[EMAIL PROTECTED]'
>  > Betreff: Buffer Kill
>  > 
>  > 
>  > > is there a way to turn off the buffer kill after 
> compilation completion? 
>  > > I've tried customizing the jde-compile-finish-hook 
> variable both with 
>  > > jde-set-variables and with custom-set-variables, but 
> neither one works. 
>  > > It's annoying if i have split buffer windows, then try 
> to compile one of 
>  > > the files, that it kills the completion buffer, and 
> unsplits the window 
>  > > automatically.  That is truly obnoxious, and i can't 
> seem to figure out
>  > how 
>  > > to turn it off. 
>  > 
>  > Try this: (remove-hook 'jde-ant-build-hook 
> 'jde-compile-finish-kill-buffer)
>  > 
>  > 
>  > Hth,
>  > Christian
> 

Reply via email to