Raymond Toy <toy(a)rtp.ericsson.se> writes:
> sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes:
>
> > Let's say I've run a compile already, and want to do it again via
> > the popup menu. However, the current buffer is different from the
> > *compilation* buffer. The new compilation assumes the
> > default-directory of the current buffer, which is bad
> > juju---especially if I'm doing a recompile which should do exactly
> > the same thing as the last time around. This is really annoying.
>
> I also find it rather annoying that when I run compile again, it
> removes the window and then creates it again. This didn't happen in
> the previous beta: It just left the compilation buffer wherever it
> was and just cleared the contents.
>
> I find the window deletion/creation visually annoying.
This might be my fault. However, I am unable to repeat it. For me,
the window is not deleted.
If you wish to debug this, `save-some-buffers' is a good place to
look. I believe the current setup of that function is correct, but I
may have overlooked something.
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Manic depression is cool... your body can make its own drugs.