Skip to content

Conversation

SoundOfScooting
Copy link

Original author: @trymeouteh

vscode-launcher only appears in the context menu of the parent/current directory while vscodium also appears on directories contained inside it. When run on a contained directory, it counter-intuitively opens the current directory instead.
vscode-launcher also doesn't appear for the root folder or folders with no name (like Trash).

vscodium has Extensions=dir; instead of vscode-launcher's Extensions=any;, but because of the above changes I don't think it will matter.

Original author: @trymeouteh

`vscode-launcher` only appears in the context menu of the parent/current directory while `vscodium` also appears on directories contained inside it.
When run on a contained directory, it counter-intuitively opens the current directory instead.
`vscode-launcher` also doesn't appear for the root folder or folders with no name (like Trash).

`vscodium` has `Extensions=dir;` instead of `vscode-launcher`'s `Extensions=any;`, but because of the above changes I don't think it will matter.
@SoundOfScooting
Copy link
Author

SoundOfScooting commented Jun 13, 2025

Sorry if this PR does not follow the proper procedure. I realize that it doesn't update the version number or changelog.
@trymeouteh if you're okay with the changes here, can I try updating the action's version number in this PR too?
The README says that in order to get this merged you have to review or approve it.
If you prefer I can instead make this into an issue and let you handle whatever changes you want to make.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant