This is the mail archive of the
mailing list for the Cygwin project.
Re: mintty/Windows interoperability (was: Re: default terminal)
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Fri, 4 Jun 2010 01:04:45 -0400
- Subject: Re: mintty/Windows interoperability (was: Re: default terminal)
- References: <AANLkTimLbuz7V2yTfJrd1e9n3d9lEZ6crMsl2v85oguM@mail.gmail.com> <20100531212927.GI18315@ednor.casa.cgf.cx> <4C0442DA.firstname.lastname@example.org> <4C06C175.email@example.com> <AANLkTim4Nv4e9QSUgFeF6TLg-vcStqMI9SDclcwLJqiL@mail.gmail.com>
- Reply-to: cygwin-apps at cygwin dot com
On Thu, Jun 03, 2010 at 07:17:34PM +0100, Andy Koppe wrote:
>On 2 June 2010 21:39, Thomas Wolff wrote:
>> Before making it the only default, however, there's still two issues to
>> consider concerning interoperability with Windows programs:
>> ?? * The known limitation with certain Windows (or even DOS) programs
>> ?? ?? due to the incompatibility of some of the multiple Windows output
>> ?? ?? methods with pty. Is anyone still trying to find a wrapper that
>> ?? ?? might solve this for input and output?
>I don't know of any attempt at this since 'ttyfier'. As you know, I
>did have a go at the input side only with 'conin', but that wasn't
>much of a success. Grabbing the screen buffer from a hidden console
>using ReadConsoleOutput and displaying it using terminal escape
>sequences seems fairly straightforward in principle, but it would
>still be a load of work. I can't commit to that.
>(See also http://code.google.com/p/mintty/issues/detail?id=56 for
>other ideas to tackle this.)
That's what Console2 does but its license does not allow us to use
the code. I have some code kicking around that is in the public
domain but it's pretty ugly.
>In the end though, these ideas are all imperfect workarounds. Given
>that there is a straightforward answer to any issue with console
>programs ("use a console"), I find it hard to justify much effort
>going into them.