Re: stack 1.7.0.1 does not color on Windows powershell terminal

2018-04-19 Thread Murat Özsöyler
Hi Emanule, Thank you for your response. I am too busy for now, but I shall try your suggestion as soon as I can. 19 Nis 2018 Per, 14:35 tarihinde, Emanuel Borsboom şunu yazdı: > stack-1.6.5 used ansi-terminal-0.7.1.1, while the stack-1.7 release > candidates use

Re: stack 1.7.0.1 does not color on Windows powershell terminal

2018-04-19 Thread Emanuel Borsboom
stack-1.6.5 used ansi-terminal-0.7.1.1, while the stack-1.7 release candidates use ansi-terminal-0.8.0.2. According to the ChangeLog, there have been some changes on Windows. Perhaps you could try building `stack` with ansi-terminal-0.7.1.1 on Windows and see if that makes a difference? > On

Re: stack 1.7.0.1 does not color on Windows powershell terminal

2018-04-19 Thread Murat Özsöyler
Hi Niklas, Thank you for your attention. As I mentioned before I upgraded stack form 1.6.x (I think) to 1.7.0.1 as per Michael Snoyman's suggestion. From then on the output is like this: [image: image.png] Before no problem were in the color. The upgrade was mandatory for me to upgrade inner

Re: stack 1.7.0.1 does not color on Windows powershell terminal

2018-04-18 Thread niklas
Hey Murat, can you clarify which colour output you mean? The colour output by stack itself, e.g. what `stack build -v` does, or the coloured output as piped from ghc compile error messages? I've tried the version you mentioned on Windows but my PowerShell seems to print both as expected. A

Re: stack 1.7.0.1 does not color on Windows powershell terminal

2018-04-17 Thread Murat Özsöyler
Hi Neil, Thank you for the info. Actually the colors were working before I upgraded to 1.7.0.1. Upgrade was mandatory to me as I use some hpack features not existed in previous version. In windows stack comes with its own msys2 installation. The colors work on msys2 terminal. But this time the

Re: stack 1.7.0.1 does not color on Windows powershell terminal

2018-04-17 Thread Neil Mitchell
Hi Murat, This isn't necessarily even a change in 1.7 - I reported this as far back as 1.5. You've always been able to get ANSI codes out, and what's even more sad is that on Windows 10 (where I'm running) it can deal with the ANSI codes properly. See