* Re: MinTTY 2.1.3 update breaks interoperability with ConEmu
@ 2015-07-31 11:44 welikesspam
2015-08-01 2:28 ` Jim Reisert AD1C
0 siblings, 1 reply; 5+ messages in thread
From: welikesspam @ 2015-07-31 11:44 UTC (permalink / raw)
To: cygwin
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: MinTTY 2.1.3 update breaks interoperability with ConEmu
2015-07-31 11:44 MinTTY 2.1.3 update breaks interoperability with ConEmu welikesspam
@ 2015-08-01 2:28 ` Jim Reisert AD1C
2015-08-01 12:20 ` Andrey Repin
0 siblings, 1 reply; 5+ messages in thread
From: Jim Reisert AD1C @ 2015-08-01 2:28 UTC (permalink / raw)
To: cygwin
> 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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: MinTTY 2.1.3 update breaks interoperability with ConEmu
2015-08-01 2:28 ` Jim Reisert AD1C
@ 2015-08-01 12:20 ` Andrey Repin
2015-08-03 7:54 ` Thomas Wolff
0 siblings, 1 reply; 5+ messages in thread
From: Andrey Repin @ 2015-08-01 12:20 UTC (permalink / raw)
To: Jim Reisert AD1C, cygwin
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: MinTTY 2.1.3 update breaks interoperability with ConEmu
2015-08-01 12:20 ` Andrey Repin
@ 2015-08-03 7:54 ` Thomas Wolff
0 siblings, 0 replies; 5+ messages in thread
From: Thomas Wolff @ 2015-08-03 7:54 UTC (permalink / raw)
To: cygwin
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* MinTTY 2.1.3 update breaks interoperability with ConEmu
@ 2015-07-31 10:39 welikesspam
0 siblings, 0 replies; 5+ messages in thread
From: welikesspam @ 2015-07-31 10:39 UTC (permalink / raw)
To: cygwin
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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2015-08-03 7:54 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-07-31 11:44 MinTTY 2.1.3 update breaks interoperability with ConEmu welikesspam
2015-08-01 2:28 ` Jim Reisert AD1C
2015-08-01 12:20 ` Andrey Repin
2015-08-03 7:54 ` Thomas Wolff
-- strict thread matches above, loose matches on Subject: below --
2015-07-31 10:39 welikesspam
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).