Hitting Ctrl-C in executed shell script in Far Manager tab kills conemu

[s-kipnis]

Versions

ConEmu build: 221218 x64 OS version: Windows 10 x64 Used shell version: Far Manager 3.0 x64

Problem description

Attempt to terminate running windows batch shell script in Far Manager windows with Ctrl-C kills Conemu The problem exists only in Far Manager windows. Standalone Far Manager works nice as ConEmu tab without Far Manager

Steps to reproduce

1. Install ConEmu to use with Far Manager
2. Open Far Manager tab
3. run command ping whatever
4. Hit Ctrl-Break

Actual results

Conemu Tab dies with messages:

Far Manager, version 3.0.5959.0 x64
Copyright © 1996-2000 Eugene Roshal, Copyright © 2000-2022 Far Group

C:\>ping 10.199.40.163

Pinging 10.199.40.163 with 32 bytes of data:
Reply from 10.199.40.163: bytes=32 time<1ms TTL=128
Reply from 10.199.40.163: bytes=32 time<1ms TTL=128
Reply from 10.199.40.163: bytes=32 time<1ms TTL=128

Ping statistics for 10.199.40.163:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C

Current directory:
C:\Users\sk

Command to be executed:
"far.exe" /w /p"C:\Program Files\ConEmu\Plugins\ConEmu;%FARHOME%\Plugins;%FARPROFILE%\Plugins"

ConEmuC: Root process was alive less than 10 sec, ExitCode=xFFFFFFFF(4294967295).
Press Enter or Esc to close console...

On running similar script(with ping) situation is the same, tab is closed without any messages.

Expected results

Conemu Tab survives

[Maximus5]

Ctrl-C does not kill the ConEmu tab. It looks like your Far.exe is crashing after your ping is killed with Control-C.

Try to use "ConEmu64.exe -basic", remove some Far plugins, and try different Far versions. I don't think now, your issue is ConEmu-related.