Closed Nathan-MV closed 2 years ago
I do not understand what you are trying to say. Can you explain, please?
In Windows 10 is only Open in Code not Open in VSCode(or any other thing)
I like your idea but I don't think anything is wrong with current behavior. At the time I wrote this extension, I had both VSCode and VSCodium installed. It made sense to me that they were distinguished from each other.
What do you think of:
Open in Code Open in Code(Codium) Open in Code(OSS) Open in Code(Insiders)
What do you think of:
Open in Code Open in Code(Codium) Open in Code(OSS) Open in Code(Insiders)
What if someone installs any of them as a flatpak too along with the native installation? Then flatpaks will be represented as
Open in Code (flatpak)
Open in Code(Codium) (flatpak)
Open in Code(OSS) (flatpak)
Open in Code(Insiders) (flatpak)
And I do not like it.
Basically, I like the old way and I am not willing to change it.
Description
Rename "Open in ####" instances where is used Code-OSS, VSCode, VSCodium and if there is support in the future VSCodeInsiders to "Open in Code" like in Windows.
Explaination
No response