2.1.3 breakes conemu

[fhoshino]

Mintty updated to 2.1.3, conemu will fail to capture the window due to spawning of process.
2.1.2 works fine with conemu.

Maximus5/ConEmu#239

[Maximus5]

The problem was with daemonizing. Well, adding -d switch will solve the problem, but...

1. This switch leads to an error if is used with previous mintty builds.
2. It's wrong, I believe, to let users to add -d switch manually. Damn, nobody reads docs.
3. I can't add the switch automatically because of (1).

So, may be you will not do forking/daemonizing if your app was started from ConEmu? Easiest way to check this - environment variable: http://conemu.github.io/en/ConEmuEnvironment.html#List_of_environment_variables_set_by_ConEmu for example ConEmuPID.

[mintty]

Disable the process-spawning with command line option -d.
The spawning was introduced to ensure signals are being delivered within mintty, which would otherwise not happen if started from a console window. I have no idea whether being invoked from ConEmu could be detected automatically, thus the option will likely be needed in future.
Also, please tell me whether in mintty -d, or older mintty, signals work (e.g. Control-C interrupts).

[Maximus5]

Ctrl-C interrupts "ls -R" properly at least when mintty is running in ConEmu tab. Either old mintty build, or new one with -d switch doesn't matter, all work.

Checking environment variable, as I've said, is the simplest way.

If you need test, you may download ConEmu, unpack it and run ConEmu.exe -basic -cmd c:\cygwin\bin\mintty.exe -

[Maximus5]

Link to cygwin topic: http://comments.gmane.org/gmane.os.cygwin/154167

[mintty]

As suggested, the workaround checks for $ConEmuPID although that's not strictly a safe indication; but starting an "outside" mintty from there works as well, so that should be fine.