question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`dotnet fsi --help` does not show option help

See original GitHub issue

Repro steps

  1. Run dotnet fsi --help or dotnet fsi -? or dotnet fsi -h in the command line

Expected behavior

Options should be listed, according to https://docs.microsoft.com/en-us/dotnet/fsharp/language-reference/fsharp-interactive-options

Actual behavior

No options are shown, and a sort of recursive suggestion of using the same options that were used is shown.

PS > dotnet fsi --help
Description:

Usage:
  dotnet fsi [options]

Options:
  -?, -h, --help  Show command line help.

Known workarounds

View the options here: https://docs.microsoft.com/en-us/dotnet/fsharp/language-reference/fsharp-interactive-options

Related information

Provide any related information (optional):

  • Operating system: Windows 11 and Ubuntu (via WSL2)
  • .NET Runtime kind (.NET Core, .NET Framework, Mono): F# Interactive version 12.0.4.0 for F# 6.0
  • Editing Tools (e.g. Visual Studio Version, Visual Studio): n/a

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:11 (11 by maintainers)

github_iconTop GitHub Comments

3reactions
baronfelcommented, Jul 16, 2022

I opened a PR on the SDK targeted for .NET 7 to address this. It probably wouldn’t be a high enough severity to make it into 6.0 servicing fixes, though.

2reactions
baronfelcommented, Jul 16, 2022

Most of the other commands are implemented as actual system.commandline commands. Some, like Nuget, FSI, MSBuild, and others, forward along to other binaries shipped in the SDK. For those, we’ve customized help output to forward the help request to the underlying binary (as opposed to the default system.commandline help output that you’re seeing here generated for FSI).

To fix this we would need to replicate that same forwarding pattern. Very easy to do, just something that needs to be done in the SDK itself.

Read more comments on GitHub >

github_iconTop Results From Across the Web

F# Interactive (dotnet) Reference
Learn how F# Interactive (dotnet fsi) is used to run F# code interactively at the console or to execute F# scripts.
Read more >
F# Interactive (fsi.exe) support in.Net Core SDK (v3.1.100. ...
This just means that fsi.exe hasn't been compiled to run as a single exe but instead needs to be called via dotnet.
Read more >
What I wish I knew when learning F#
F# has type providers that can help somewhat in this problem space but they are limited in what they can take as inputs...
Read more >
Department of State News Letter - Page 23 - Google Books Result
SETTING THE RECORD STRAIGHT On Serving U.S. Travelers Abroad With the advent of ... is the Editor of the " Issues " series...
Read more >
How to use
FSI is displayed using the builtin :terminal feature introduced in Vim 8 / Neovim and can be used like in VSCode. :FsiShow. Shows...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found