File does not open via UNC path #2885
Comments
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. |
Can confirm I'm seeing this behavior on 0.115. |
Closing as duplicate of #2313 |
This will be fixed in the next release, 0.116 |
Thank you Kevin! I appreciate it. |
So is it really fixed? |
@iamstarkov Can you try and let us know? |
I have a follower in twitter which complain about this error, so I just wondering is it fixed or not |
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? |
Nope, not working for me on atom 1.5.3 windows 8.1 64bit. |
I have atom 1.5.4 on Windows 7 64bit and also have the same issue |
Same issue here on Windows 10 build 1511 with atom 1.7.3 still not fixed |
Same issue on Mac running 1.7.4, I've had to switch to VSCode today just to get my work done :( |
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! |
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.
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).
The text was updated successfully, but these errors were encountered: