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 20:53:34 +0300 [thread overview]
Message-ID: <86zfr2fhb5.fsf@gnu.org> (raw)
In-Reply-To: <CABodVWXdfXUhjhJNb13hcndALq+7A+L8VBODod7vBbD77DW5Vg@mail.gmail.com> (message from Tze Chian Kam on Mon, 1 Jul 2024 01:58:30 +1000)
[Please use Reply All to reply, to keep the bug tracker CC'ed.]
> From: Tze Chian Kam <tze.chian.kam@gmail.com>
> Date: Mon, 1 Jul 2024 01:58:30 +1000
>
> > From: Eli Zaretskii
> > Date: Sun, 30 Jun 2024 12:07:06 +0300
> > Please show the exact file you used as the compilation command,
> > because I cannot reproduce this with a few programs I tried, see
> > below.
>
> Sorry, I used a Python file:
> ```
> import time
>
> while True:
> print("active")
> sleep(1)
> ```
And how exactly did you invoke this? Please show the complete command
you typed at the prompt of "M-x compile", because trying to reproduce
this (see below) I could't.
Also, can you interrupt the same program if you run it from the
Windows command prompt window and then type Ctrl-C?
I tried to run this program (without knowing how exactly did you do
that). Here's what I did:
. saved this program to a file loop.py
. in "emacs -Q" typed the Emacs command
M-x compile RET python loop.py RET
I then got an error:
python loop.py
active
Traceback (most recent call last):
File "loop.py", line 5, in <module>
sleep(1)
NameError: name 'sleep' is not defined
Compilation exited abnormally with code 1 at Sun Jun 30 20:47:35, duration 0.12 s
I then modified the program as follows:
import time
while True:
print("active")
time.sleep(1)
and ran the same compilation command again, then typed C-c C-k into
the compilation buffer. The result:
python loop.py
active
active
active
active
active
Traceback (most recent call last):
File "loop.py", line 5, in <module>
time.sleep(1)
KeyboardInterrupt
Compilation interrupt at Sun Jun 30 20:49:10, duration 4.37 s
which is what I would expect.
My Python is version 3.4.4, for native MS-Windows, installed from
python.org.
So bottom line: it works for me, even with your test program. I'm
puzzled why it doesn't work for you.
next prev parent reply other threads:[~2024-06-30 17:53 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
[not found] ` <CABodVWXdfXUhjhJNb13hcndALq+7A+L8VBODod7vBbD77DW5Vg@mail.gmail.com>
2024-06-30 17:53 ` Eli Zaretskii [this message]
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=86zfr2fhb5.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).