Re: [PATCH 0/2] Really fix the isatty() problem on Windows

Hi Hannes, On Thu, 22 Dec 2016, Johannes Sixt wrote: > Am 21.12.2016 um 22:15 schrieb Johannes Sixt: > > Am 21.12.2016 um 18:53 schrieb Johannes Schindelin: > > > The current patch series is based on `pu`, as that already has the > > > winansi_get_osfhandle() fix. For ease of testing, I also

Re: [PATCH 0/2] Really fix the isatty() problem on Windows

Am 21.12.2016 um 22:15 schrieb Johannes Sixt: Am 21.12.2016 um 18:53 schrieb Johannes Schindelin: The current patch series is based on `pu`, as that already has the winansi_get_osfhandle() fix. For ease of testing, I also have a branch based on master which you can pull via git pull

Re: [PATCH 0/2] Really fix the isatty() problem on Windows

Johannes Sixt writes: > Am 21.12.2016 um 18:53 schrieb Johannes Schindelin: >> The current patch series is based on `pu`, as that already has the >> winansi_get_osfhandle() fix. For ease of testing, I also have a branch >> based on master which you can pull via >> >> git pull

Re: [PATCH 0/2] Really fix the isatty() problem on Windows

Am 21.12.2016 um 18:53 schrieb Johannes Schindelin: The current patch series is based on `pu`, as that already has the winansi_get_osfhandle() fix. For ease of testing, I also have a branch based on master which you can pull via git pull https://github.com/dscho/git

[PATCH 0/2] Really fix the isatty() problem on Windows

My previous fix may have fixed running the new t/t6030-bisect-porcelain.sh script that tested the new bisect--helper, which in turn used isatty() to determine whether it was running interactively and was fooled by being redirected to /dev/null. But it not only broke paging when running in a CMD