pseudo terminal support, was Re: [git-for-windows] Re: [ANNOUNCE] Git for Windows 2.27.0-rc0

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: May 19, 2020, 11:16 UTC
Message-ID: <nycvar.QRO.7.76.6.2005191311540.56@tvgsbejvaqbjf.bet>
In-Reply-To: <nycvar.QRO.7.76.6.2005180503440.55@tvgsbejvaqbjf.bet>

Hi,

On Mon, 18 May 2020, Johannes Schindelin wrote:

Show 45 quoted lines

> On Sat, 16 May 2020, Bryan Turner wrote:
>
> > On Sat, May 16, 2020 at 7:10 AM Johannes Schindelin <
> > Johannes.Schindelin@gmx.de> wrote:
> >
> > > Hi Bryan,
> > >
> > > On Fri, 15 May 2020, Bryan Turner wrote:
> > >
> > > > On Fri, May 15, 2020 at 10:32 AM Johannes Schindelin
> > > > <johannes.schindelin@gmx.de> wrote:
> > > > >
> > > > > Dear Git users,
> > > > >
> > > > > I hereby announce that Git for Windows 2.27.0-rc0 is available from:
> > > > >
> > > > >
> > > https://github.com/git-for-windows/git/releases/tag/v2.27.0-rc0.windows.1
> > > >
> > > > I've added the 2.27.0-rc0 release candidates for Git and Git for
> > > > Windows to Bitbucket Server's test matrix. No failures to report.
> > > >
> > > > Thanks as always for these early release candidates!
> > >
> > > Thank you so much!
> > >
> > > To be honest, this time round I would _really_ like to ask for some manual
> > > testing. I upgraded the MSYS2 runtime from being based on Cygwin v3.0.7 to
> > > v3.1.4, and the biggest new feature is support for those new-fangled
> > > pseudo terminals that Windows 10 now supports. I did find a couple of
> > > rough edges in my use cases, but I am not exactly a typical Git for
> > > Windows user...
> > >
> > > Could I ask for some manual testing in particular of anything run inside
> > > the Git Bash?
> >
> >
> > I’m happy to set it up and use it as my daily driver on one of my
> > workstations, but I don’t want to overpromise how much help I can really
> > offer for that sort of testing. I don’t do much of my full-time development
> > on Windows anymore for a variety of reasons, so even if I install it in my
> > Windows machines I won’t get that much active use in. And when I do use
> > Windows, I keep my workflow pretty simple, so aside from basic adds and
> > commits with an occasional checkout or very rare rebase, I just don’t cover
> > that much functionality.

Turns out that I ran into even more issues when trying to do a visual selection in `vim`: it would frequently "lose" the selection when I moved via the cursor keys.

So I've come to the conclusion that the pseudo console support code is still too buggy to unleash onto Git for Windows' users, except as an experimental option. I will patch it to make the pseudo console feature opt-in instead of opt-out, and then also offer to configure it in Git for Windows' installer via an experimental option.

Has anybody else run into issues with console programs (such as `vim`, interactive Bash, etc)? Or is there anybody with a very different experience than mine, i.e. _not_ having run into any issues despite using (interactively) Git Bash extensively?

Ciao, Dscho