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.

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

[global tool] FAKE dotnet global tool is not found on zsh #1951

Closed
baronfel opened this issue May 21, 2018 · 5 comments
Closed

[global tool] FAKE dotnet global tool is not found on zsh #1951

baronfel opened this issue May 21, 2018 · 5 comments

Comments

@baronfel
Copy link
Contributor

baronfel commented May 21, 2018

Description

When using zsh the fake global tool stub is never run, despite the appropriate $PATH entries being in place. The tool is run correctly using bash. This is something that impacts every dotnet sdk global tool (try dotnet tool install -g weeknumber && weeknumber to verify). I'll be opening this over at the dotnet/cli repo as well, but wanted this here as a tracking issue.

Repro steps

Please provide the steps required to reproduce the problem:

  1. Have the 2.1 preview SDK installed (2.1.300-rc1-008673)
  2. run zsh with no profile via zsh --no-rcs
  3. dotnet tool install -g fake-cli --version '5.0.0-*'
  4. fake

Expected behavior

The FAKE cli help should display

Actual behavior

The shell reports that fake could not be found.

Known workarounds

  • run the command in bash, or
  • run the fake command explicitly, via ~/.dotnet/tools/fake

Related information

  • Mac OSX High Sierra 10.13.4
  • 5.0 rc 15
  • Mono 5.12 or dotnet sdk 2.1.300-rc1-008673
@baronfel
Copy link
Contributor Author

Here's the upstream tracking issue: https://github.com/dotnet/cli/issues/9321

@matthid
Copy link
Member

matthid commented May 21, 2018

@baronfel Is your shell broken? dotnet sdk is just adding an executable into the folder. afaik there is nothing specific to why is wouldn't work in zsh

@matthid
Copy link
Member

matthid commented May 21, 2018

Maybe zsh doesn't resolve ~/?

@baronfel
Copy link
Contributor Author

that's the problem exactly. that ~-path is being written by the dotnet cli tool installer, so I'm hoping they'll update and write the full path to support more shells.

@matthid
Copy link
Member

matthid commented May 21, 2018

I'm closing this here since it is easy to workaround (just manually edit your PATH) and the issue is tracked in dotnet/cli

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants