GNU bug report logs - #76943
30.1; comint-interrupt-subjob does not interrupt process in inferior-python

Previous Next

Package: emacs;

Reported by: Garid Zorigoo <garidzorigoo <at> gmail.com>

Date: Tue, 11 Mar 2025 15:28:01 UTC

Severity: normal

Found in version 30.1

Done: Mattias Engdegård <mattias.engdegard <at> gmail.com>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Garid Zorigoo <garidzorigoo <at> gmail.com>, kobarity <kobarity <at> gmail.com>
Cc: 76943 <at> debbugs.gnu.org
Subject: bug#76943: 30.1; comint-interrupt-subjob does not interrupt process in inferior-python
Date: Thu, 13 Mar 2025 08:22:13 +0200

> From: Garid Zorigoo <garidzorigoo <at> gmail.com>
> Date: Thu, 13 Mar 2025 11:04:23 +0900
> 
> 
> I found a work around, not sure how & why.
> Changing the value of comint-ptyp seems to make comint-interrupt-subjob work:
> 
>  (setq comint-ptyp nil)
> 
> Hope this helps.
> 
> I believe that inferior-python should be able to interrupt subjobs
> by default (i.e. without the user changing the above variable value).

kobarity, any comments or suggestions?
This bug report was last modified 31 days ago.

Previous Next

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