Change was originally made for #15741 to list VS Code as an option (not the default) for opening directories and files. Which distribution are you seeing the issue with ? Also did you have a default handler before VS Code was installed xdg-mime query default inode/directory ?

Do you have any links to documentation that say the opposite?

@Tyriar the distro is not at fault here.

The problem keeps recurring on package upgrade, so for years I've sought guidance at #114425 .
It's a bit tiresome.

An idea I have is to record down the user's default file explorer before updating the desktop and MIME databases, and afterwards, use xdg-mime to set the default for inode/directory back to their preferred file explorer. I'm unsure whether the distro has a default value set in the first place for that MIME type, and whether the xdg-mime command is available.

I haven't seen any command that allows us to update the desktop and MIME databases while allowing us to state that we explicitly don't want to be the default application for a given MIME type.

@deepak1556 I'm seeing the behaviour on voidlinux in KDE/Dolphin and Sway/Nemo.
is #15741 a nautilius specific remedy?

I don't think having VSCode advertising inode/directory is the right way to go.
I suspect the priority and/or hijack issue might be as simple as alphabetic order of the executable named code, but I don't know how to verify that.

Here's another report of people affected by this issue:
https://bbs.archlinux.org/viewtopic.php?id=282278

Please help make it stop 🙏

I believe the issue is that the commands we use don't control what order the entry gets placed into the file. I've had similar issues with brave, and so I believe it is an alphabetical order issue. I wrote up a comment at #114425 (comment)

@rzhao271 we should reopen #15741 if the behavior has now been reverted.