Fsharp: Incorrect usage path when used via dotnet command

Created on 24 Jan 2020  路  3Comments  路  Source: dotnet/fsharp

#help says See 'dotnet --help' for options which should probably be See 'dotnet fsi --help' for options.

dotnet fsi --help says Usage: dotnet <options> [script.fsx [<arguments>]] which should probably be Usage: dotnet fsi <options> [script.fsx [<arguments>]].

Area-DotNetCore Area-FSI bug

All 3 comments

@KevinRansom is this set of strings ours, or are they in the CLI?

@cartermp the problem can be found here:
https://github.com/dotnet/fsharp/blob/cba6e1b8ce8e931f288f63ae0e27a2fb02a458e7/src/fsharp/fsi/fsi.fs#L757

It is assumed that fsi is invoked directly and not via some intermediate executable.

Cloning the repo to try and see if I can fix it 馃檪.

Edit: the other case mentioned by @drguildo (output from dotnet fsi --help) is found here:
https://github.com/dotnet/fsharp/blob/cba6e1b8ce8e931f288f63ae0e27a2fb02a458e7/src/fsharp/fsi/fsi.fs#L631

The easiest way to find these issues is to look at https://github.com/dotnet/fsharp/blob/0dc21fae8a120b8a6554929999becf9b82f33061/src/fsharp/fsi/FSIstrings.txt and search for the problematic string, then find references to the generated FSIstrings.SR.* function.

Thanks @AndreasHassing for addressing this!

Was this page helpful?
0 / 5 - 0 ratings