Skip to content

Network path broke when using auto complete #306

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
monghuz opened this issue Sep 28, 2016 · 6 comments
Closed

Network path broke when using auto complete #306

monghuz opened this issue Sep 28, 2016 · 6 comments
Labels
Milestone

Comments

@monghuz
Copy link

monghuz commented Sep 28, 2016

Please fill in these details so that we can help you!

System Details

  • Operating system name and version: Win 10
  • VS Code version: 1.5.3
  • PowerShell extension version: 0.7.2

Issue Description

When I using the auto complete feature for network path the leading double backslash changed to single one. As a result of it after every time I need to read the missing backslash to the beginning of the path.

Example before the autocomplete feature used
\\my\share
At this point I see the sub folders and files as expected.
Then:
\my\share\folder1

@mpearon
Copy link

mpearon commented Apr 29, 2017

I encountered the same behavior, and got a response:
#681

@daviwil
Copy link
Contributor

daviwil commented Jun 1, 2017

Hey @monghuz, I apologize for the extremely long delay in response! Are you still seeing this issue in the latest VS Code and PowerShell extension versions?

@daviwil daviwil added this to the June 2017 milestone Jun 1, 2017
@monghuz
Copy link
Author

monghuz commented Jun 1, 2017

Hey @daviwil,

Sadly yes. I just upgraded to 1.12.2 but the issue is still there.
To repro the issue you can create a share (abc) on your local pc and try to resolve the address
type:
\\yourPC\a
hit ctrl + space

result should be
\yourPC\abc

@daviwil
Copy link
Contributor

daviwil commented Jun 1, 2017

Can you try it in the VS Code Insiders release? I believe they fixed it recently but the fix hasn't made it to the main VS Code release yet.

@mpearon
Copy link

mpearon commented Jun 9, 2017

Rejoice, @monghuz As of 1.13.0, this is corrected! :)

@daviwil
Copy link
Contributor

daviwil commented Jun 9, 2017

Yep, this should be fixed now, let me know if you still see it after installing the VS Code 1.13.0 update which just got released yesterday.

@daviwil daviwil closed this as completed Jun 9, 2017
@daviwil daviwil modified the milestones: June 2017, 1.3.0 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