GNU bug report logs - #71853
29.4; `kill-compilation` does not kill compilation process on Windows

Previous Next

Full log

Message #22 received at 71853 <at> debbugs.gnu.org (full text, mbox):

From: Tze Chian Kam <tze.chian.kam <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 71853 <at> debbugs.gnu.org
Subject: Re: bug#71853: 29.4; `kill-compilation` does not kill compilation
 process on Windows
Date: Tue, 2 Jul 2024 16:26:32 +1000

> From: Eli Zaretskii
> Date: Mon, 01 Jul 2024 14:27:09 +0300
>
> > From: Tze Chian Kam <tze.chian.kam <at> gmail.com>
> > Date: Mon, 1 Jul 2024 12:53:51 +1000
> > Cc: 71853 <at> debbugs.gnu.org
> >
> > > > 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.
> >
> > I did "M-x compile RET python loop.py RET". Also, when running this
> > program, it does not output anything in the *compilation* buffer ("active"
> > is not printed every second).
>
> The fact that it doesn't print "active" is already a sign of some
> problem.
>
> Where did you download your Python from?  Is it a native Windows
> executable, or something else, like Cygwin or MSYS2 build of Python?

It is a MSYS2 build of Python.

I just tested with Emacs in my global path (so I can launch Emacs from
Powershell/Command Prompt) and it "C-c C-k' works (using native
Windows Python) but I still can't see the prints before killing the process.

Previous Next

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