Welcome to Vifm Q&A, where you can ask questions about Vifm usage. Registration is optional, anonymous posts are moderated. GitHub or Google logins are enabled.
0 votes
in vifm by


I have problem launching vifm on the windows network directory. I am using msys2 with vifm obtained from the package manager.

I have no luck launching with command vifm , vifm . , vifm //networkname, vifm "//networkname" on the terminal

Even when inside vifm, I tried command :goto //networkname and it says: "Path doesn't exist: /networkname"

Thank you for your help

1 Answer

0 votes
Best answer


msys2 is based on Cygwin and so is Unix-like environment. This means that that build doesn't have Windows-specific features like :volumes command or Windows paths support including UNC paths.


Is there any workaround to get this working on msys?


No, I don't really know how to compile it as a Windows application against Unix-like curses.


Assign the network drive to a drive letter in windows e.g. z:
Then mount your network drive using fstab entry in msys2:

z: /mnt/mountpoint smbfs binary,user,notexec 0 0

Then use vifm and navigate to it from /mnt/mountpoint, you will no longer experience issues with UNC paths or path errors.

If you would like to make a bug report or feature request consider using GitHub, SourceForge or e-mail. Posting such things here is acceptable, but this is not a perfect place for them.

Support Ukraine