Skip to content

Tab Completion removes backslash in UNC Path #681

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

Closed
mpearon opened this issue Apr 14, 2017 · 8 comments
Closed

Tab Completion removes backslash in UNC Path #681

mpearon opened this issue Apr 14, 2017 · 8 comments
Labels
Milestone

Comments

@mpearon
Copy link

mpearon commented Apr 14, 2017

System Details

  • Operating system name and version: Windows 10 v1607, build 14393.970
  • VS Code version: 1.11.2
  • PowerShell extension version: 0.11.2
  • Output from $PSVersionTable:

PSVersion 5.1.14393.953
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14393.953
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Issue Description

Tab completion is removing the initial backslash from UNC Paths.
For instance:
\\CorpServer\ becomes \CorpServer\ when one of the subdirectories is selected.
This occurs at every level, not just at the root of the server/share.

@daviwil
Copy link
Contributor

daviwil commented Apr 24, 2017

Wow, that's weird, I'll take a look!

@daviwil daviwil added this to the May 2017 milestone Apr 24, 2017
@mpearon
Copy link
Author

mpearon commented Apr 29, 2017

I just recently learned that I could embed GIFs, and grabbed a copy of LICEcap, so I've decided to attach a demonstration, so that others can see what's happening.

uncissue

@AspenForester
Copy link
Contributor

I hadn't noticed this behavior before, but I can report that I can duplicate the issue with:
VSCode: 1.12.0
PowerShell Extension: 1.0.0

Name Value


PSVersion 5.1.14393.1066
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14393.1066
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

@daviwil
Copy link
Contributor

daviwil commented May 17, 2017

This seems to be fixed in the latest Visual Studio Code Insiders build, can you try it there and let me know if it's resolved for you?

@mpearon
Copy link
Author

mpearon commented May 17, 2017

@daviwil
I checked in Insiders, and you are correct - it appears to be working as expected! :)

@daviwil
Copy link
Contributor

daviwil commented May 17, 2017

Great, thanks for confirming! I'll keep this issue open until that fix comes to the stable VS Code release.

@daviwil daviwil modified the milestones: June 2017, 1.1.0 May 17, 2017
@mpearon
Copy link
Author

mpearon commented Jun 9, 2017

Great news, @daviwil! As of 1.13.0, this behavior seems to have been corrected! :)

@mpearon mpearon closed this as completed Jun 9, 2017
@daviwil
Copy link
Contributor

daviwil commented Jun 9, 2017

That's great, thanks a lot!

@daviwil daviwil modified the milestones: 1.3.0, June 2017 Jun 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants