Re: MinTTY 2.1.3 update breaks interoperability with ConEmu

Re: MinTTY 2.1.3 update breaks interoperability with ConEmu

[welikesspam]

Please disregard this post. Checking the changelog reveals that this is 
caused by a new feature, and can be overridden with the -d (--nodaemon) 
switch. My fault for not R'ing TFM before posting. I apologize.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: MinTTY 2.1.3 update breaks interoperability with ConEmu

[Jim Reisert AD1C]

> Please disregard this post. Checking the changelog reveals that this is
> caused by a new feature, and can be overridden with the -d (--nodaemon)
> switch.

Why isn't the old behavior the default (spawn one process), with the
new feature being *enabled* by the -d switch?  Wouldn't "-daemon" also
make more sense than "-nodaemon"?

-- 
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: MinTTY 2.1.3 update breaks interoperability with ConEmu

[Andrey Repin]

Greetings, Jim Reisert AD1C!

>> Please disregard this post. Checking the changelog reveals that this is
>> caused by a new feature, and can be overridden with the -d (--nodaemon)
>> switch.

> Why isn't the old behavior the default (spawn one process), with the
> new feature being *enabled* by the -d switch?  Wouldn't "-daemon" also
> make more sense than "-nodaemon"?

Had the same question.


-- 
With best regards,
Andrey Repin
Saturday, August 1, 2015 15:19:17

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: MinTTY 2.1.3 update breaks interoperability with ConEmu

[Thomas Wolff]

Am 01.08.2015 um 14:19 schrieb Andrey Repin:
> Greetings, Jim Reisert AD1C!
>
>>> Please disregard this post. Checking the changelog reveals that this is
>>> caused by a new feature, and can be overridden with the -d (--nodaemon)
>>> switch.
>> Why isn't the old behavior the default (spawn one process), with the
>> new feature being *enabled* by the -d switch?  Wouldn't "-daemon" also
>> make more sense than "-nodaemon"?
> Had the same question.
Because the purpose of the new behaviour is to ensure normal operation
when mintty is called from a cygwin console, i.e. within a normal cygwin
environment. Unfortunately, otherwise, signal delivery is broken within
mintty, e.g. ^C does not work. I guess this is some bug in cygwin
itself, if you like to help debug it :) , we may eventually revert to
the previous behaviour.
Suggestions for better solutions are welcome, and I will check to detect
ConEmu explicitly to make an exception in that case.
Thomas

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

MinTTY 2.1.3 update breaks interoperability with ConEmu

[welikesspam]

As of update 2.1.3, MinTTY, when opening, spawns 2 child processes, the 
second of which is the actual MinTTY window. This behavior is different 
from MinTTY 2.1.2, which spawned one, and breaks interoperability with 
ConEmu. Is there a reason why MinTTY needs to create a third process?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple