[Bug] Can't stop using Ctrl+C when output very fast
Open
Nobody has claimed this yet.
🐛 Type: Bug
👆 ConEmu
- Dominant language
- PowerShell
- Stars
- 27k
- Forks
- 2.1k
- PR merge metrics
- No merged PRs in 30d
Description
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,
- cmd
Ctrl+Ccan't stop it - 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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing adb logcat in Cmder Full on Windows 10 with rapidly updating output. Investigate how Ctrl+C interruption and window closing behave under this high-output condition, and verify that both stopping the command and closing Cmder work reliably when the issue is fixed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100