Closed nojb closed 4 months ago
I did get 75% of the way porting down
to run on Windows but ran out of time (and still don't have the time). The patches are available at ~https://gitlab.com/diskuv/DkHelloWorldActor/-/tree/main/dependencies/down~ https://gitlab.com/diskuv/share/down-win32.git
My git comment says: "Printable characters works, but not up and down arrows."
I don't know what @jonahbeckford did (there's a login screen).
But:
The deeper issue is that Down is based on ANSI escape codes which are specific to UNIX.
Following a few links here and there it seems there is some kind of compatibility built in window. E.g.
https://learn.microsoft.com/en-us/windows/console/console-virtual-terminal-sequences
Not sure if all sequences I use are supported but there is e.g. cursor movement.
Oops. Edited the link.
Following a few links here and there it seems there is some kind of compatibility built in window. E.g.
Indeed, thanks for the link. Could not resist using this to give it a shot after @jonahbeckford claimed that he had it almost working (but before he revealed his patch). It is not much, but I got something bare bones working: #35.
Release 0.3.0 with Windows support is on the way to opam
. Thank you all !
The package does not even compile at the moment:
Of course, this is a just a surface issue. The deeper issue is that Down is based on ANSI escape codes which are specific to UNIX. The Windows console is conceptually different and is controlled using system calls. Making Down work with on Windows would require, as far as I understand, a complete rewrite of anything that uses ANSI codes to make API calls instead (a fair amount of work).
I'm opening the issue following the discussion at https://discuss.ocaml.org/t/ann-down-0-2-0-and-omod-0-4-0/14380/5.