From: Eli Zaretskii <eliz@gnu.org>
To: Tze Chian Kam <tze.chian.kam@gmail.com>
Cc: 71853@debbugs.gnu.org
Subject: bug#71853: 29.4; `kill-compilation` does not kill compilation process on Windows
Date: Sun, 30 Jun 2024 12:07:06 +0300 [thread overview]
Message-ID: <86plryhk91.fsf@gnu.org> (raw)
In-Reply-To: <CABodVWVHLEPKZ9W+-D5uo2d-YtvmrFJjawmOR2BjWOqeyUaJnw@mail.gmail.com> (message from Tze Chian Kam on Sun, 30 Jun 2024 12:57:11 +1000)
tags 71853 moreinfo
thanks
> From: Tze Chian Kam <tze.chian.kam@gmail.com>
> Date: Sun, 30 Jun 2024 12:57:11 +1000
>
> Steps to reproduce:
> 1) Open Emacs with `-q`.
> 2) Run a trivial file with an infinite loop with `M-x compile`
Please show the exact file you used as the compilation command,
because I cannot reproduce this with a few programs I tried, see
below.
> Expected outcome:
> Should be able to kill the process with `M-x kill-compilation` or
> `C-c C-k`.
>
> Actual outcome:
> `C-c C-k` is ignored and `M-x kill-compilation` is ran but does not
> stop the process.
I tried this with several commands and it worked for me with all of
them. Here are the commands I tried:
. sleep 20
. ping -t SOME-EXISTING-SITE
. a batch file which does this:
@echo off
:again
ping -n 1 SOME-EXISTING-SITE
sleep 60s
goto again
In all three cases, I get the same expected result in the
*compilation* buffer:
Compilation interrupt at Sun Jun 30 11:58:49, duration 4.44 s
(with the time and the "duration" values changing as appropriate).
So I suspect the problem is with some specific command/program or a
group of programs that behave in a specific way. Thus the request to
show which program you used in your case.
(Just to be sure: you typed "C-c C-k" from the *compilation* buffer,
yes? If you want to interrupt the compilation process from another
buffer, you need to invoke kill-compilation by name, via M-x.)
> For now, I have a workaround to advice `compile` to interactive mode
> (comint) and killing the process with `C-c C-\`. Is this a Windows
> problem or my setup?
Not clear yet; more info is needed.
next prev parent reply other threads:[~2024-06-30 9:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 2:57 bug#71853: 29.4; `kill-compilation` does not kill compilation process on Windows Tze Chian Kam
2024-06-30 9:07 ` Eli Zaretskii [this message]
[not found] ` <CABodVWXdfXUhjhJNb13hcndALq+7A+L8VBODod7vBbD77DW5Vg@mail.gmail.com>
2024-06-30 17:53 ` Eli Zaretskii
2024-07-01 2:53 ` Tze Chian Kam
2024-07-01 11:27 ` Eli Zaretskii
2024-07-02 6:26 ` Tze Chian Kam
2024-07-02 6:36 ` Tze Chian Kam
2024-07-02 12:43 ` Eli Zaretskii
2024-07-02 12:41 ` Eli Zaretskii
2024-07-03 3:26 ` Tze Chian Kam
2024-07-03 11:17 ` Eli Zaretskii
2024-07-04 4:30 ` Tze Chian Kam
2024-07-04 6:18 ` Eli Zaretskii
2024-07-20 9:50 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86plryhk91.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71853@debbugs.gnu.org \
--cc=tze.chian.kam@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).