Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

File does not open via UNC path #2885

Closed
dcerman opened this issue Jul 9, 2014 · 15 comments
Closed

File does not open via UNC path #2885

dcerman opened this issue Jul 9, 2014 · 15 comments
Labels
bug windows Issues that occur on Windows but not on other platforms.

Comments

@dcerman
Copy link

dcerman commented Jul 9, 2014

Using Atom version 0.114.0-f6400a4 on Windows 8.1, I cannot open files via UNC paths (e.g. \server\share\folder\index.html). The tree view accurately shows the files and folders available. However, when I open a file, the editor tab appears, but its content is empty, as though it is a new file. The content in the file does not appear. I have reproduced this behavior with HTML, JavaScript, CSS, and plaintext files.

atom-unc-bug

The status bar in the above screenshot might provide some insight to what is going on.

The file opens properly when accessed via a mapped drive letter to the same network location (e.g. U:\folder\index.html where U: is mapped to \server\share).

@speveril
Copy link

I ran into this as well, using 0.113.0 on Windows 8.1. Take note of the filename at the bottom -- it seems to triple the name of whatever you opened via Open Folder... If you then save the file it will (silently) create a (for instance) server\share\server\share\folder\ directory structure inside \server\share, and put the saved file there.

@Windos
Copy link

Windos commented Jul 15, 2014

Can confirm I'm seeing this behavior on 0.115.

@batjko
Copy link
Contributor

batjko commented Jul 15, 2014

This has already been reported in previous issues: #2313, #2961 and #2948.

Keep an eye on those, I'm sure it's currently being worked on.

@kevinsawicki
Copy link
Contributor

Closing as duplicate of #2313

@kevinsawicki
Copy link
Contributor

This will be fixed in the next release, 0.116

@dcerman
Copy link
Author

dcerman commented Jul 22, 2014

Thank you Kevin! I appreciate it.

@iamstarkov
Copy link

This will be fixed in the next release, 0.116

So is it really fixed?

@batjko
Copy link
Contributor

batjko commented Jul 15, 2015

@iamstarkov Can you try and let us know?

@iamstarkov
Copy link

I have a follower in twitter which complain about this error, so I just wondering is it fixed or not

@batjko
Copy link
Contributor

batjko commented Jul 15, 2015

I don't have any network to open files from, so whoever has the issue should update to the latest version (if applicable) and see how it goes.

I have heard from some people that it is now working fine, but I don't know how representative that is.

Note that the original issue is still open, though the most recent comments seem to suggest it's doing fine now?

@zacps
Copy link

zacps commented Mar 6, 2016

Nope, not working for me on atom 1.5.3 windows 8.1 64bit.

@Weechit
Copy link

Weechit commented Mar 10, 2016

I have atom 1.5.4 on Windows 7 64bit and also have the same issue

@eldblz
Copy link

eldblz commented May 8, 2016

Same issue here on Windows 10 build 1511 with atom 1.7.3 still not fixed

@brandonk3nt
Copy link

Same issue on Mac running 1.7.4, I've had to switch to VSCode today just to get my work done :(

@lock
Copy link

lock bot commented Apr 7, 2018

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!

@lock lock bot locked and limited conversation to collaborators Apr 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug windows Issues that occur on Windows but not on other platforms.
Projects
None yet
Development

No branches or pull requests

10 participants