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

Cannot open directories in UNC paths by the command code #38587

Closed
tats-u opened this issue Nov 17, 2017 · 1 comment
Closed

Cannot open directories in UNC paths by the command code #38587

tats-u opened this issue Nov 17, 2017 · 1 comment
Labels
feature-request Request for new features or functionality help wanted Issues identified as good community contribution opportunities workbench-cli VS Code Command line issues

Comments

@tats-u
Copy link
Contributor

tats-u commented Nov 17, 2017

  • VSCode Version: 1.18.0
  • OS Version: Windows 10 1709 17025.1000 (Insider Preview Slow ring)

Steps to Reproduce:

  1. Open PowerShell
  2. Set-Location to any UNC paths
  3. Run code with any arguments

Reproduces without extensions: Yes

e.g.

PS C:\users\user> cd \\address.to.nas\directory
PS Microsoft.PowerShell.Core\FileSystem::\\address.to.nas\directory> code .
'\\address.to.nas\directory'
CMD.EXE was started with the above path as the current directory. UNC paths are not supported. Defaulting to Window directory.

Cannot open the directory in Visual Studio Code. This is because code.cmd is a batch script of CMD, which does not support UNC paths. You have to make a PowerShell script named code.ps1 that behaves like code.cmd to solve it.

@vscodebot vscodebot bot added the terminal Integrated terminal issues label Nov 17, 2017
@Tyriar Tyriar added workbench-cli VS Code Command line issues feature-request Request for new features or functionality help wanted Issues identified as good community contribution opportunities and removed terminal Integrated terminal issues labels Dec 15, 2017
@Tyriar Tyriar removed their assignment Dec 15, 2017
@Tyriar
Copy link
Member

Tyriar commented Dec 15, 2017

FYI @joaomoreno

@tats-u tats-u closed this as completed Apr 16, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators May 31, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality help wanted Issues identified as good community contribution opportunities workbench-cli VS Code Command line issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants