I wonder why using AppImage desktop client is required for the edit locally option in nextcloud to work. Appearently what is missing using a distro package of the desktop client is a mime scheme handler for the nc:// scheme.
I find that stupid.
If you have this working, could you post that file here?
If you know what the command should be, could you post it here? someting like ânextcloud %u` maybe?
Ironically, I can open Nextcloud in my file manager and open any file from there, the âedit locallyâ is just missing the nc:// mime scheme handler .desktop in the system, with a command that redirects to the local mime handler for the file.
When in the web interface, an option for a file is âedit locallyâ. It should open in a native app on my client, like libreoffice, given I have nextcloud desktop client installed - but appearently, installed means âAppImageâ, the arch ânextcloudâ package is not good enough?
For me, it kind of worksâŠsometimes. If I try it repeatedly, Iâd say maybe one out of three times.
Iâm on Arch with Gnome and Firefox using the client from the Arch repositories. So, at least in principle, the AppImage is not required for it to work. And no, I didnât change anything: just installed the desktop client from the Arch repos and left the configuration at its defaults.
However, I donât know why itâs so unreliable, and honestly, I donât have the motivation to investigate further since I donât really need the feature. If itâs important to you, maybe check to see if thereâs already an open issue on GitHub. If not, open one.
Of course, it could also be related to how the Arch package is built, as well as the browser, desktop environment, or window manager youâre using. Therefore, finding the root cause might not be that straightforward.
As I said, it works in principle, at least on my system. By the way, while I had a rough start with it earlier while testing it, the files now seem to open almost instantly on the first try, i.e., without having to click âEdit Locallyâ multiple times, as I wrote in my previous post. Maybe it had to register the nc:// links first, which took too long and caused the file action to time out. Either way, it seems to work for me now.
However, I havenât really looked deeply into how it actually works, and I suppose itâs entirely possible that it might not work at all under certain circumstances. That said, the developers can only improve it if users report issues, since testing it across all the different distributions out there, especially DIY ones like Arch, where nearly every user has a unique setup, is practically impossible.
