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
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
> 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
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:/
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?
--
Proble
5 matches
Mail list logo
