Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fsx --help gives fsxc help #34

Open
knocte opened this issue Aug 19, 2023 · 0 comments
Open

fsx --help gives fsxc help #34

knocte opened this issue Aug 19, 2023 · 0 comments

Comments

@knocte
Copy link
Member

knocte commented Aug 19, 2023 

$ fsx --help
Usage: dotnet fsxc [OPTION] yourscript.fsx
...
@knocte knocte changed the title fsx --help gives fsxc help fsx --help gives fsxc help (Linux) Aug 19, 2023
knocte added a commit that referenced this issue Aug 21, 2023
@knocte
fsx,fsxc: fix PrintUsage() to identify prog
9932e4c 
Fixes #34
knocte added a commit that referenced this issue Aug 21, 2023
@knocte
fsx,fsxc: fix PrintUsage() to identify prog
cc00041 
Fixes #34
knocte added a commit that referenced this issue Aug 21, 2023
@knocte
fsx,fsxc: fix PrintUsage() to identify program
9425b8e 
Fixes #34
@knocte knocte changed the title fsx --help gives fsxc help (Linux) fsx --help gives fsxc help Aug 21, 2023
knocte added a commit that referenced this issue Aug 21, 2023
@knocte
fsx,fsxc: fix PrintUsage() to identify program
32849ba 
Partially addresses this bug[1] (only partially because
it still happens in Unix, due to the fact that in Linux
and macOS we still use launcher.sh instead of fsx proj).

[1] #34
knocte added a commit that referenced this issue Aug 21, 2023
@knocte
fsx,fsxc: fix PrintUsage() to identify program
0698ed8 
Partially addresses this bug[1] (only partially because
it still happens in Unix (when not installed via `dotnet
tool install`), due to the fact that in Linux
and macOS we still use launcher.sh instead of fsx proj.

[1] #34
knocte added a commit that referenced this issue Aug 21, 2023
@knocte
fsx,fsxc: fix PrintUsage() to identify program
750159c 
Partially addresses this bug[1], but only partially because it
still happens in Unix (when not installed via `dotnet
tool install`), due to the fact that in Linux
and macOS we still use launcher.sh instead of fsx proj.

[1] #34
knocte added a commit that referenced this issue Aug 21, 2023
@knocte
fsx,fsxc: fix PrintUsage() to identify program
dc62d8c 
Partially addresses this bug[1], but only partially because it
still happens in Unix (when not installed via `dotnet
tool install`), due to the fact that in that case the script
launcher.sh is used instead of the 'fsx' proj.

[1] #34
knocte added a commit that referenced this issue Aug 23, 2023
@knocte
fsx,fsxc: fix PrintUsage() to identify program
b6d8818 
Partially addresses this bug[1], but only partially because it
still happens in Unix (when not installed via `dotnet
tool install`), due to the fact that in that case the script
launcher.sh is used instead of the 'fsx' proj.

[1] #34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@knocte