The -k flag was meant to be only for fsxc (not fsx) program, but we're showing it in the fsx case, and in that case it's not doing what it says (it should just compile and not run).
This bug actually only happens in Unix (macOS+Linux) and only when not being installed as a dotnet tool. Why? Because in those cases launcher.sh is used (instead of fsx.fsproj).
The
-k
flag was meant to be only forfsxc
(notfsx
) program, but we're showing it in the fsx case, and in that case it's not doing what it says (it should just compile and not run).