#Mountain duck delelet folder not working windows#
Using the net use command in Windows to mount a folder as a Network Drive.Īgain this works for some applications, but unfortunately has a big performance hit.Įspecially the VSCode intelesense server seems to struggle a lot. Unfortunately Git seems to break through the substitution and uses the real path. This works for some applications, but breaks Git and VSCode. Using the subst command in Windows to mount a folder to a drive letter. I stopped trying as sync performance via the WebDAV protocol is terrible. Using Mountain Duck and WebDAV to see if I can choose a mount point. Why is it working for me, but not for them?Īnd here are some workarounds I’ve tried: That’s a recipe for long nights of debugging.
The path I get will always be different to the path someone has who I’ve shared something with. Having special characters like ö,ä,ü,etc. But I do have a special character in my last name. In my case that’s not that big of an issue. Like Python, Rust, Blender and Nuke, just to name a few. This can result in many hard to debug problems when using those paths in certain software.
Here’s a non exhaustive list of problems:įirst and foremost there is a whitespace in the path - My😟Libraries. Now I generally don’t like paths being “forced” on me, but in this case it creates some real problems. I can’t change the “main” library containers - “My Libraries”, “Shared with all”, etc. I can/have to choose the root folder - seafile. What I mean by custom root is the ability to customize the root drive and folder SeaDrive uses.įor example my current path on Windows looks like this:Īt the moment I only have control over a limited part of that path. Custom SeaDrive root possible? Custom SeaDrive root possible?
0 kommentar(er)
