public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Nicolás Ojeda Bär" <n.oje.bar@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Support for ConPTY?
Date: Wed, 03 Oct 2018 16:49:00 -0000	[thread overview]
Message-ID: <CAPunWhBr7oVJKkZReBqN+CumYkPuOug7ut+frg5MKgNYYNcPuw@mail.gmail.com> (raw)
In-Reply-To: <882627903.20181003192309@yandex.ru>

Hi Andrey,

Thanks for your email. I am rather ignorant about the technical
issues, but if you take a look at the section titled

  ConHost - Investing in yesterday for tomorrow

in the referenced blog post it seems to indicate quite clearly that
the new API can be used to run *existing* Console applications so that
they appear to be basically Unix terminal applications (doing I/O
using VT codes, etc).

Cheers,
Nicolás


On Wed, Oct 3, 2018 at 6:35 PM Andrey Repin <anrdaemon@yandex.ru> wrote:
>
> Greetings, Nicolás Ojeda Bär!
>
> > I was wondering if it would be possible to use the recent ConPTY API
>
> >
> > https://blogs.msdn.microsoft.com/commandline/2018/08/02/windows-command-line-introducing-the-windows-pseudo-console-conpty/
>
> > to improve the compatibility of Cygwin with native Windows console
> > applications (especially interactive ones).
>
> "Native Windows console applications" are not using that API, so, the point?
>
>
> --
> With best regards,
> Andrey Repin
> Wednesday, October 3, 2018 19:22:41
>
> 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

  reply	other threads:[~2018-10-03 16:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-03 16:08 Nicolás Ojeda Bär
2018-10-03 16:35 ` Andrey Repin
2018-10-03 16:49   ` Nicolás Ojeda Bär [this message]
2018-10-03 18:39     ` Brian Inglis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPunWhBr7oVJKkZReBqN+CumYkPuOug7ut+frg5MKgNYYNcPuw@mail.gmail.com \
    --to=n.oje.bar@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).