[Bug] Can't stop using Ctrl+C when output very fast

[ganqiuye]

Version Information

Cmder version:1.3.25.328
Operating system:win10

Cmder Edition

Cmder Full (with Git)

Description of the issue

catching an android log:
#adb logcat

if the output log is very fast,

1. cmd Ctrl+C can't stop it
2. it is also unsuccessful to close the window of cmder

How to reproduce

No response

Additional context

No response

Checklist

• I have read the documentation.
• I have searched for similar issues and found none that describe my issue.
• I have reproduced the issue on the latest version of Cmder.
• I am certain my issues are not related to ConEmu, Clink, or other third-party tools that Cmder uses.

[chrisant996]

It's not a Cmder issue. It's either an adb issue or ConEmu issue.

Have you tried pressing Ctrl-Break instead? That sometimes works even when a program isn't properly responding to Ctrl-C.

[ugenehan]

the same

[Ben-Mack]

I also have the problem where ConEmu can stop some python program with Ctrl+C but Cmder can't, Cmder can only stop by closing the window.

[myfonj]

Probably related to ConEmu/ConEmu#2395 . Problem is that ConEmu basically also blames "third parties" for this problem, and from my tests with simple

timeout /t 10 /nobreak

even it's clean instance tends to be inconsistent with the Ctrl+C behaviour on my setup.

---

Cmder can only stop by closing the window

You can also try tab context menu > Close or kill > Kill all but shell (and/or set a keyboard shortcut for that) as suggested around here. Sadly probably not as clean exit as regular break, but useful for side-effect-free terminations nonetheless.