codium as app executable name instead of vscodium? #1501

New Issue

Closed

opened 2025-09-10 23:53:34 -05:00 by giteasync · 14 comments

giteasync commented 2025-09-10 23:53:34 -05:00

Owner

Copy Link

Originally created by @435vic on GitHub.

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.

Originally created by @435vic on GitHub. 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.

giteasync closed this issue 2025-09-10 23:53:34 -05:00

giteasync commented 2025-09-10 23:53:35 -05:00

Author

Owner

Copy Link

@drasbeck commented on GitHub:

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.

@drasbeck commented on GitHub: 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`.

giteasync commented 2025-09-10 23:53:35 -05:00

Author

Owner

Copy Link

@JL2210 commented on GitHub:

See number #28.

@JL2210 commented on GitHub: See number #28.

giteasync commented 2025-09-10 23:53:35 -05:00

Author

Owner

Copy Link

@dzmitry-lahoda commented on GitHub:

For pwsh:

New-Alias code vscodium

@dzmitry-lahoda commented on GitHub: For `pwsh`: ``` New-Alias code vscodium ```

giteasync commented 2025-09-10 23:53:35 -05:00

Author

Owner

Copy Link

@435vic commented on GitHub:

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

@435vic commented on GitHub: I see... Well, that does make sense. Thank you!

giteasync commented 2025-09-10 23:53:35 -05:00

Author

Owner

Copy Link

@JL2210 commented on GitHub:

Just make a symlink or an alias.

@JL2210 commented on GitHub: Just make a symlink or an alias.

giteasync commented 2025-09-10 23:53:35 -05:00

Author

Owner

Copy Link

@JL2210 commented on GitHub:

No, put alias code=vscodium in your bashrc.

@JL2210 commented on GitHub: No, put alias code=vscodium in your bashrc.

giteasync commented 2025-09-10 23:53:35 -05:00

Author

Owner

Copy Link

@stripedpajamas commented on GitHub:

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.

@stripedpajamas commented on GitHub: 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.

giteasync commented 2025-09-10 23:53:35 -05:00

Author

Owner

Copy Link

@stripedpajamas commented on GitHub:

I think @dzmitry-lahoda is on Windows @JL2210

@stripedpajamas commented on GitHub: I think @dzmitry-lahoda is on Windows @JL2210

giteasync commented 2025-09-10 23:53:35 -05:00

Author

Owner

Copy Link

@bittner commented on GitHub:

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

@bittner commented on GitHub: Can we reopen this issue? I'd like to fix this problem for everyone.

giteasync commented 2025-09-10 23:53:35 -05:00

Author

Owner

Copy Link

@bittner commented on GitHub:

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.

@bittner commented on GitHub: 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.

giteasync commented 2025-09-10 23:53:35 -05:00

Author

Owner

Copy Link

@drasbeck commented on GitHub:

Thanks @bittner. 💪

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

@drasbeck commented on GitHub: Thanks @bittner. 💪 Now I'm happily waiting for this change to silently appear via homebrew.

giteasync commented 2025-09-10 23:53:35 -05:00

Author

Owner

Copy Link

@stripedpajamas commented on GitHub:

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

@stripedpajamas commented on GitHub: Yes that's where the change should be made -- that's the part that updates the product.json file right before building.

giteasync commented 2025-09-10 23:53:36 -05:00

Author

Owner

Copy Link

@bittner commented on GitHub:

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

Thanks @stripedpajamas and @paulcarroty! 🥇 🥂 🍾

@bittner commented on GitHub: Everyone looking into upgrading your `vscodium` package, please [read my hints](https://github.com/VSCodium/vscodium/pull/176#issuecomment-501396622) in the PR. :eyes: Thanks @stripedpajamas and @paulcarroty! :1st_place_medal: :clinking_glasses: :champagne:

giteasync commented 2025-09-10 23:53:36 -05:00

Author

Owner

Copy Link

@bittner commented on GitHub:

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.

@bittner commented on GitHub: Cool, thank you! I'm not totally sure, but shouldn't it possible to simply change the value for `applicationName` in [build.sh](https://github.com/VSCodium/vscodium/blob/master/build.sh#L24)? 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](https://github.com/VSCodium/vscodium/blob/master/.travis.yml#L29-L33).

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

master

insider

1.112.01907

1.110.11631

1.110.11607

1.110.11602

1.110.01571

1.109.51242

1.109.41146

1.109.31074

1.109.21026

1.109.01000

1.108.20787

1.108.10359

1.107.18627

1.107.18605

1.106.37943

1.106.37938

1.106.27818

1.105.17075

1.105.17017

1.105.16999

1.105.16954

1.105.06922

1.105.06808

1.104.36664

1.104.26450

1.104.16282

1.104.06131

1.104.06114

1.103.25610

1.103.15539

1.103.15418

1.103.05312

1.102.35058

1.102.24914

1.102.14746

1.102.04606

1.101.24242

1.101.14098

1.101.03933

1.100.33714

1.100.23258

1.100.13210

1.100.03093

1.99.32846

1.99.32704

1.99.32562

1.99.22418

1.99.12392

1.99.02289

1.99.02283

1.99.02277

1.98.2.25078

1.98.2.25077

1.98.2.25072

1.98.1.25070

1.98.0.25067

1.97.2.25045

1.97.1.25044

1.97.0.25037

1.96.4.25026

1.96.4.25017

1.96.3.25013

1.96.2.24355

1.96.1.24353

1.96.0.24352

1.96.0.24347

1.95.3.24321

1.95.3.24320

1.95.2.24313

1.95.1.24307

1.94.2.24286

1.94.2.24284

1.94.1.24283

1.94.0.24282

1.94.0.24281

1.93.1.24256

1.93.0.24253

1.92.2.24228

1.92.1.24225

1.91.1.24193

1.91.0.24190

1.90.2.24171

1.90.1.24165

1.90.0.24158

1.89.1.24130

1.89.0.24127

1.89.0.24126

1.88.1.24104

1.88.1.24102

1.88.0.24096

1.87.2.24072

1.87.1.24068

1.87.0.24060

1.86.2.24057

1.86.2.24054

1.86.2.24053

1.85.2.24019

1.85.1.23348

1.85.0.23343

1.84.2.23319

1.84.2.23317

1.84.2.23314

1.84.0.23306

1.84.1.23311

1.83.0.23283

1.83.1.23285

1.83.0.23277

1.82.3.23277

1.82.2.23257

1.82.0.23250

1.82.1.23255

1.81.1.23222

1.81.0.23216

1.80.1.23208

1.80.2.23209

1.81.0.23215

1.80.0.23188

1.80.1.23194

1.79.2.23166

1.79.1.23164

1.79.0.23159

1.78.1.23131

1.78.2.23132

1.78.1.23130

1.77.3.23102

1.77.1.23095

1.77.2.23101

1.77.0.23095

1.77.0.23093

1.77.0.23090

1.76.0.23062

1.76.1.23069

1.76.2.23074

1.75.1.23040

1.75.0.23033

1.74.3.23010

1.74.2.23007

1.74.0.22342

1.74.1.22349

1.74.2.22355

1.73.1.22314

1.73.0.22306

1.72.2.22289

1.72.2.22286

1.72.1.22284

1.72.0.22279

1.71.2.22258

1.71.1.22256

1.71.0.22245

1.70.2.22230

1.70.1.22229

1.70.1.22228

1.70.1

1.70.0

1.69.2

1.69.1

1.69.0

1.68.1

1.68.0

1.67.2

1.67.1

1.67.0

1.66.2

1.66.1

1.66.0

1.65.1

1.65.2

1.65.0

1.64.1

1.64.2

1.64.0

1.63.1

1.63.2

1.63.0

1.62.3

1.62.2

1.62.1

1.62.0

1.61.2

1.61.0

1.61.1

1.60.2

1.60.1

1.60.0

1.59.1

1.59.0

1.58.2

1.58.0

1.58.1

1.57.1

1.57.0

1.56.0

1.56.1

1.56.2

1.55.0

1.55.1

1.55.2

1.54.2

1.54.3

1.53.1

1.53.2

1.53.0

1.52.1

1.52.0

1.51.0

1.51.1

1.50.1

1.50.0

1.49.2

1.49.3

1.49.1

1.49.0

1.48.1

1.48.2

1.48.0

1.47.0

1.47.1

1.47.2

1.47.3

1.46.0

1.46.1

1.45.0

1.45.1

1.43.2

1.44.0

1.44.1

1.44.2

1.43.1

1.43.0

1.42.0

1.42.1

1.41.1

1.41.0

1.40.2

1.40.0

1.40.1

1.39.0

1.39.1

1.39.2

1.38.1

1.38.0

1.37.1

1.37.0

1.36.1

1.36.0

1.35.1

1.35.0

1.34.0

1.33.1

1.33.0

1.32.2

1.32.3

1.32.1

1.32.0

1.31.1

1.31.0

1.30.2

1.30.0

1.30.1

1.29.1

1.29.0

1.28.2

1.28.1

1.28.0

1.27.2

1.27.1

1.26.1

1.26.0

Labels

Clear labels

bug

bug

discussion

documentation

downstream

duplicate

enhancement

extension

good first issue

help wanted

invalid

never-stale

pull-request

Mirrored from GitHub Pull Request

question

stale

telemetry

upstream

wontfix

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

giteasync

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: VSCodium/vscodium#1501