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

UNC filepaths do not appear to be supported in Windows #37

Open
tbttfox opened this issue Feb 24, 2016 · 0 comments
Open

UNC filepaths do not appear to be supported in Windows #37

tbttfox opened this issue Feb 24, 2016 · 0 comments

Comments

@tbttfox
Copy link

tbttfox commented Feb 24, 2016

I'm using windows 7. I don't have a linux box to test this on, unfortunately.

Say I open a UNC file path on our network, such as \\source\dev\tbttfox\path\to\file.py
And then hit the '-' key to start FileBeagle. At this point, I see a proper listing of the current directory, but I cannot navigate from there.

If I try to open any file in the shown directory, it will instead try to open C:\source\dev\tbttfox\path\to\anyfile.py
If I try to go up a directory with the '-' key, It tries to open C:\Windows\system32\source\dev\tbttfox\path\to\, and I get a blank directory with only the ..\ option.
If I try to go up a directory by choosing the ..\ line, I get a FileBeagle: [Error] Cannot open directory: source\dev\tbttfox\path\to\ (note the missing preceeding slashes)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant