After disucssion in IRC:

• 1 is not a bug, but a shell feature. Must escape spaces. Underscores work as expected.
• 2 just works.
• 3 I will investigate.

IchoTolot: I want to test stuff on a Windows machine. May I invite you noodles with bolognese at your place? I will be a good boy and test NL levels too :3

Tested with Icho 3 weeks ago:

lix --coverage singlefile.txt > a.txt
Works, writes singlefile.txt's result into file a.txt.

lix --coverage dir\subdir > a.txt
Doesn't work, but I forgot to write what "doesn't work" means.

lix --coverage dir\file.txt
Doesn't work, no shell output.

lix
Doesn't start the game, but gives a dialog box: Bad File Descriptor.

Nepster says in IRC:

Second case: lix --coverage "dir\subdir" > a.txt does work on my computer.
Fourth case: I can start lix from the command line without problems using either lix or lix.exe.

Closing this because everything seems to work. If anybody has problems, file a new issue.

We don't get console output because I link with "lflags-windows": ["-L/subsystem:windows"], and that seems to close stdout. I should tell the Windows command-line users about this in my documentation, and explain how to redirect to file (> a.txt).