On Apr  4 01:36, Takashi Yano wrote:
> On Sat, 30 Mar 2019 22:08:04 +0900 Takashi Yano wrote:
> > Known problems:
> > * mintty fails to start if it is started in console cygwin
> >   session.
> 
> This has been resolved in the new version.

Confirmed.

> On Tue, 2 Apr 2019 13:02:48 +0200 Corinna Vinschen wrote:
> > I found another weird effect which I can't explain off the top
> > of my head:  system_printf() debug output does not show up
> > in a mintty anymore with this patch.  Any idea why?
> 
> I am not sure, but this may be fixed in the new version.
> Could you please try?

Yes, it seems like that's fixed.

Mintty seems to start faster than with v1, too.

I encountered two other issues though, while running cygport to build
the latest gawk testbuild:

  $ cygport gawk.cygport build
  >>> Compiling gawk-4.2.62-1.x86_64

- This ">>> Compiling ..." line is printed by cygport itself.  It's bold
  black without the ConPTY patch, but it's bold white with your ConPTY
  patch.  Any idea why?

- There's a good chance that pressing Ctrl-C at this point will not only
  exit cygport, but also the shell *and* mintty.  Is it possible that
  another call to init_console_handler is required when the process
  runs in the ConPTY?


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer