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

Previous Next

Package: emacs;

Reported by: Christopher Schmidt <christopher <at> ch.ristopher.com>

Date: Mon, 27 Aug 2012 14:58:02 UTC

Severity: wishlist

Tags: patch

Found in version 24.2.50

Done: Christopher Schmidt <christopher <at> ch.ristopher.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Christopher Schmidt <christopher <at> ch.ristopher.com>
To: Martin Blais <blais <at> furius.ca>
Cc: 12288 <at> debbugs.gnu.org
Subject: bug#12288: 24.2.50; compilation-start: Query for killing existing compilation process only if query-on-exit-flag is non-nil
Date: Sat,  1 Sep 2012 16:29:01 +0100 (BST)
Martin Blais <blais <at> furius.ca> writes:
> 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).

This is exactly what I don't want.

Those processes that have a nil query-on-exit-flag should be killed by
compilation-start without a yes-or-no query.  A buffer-local non-nil
value for compilation-always-kill allows me to achieve that.

I still think a check for query-on-exit-flag in compilation-start is a
good idea.  Non-nil query-on-exit-flag and non-nil buffer-local
compilation-always-kill feels redundant, doesn't it?

        Christopher




This bug report was last modified 12 years and 310 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.