Edit locally should only open explorer/finder and highlight file instead of opening in standard app

[pschopen]

The "edit locally" function ist a huge improvement in NC as you sometimes need special software or features that Collabora doesn't provide. However, often users want to choose which software should open the file individually. Why does the "edit locally" button not only point onto the file within the explorer / finder? Then you can decide what should happen with the file individually.

That already does work for folders e.g. I would suggest the same behaviour for files, too.

[Rello]

Hello,

this is not how "edit locally" works, as the name says. The users are expecting a quick edit without additional clicks. In a standard setup, there is only one app per filetype.
As a workaround you can remove the local filetype link in your OS to trigger the pop-up every time.

But from Nextcloud side we cannot separate if a) or b) is supposed to happen. We just trigger the OS' standard behavior.

[pschopen]

Does it make sense to offer an alternative "show in file manager"? And then only point to the file inside the explorer or finder?

[jospoortvliet]

Why not then do 'edit locally' on the folder? You then have all the files, that's what I do... I would not want to add much more complexity and options to the menu, to be honest.

[pschopen]

Why not then do 'edit locally' on the folder? You then have all the files, that's what I do... I would not want to add much more complexity and options to the menu, to be honest.

Is also what I do so far, but it becomes very unhandy when there are many files in one folder.

However, I do see the point that more options are also more confusing. I would have preferred to remove "edit locally" for "open locally" and have only pointed to the file within the file explorer. Then the user had every possible option to work with the file the OS offers.

[i2h3]

The "edit locally" function ist a huge improvement in NC as you sometimes need special software or features that Collabora doesn't provide. However, often users want to choose which software should open the file individually. Why does the "edit locally" button not only point onto the file within the explorer / finder? Then you can decide what should happen with the file individually.

This is what will happen starting with the upcoming version 34 in case of the file provider. The macOS app sandbox does not allow us to programmatically open file provider items. See pull request #10305.