nushell: Windows Executable Symlinks don't run

Describe the bug When trying to run a Windows Executable via a Symlink, instead of running the linked-to executable, NuShell gives an error message: error: Command not found

To Reproduce Steps to reproduce the behavior:

  1. Create a symlink in the current directory that links to a valid executable on the system (this may require Administrator privileges).
  2. Attempt to call that executable from NuShell.
  3. Observe the error.

Expected behavior Calling an executable through a symlink calls the linked-to executable.

Configuration (please complete the following information):

  • OS: Windows
  • Version: 0.12.0
  • Optional features (if any): None (used zip file from GH Releases)

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 15 (12 by maintainers)

Commits related to this issue

Most upvoted comments

@avandesa - not sure if you’ll see, but I also submitted a related issue: https://gitlab.com/avandesa/ichwh-rs/-/issues/2