Cmder: Cmder hangs after idling for a few minutes or when clicking above the cursor

I also noticed that it hangs the same way if you click anywhere above where the cursor is.

I can confirm that issue, too. After a re-login (lock screen) you have to be patient.

r3Fuze has come up with a reliable way to replicate it. It's possible what I thought was an idling issue was actually me clicking above the cursor.

I have found the setting that is responsible for this. How it should be handled can be discussed.

Un-checking the box will fix the lockup issue. We could require a modifier key, which would keep the feature enabled by default, or just disable it all together. I have no idea what this could impact by disabling it.

I'll investigate this, I have the same issues and can be up to 10 seconds before I can do anything.

@sc0tt So this works for me.

Now would we want this disabled to prevent this happening for new users (will not allow users to change cursor position with mouse click) or leave it enabled and put it in the readme?

Can you still select and highlight text to copy? Not being able to mouse click on your line to type is default behavior it shouldn't be too shocking.

@Jackbennett Holding shift and click+dragging with the mouse still enables you to copy text. The issue here is that pressing above the active line will queue any input into the console for up to 10 seconds.

Unless we find a reason, my vote goes to disabling this feature.

I've had this checkbox turned off for months now with no ill effects. Would be great if this was the default in cmder.

@sc0tt Thanks for the screenshot. That solved it for me.

Yeah, thanks. Without this tweak, cmder was unusable, and I was close to giving it up until I found this thread. This really should be looked into and resolved. Or as you say, by default off.

This will be in the next release.

Thanks for the resolution. I was also close to give up with cmder.

I just ran into this issue with the most recent cmder as well.. it is quite annoying.

Edit: It would probably be useful for anyone to know that disabling the left click option mentioned above does resolve the issue for me as well.

This is happening still whether I use cmder or plain ConEmu+clink combo. It is happening a lot less ( but still happening) if I dont use clink.
I think it must be taken up with ConEmu / clink developers..

still happening on me dunno how to fix it

omg I was tearing my hair out trying to find out what was causing this with cmder. I almost dropped cmder because of this issue. You guys should definitely set this off by default. It's probably causing a bunch of newer users to just throw their hands and give up.

Btw. The settings window looks a bit different now than it used to in 2014. This is what it looks like now:

THANK YOU! It really drove me crazy.
Amazing this is still a problem these days.
As the "cool kids" say on Youtube:

2019?