If HTML file is selected, just nvALT and Unknown with a Sublime Text icon is showing up as editor in the context menu plus a long empty menu. Selecting Unknown doesn't open Sublime Text. Selecting .htaccess is working and gives MacVim and Sublime Text as available options. Tried resetting lsregister with no avail.
Do you see the same issue in File → Edit With?
Yes, same issue in Edit With menu (see attachment). After upgrading to Cyberduck 6.3.3, on the first run of the new version there were some valid editors in both menus, though the first two were named unknown next to the nvALT and Xcode icon. The initial issue returned immediately after quitting and restarting Cyberduck. Only in Preferences the list of alternative editors is showing all my valid editors correctly.
Please try to rebuild the launch services database using /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -v -apps u in a Terminal.app window.
Hello dkocher. Sorry for not replying immediately to your last comments.
I was trying to rebuild launch services database without success before I have been opening this ticket in 2017 for Cyberduck version 6.3.2.
While I have been without access to internet for quite some time, Cyberduck version 7.x got released. However, even without rebuilding launch service db, with Cyberduck version 7.0.0 the bug suddenly disappeared. The menu with list of editors returned to normal behavior and remote html files could be opened in an editor of choice through the context menu and the main menu.
As of Cyberduck version 7.0.2 the bug suddenly returned. The difference to version 6.x is, that rebuilding launch services database is now a working solution for the bug and the menu works again. Maybe it is just a temporary fix and nvALT is going to reappear as the only selectable editor in the close future. At the time version 7.0.0 was installed, there were also some macOS security patches. Those could have run some maintenance scripts like fetching lsdb. I´ll keep an eye on it and maybe report back, if there is some further remarkable note on the bug.