RE: Thoughts on the Contributing page
Andreas, Alp:
- On windows build.bat defaults to stack which I think has never worked on my box. Andrey? (cc'd him)
Actually `build.bat` calls the Cabal-based build script. This was a relatively recent change, and we plan to stick to it in the long term, while still providing an alternative `build.stack.bat`.
There are also a few quality of life issues like ctrl+c not canceling the build on windows. Which I hope will be resolved at some point but not sure if these should be showstoppers.
Indeed. I hope it's not difficult to fix this, but I'm not sure where to start. Any suggestions are very welcome. Cheers, Andrey
Indeed. I hope it's not difficult to fix this, but I'm not sure where to start. Any suggestions are very welcome.
It is unfortunately, because it's not a bug. Odds are both of you are using MinTTY which people blindly recommend to use. The problem is MinTTY is not designed to run native Windows applications, it is designed to run ported POSIX applications. e.g. things linked against the msys2/cygwin runtime. Because of this it implements a very intrusive hack in order to be able to handle signals the way they would be under a posix application, which simply isn't compatible with Windows signals see https://github.com/mintty/mintty/issues/56 Because your build is triggered by a batch file, when you press ctrl+c mintty will terminate the parent process indiscriminately if it's a script, e.g. the batch process is killed but none of the children are. This is why ghci has ghcii.sh as a workaround. e.g. why pressing ctrl+c terminate ghci instead of the computation as we can't. this is why you should not use MinTTY with a native Windows application. MinTTY also introduces a number of character encoding problems for native Windows applications, see https://github.com/mintty/mintty/wiki/Tips#inputoutput-interaction-with-alie.... In short, the issues you're seeing are by design. Now you have two options: 1) Don't use mintty, instead use something like ConEmu https://conemu.github.io/ with bash.exe from msys2 as the terminal host.This will work for Native application but have issues with interactive posix applications like msys2 gdb (mingw64 gdb should in theory work fine though, but it's slightly more limited) and i.e.. tmux won't work. (the problems are thus flipped). 2) Use WinPTY https://github.com/rprichard/winpty to wrap native application calls (you can just install it via pacman), which works and you can keep using MinTTY, but this does have a slight performance overhead as the reason it works is that it spawns a hidden buffer and scrapes output from it and send events to it to check the native behavior for Windows applications. TL;DR; It's not a simple issue, the application can only deal with one signal processing method at a time. Cheers, Tamar
Cheers, Andrey _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
participants (2)
-
Andrey Mokhov -
Phyx