Active console (cmd.exe) is closed on pressing CTRL-C

[Maximus5]

Originally reported on Google Code with ID 1340

Required information!
OS version: Win7/64/Ultimate/de
ConEmu version: 131114

Reported by pfeiffer@tzi.de on 2013-11-15 14:56:51

[Maximus5]

Here is my configuration file.

Reported by pfeiffer@tzi.de on 2013-11-15 14:57:26

---

- _Attachment: [ConEmu.xml](https://storage.googleapis.com/google-code-attachments/conemu-maximus5/issue-1340/comment-1/ConEmu.xml)_

[Maximus5]

I believe, this is not a ConEmu problem. And does not reproduced on my side, CtrlC just
goes new empty prompt line.
Check your third party tools I think. Unload all processes from memory to ensure that
there is no other intrusions.
Also, you may attach mini dump of cmd.exe, may be it will show smth...

Reported by ConEmu.Maximus5 on 2013-11-15 15:11:40

[Maximus5]

Without additional information issue will be closed soon.

Reported by ConEmu.Maximus5 on 2013-11-19 07:50:37

[Maximus5]

I have the same issue.

But it occures only if I open cmd.exe directly (start > run > cmd.exe) and then ConEmu
takes control. If I press Ctrl+C in this session, it will be closed. Additionaly, the
cmd.exe process, which was opened in ConEmu this way, will remain in running processes.
So if I open and close 10 cmd.exe sessions this way, I will end up with 10 running
cmd.exe processes, but none visible.

If I run ConEmu directly (from Start menu for example) and a default cmd.exe session
is opened, Ctrl+C just goes to a new empty line like you said.

Os version: Win7/64/Pro
ConEmu version: 131119

Reported by ivan.centes on 2013-11-22 13:25:15

[Maximus5]

Also, I tested it on a clean Windows start, with nothing but ConEmu running in processes.

Reported by ivan.centes on 2013-11-22 13:27:36

[Maximus5]

Reported by ConEmu.Maximus5 on 2013-11-22 16:11:53

• Status changed: Accepted

[Maximus5]

It really seems to depend on how a console is started. If I start cmd.exe from the start
menu, I can close it via CTRL-C but if I duplicate the console within ConEmu a CTRL-C
doesn't close the console (instead the line is aborted).

Reported by pfeiffer@tzi.de on 2013-11-29 09:44:10

[Maximus5]

Have you already had success reproducing this problem?

Reported by pfeiffer@tzi.de on 2013-12-09 14:15:38

---

- _Attachment: screenshot.png
_

[Maximus5]

By the way, sometimes I see this assertion when pressing CTRL-C.

Reported by pfeiffer@tzi.de on 2013-12-09 14:16:15

[Maximus5]

Reproduced when cmd is started using "Default terminal" feature. Not fixed yet.

Does assertion appears on latest (ATM 131207) build?

Reported by ConEmu.Maximus5 on 2013-12-09 14:20:35

[Maximus5]

I've confirmed, that Ctrl+C may terminate active console process, but ONLY if this console
was started via "Default terminal feature". For ALL other cases - check your console
applications.

Simple workaround ATM - run your scripts in ConEmu (even from shortcut) but not "directly".

Reported by ConEmu.Maximus5 on 2013-12-20 21:54:04

[Maximus5]

Most of my console processes are launched by other tools and has to be grabbed by ConEmu.
All these consoles can be accidentally closed by pressing CTRL-C. This is an bug that
occurs here multiple time per day.

I would so happy to see this fixed in one of the next betas! :-)

Reported by pfeiffer@tzi.de on 2014-01-09 11:28:18

[Maximus5]

140109

Reported by ConEmu.Maximus5 on 2014-01-10 00:02:56

[Maximus5]

Thank you so much!

Reported by pfeiffer@tzi.de on 2014-01-10 12:45:17

[Maximus5]

I've been having this issue too on multiple computers (all of them with Win7 64 bit).

And unfortunately the problem is still there in 140109.

I think is something more. In my case the console remains attached all the time and
I've no problem with the CTRL+C most of the time, but sometimes, when I switch from
another application to conEmu, I start typing something, and nothing show up on the
screen. 

Here *IF I WAIT*, after ~2-3 seconds the characters I typed show up on the console
and everything works fine (including CTRL+C), *BUT* if I press CTRL+C during this 2-3
sec period, the console closes.

I don't know if it's relevant or not, but I've noticed a similar behavior also with
'Console2'.

Hope this help identifying the issue.

Reported by fabriziobertocci on 2014-01-11 15:43:17

[Maximus5]

@fabriziobertocci
This is not a ConEmu problem. In any case, your issue can't match this exact one.
Try to run cmd outside of ConEmu. I'm sure, your Ctrl+C behavior will be the same.
If you are still sure this is ConEmu's problem - open new issue.

Reported by ConEmu.Maximus5 on 2014-01-11 16:15:17

• Status changed: Fixed

[Maximus5]

hmm I'll see if I can verify it on the command prompt console. 
Thanks for checking.

Reported by fabriziobertocci on 2014-01-13 15:53:59

[Maximus5]

Don't hesitate to create new issue, if you ensure about ConEmu-related problem. But
I think, your console issue yes about smth else...

Reported by ConEmu.Maximus5 on 2014-01-13 15:58:14