codium as app executable name instead of vscodium?

[435vic]

The titles, names, and executables in the official and OSS versions all are variations of code and code-oss respectively. Maybe we should keep the pattern by making the executable codium? Also I think the Visual Studio name is copyrighted by Microsoft, not sure, but we might as well be careful. Something else I like about the original code executable is that it's very quick to type, enabling commands like code ~/very/big/path feel more fluent and quick.

[JL2210]

See number #28.

[435vic]

I see... Well, that does make sense. Thank you!

[drasbeck]

I like the idea of codium instead of vscodium, because it eases the onboarding of new users.

@435vic, if things stay unchanged (and it looks like they do) you could always just create a symlink to vscodium, called codium.

[JL2210]

Just make a symlink or an alias.

[dzmitry-lahoda]

For pwsh:

New-Alias code vscodium

[JL2210]

No, put alias code=vscodium in your bashrc.

[stripedpajamas]

I think @dzmitry-lahoda is on Windows @JL2210

[bittner]

Can we reopen this issue? I'd like to fix this problem for everyone.

[bittner]

Personally, I'd like to stick to the pattern that the non-free distribution follows:

• VSCode --> code
• VSCodium --> codium

That will make it also easier for developers transitioning from VSCode to VSCodium.
Muscle memory is a thing that is hard to overcome.

[stripedpajamas]

All yours @bittner 💙

This is a breaking change, so proceed with caution. Making the change should be simple (change product.json pre-build). I suppose we will need a big notice in the changelog of the next release that lets people know that vscodium will no longer work (and therefore anyone who has alias code=vscodium will break as well). I'm not sure if any extensions are affected. Some extensions try to call the binary itself... I remember this coming up in an issue a couple of weeks ago but I don't recall where it ended up.

[bittner]

Cool, thank you!

I'm not totally sure, but shouldn't it possible to simply change the value for applicationName in build.sh? I'll try that in a PR. I hope the build will tell me when things break.

Do we have functional tests? I don't see any. We may want to add a simple one (à la "run codium --version") to the before_deploy: block or after calling ./build.sh in .travis.yml.

[stripedpajamas]

Yes that's where the change should be made -- that's the part that updates the product.json file right before building.

[bittner]

Everyone looking into upgrading your vscodium package, please read my hints in the PR. 👀

Thanks @stripedpajamas and @paulcarroty! 🥇 🥂 🍾

[drasbeck]

Thanks @bittner. 💪

Now I'm happily waiting for this change to silently appear via homebrew.