bug#12288: 24.2.50; compilation-start: Query for killing existing compilation process only if query-on-exit-flag is non-nil

[Martin Blais <blais@furius.ca>]

I'm not sure I understand. Let's recap a bit:

a. in 'compilation-start-hook, there's a hint that you can force the
   process-query-on-exit-flag on the compile process; that would presumably
   allow you to kill the buffer without a query, but not on a subsequent call to
   compile. (BTW I just tried the suggested hook as is and it doesn't work for
   me, but that's another issue).

b. compilation-always-kill can now be set to 't to suppress the query on another
   invocation to compile. Note that the new variable does not change the current
   behaviour, the default value is to ask. This should not affect what happens
   when you try to kill the buffer on a running process.

So I don't understand the question. Which of the events are you referring to?
(a) or (b)?  

And if (b), given that the variable does not change the behaviour, what do you
mean?





On Sat, Sep 1, 2012, at 06:58, Christopher Schmidt wrote:
> Christopher Schmidt <christopher@ch.ristopher.com> writes:
> > I find it annoying that compilation-start always asks before killing
> > the previous (running) compilation process.  I think
> > process-query-on-exit-flag should be taken into account here.
> 
> Revno 109813 introduces variable compilation-always-kill which, if
> non-nil, unconditionally removes the query for killing the compilation
> process.
> 
> This variable does not help me as occasionally I want to be asked
> whether I would like to kill the compilation process.
> 
> Can both compilation-always-kill and query-on-exit-flag be taken into
> account?
> 
>         Christopher