VSCodium/vscodium
1
0
Fork 0
mirror of https://github.com/VSCodium/vscodium.git synced 2026-04-09 20:50:20 -05:00
Code Issues 135 Packages Projects Releases 10 Wiki Activity

typo in DOCS.md to open vscodium with terminal #1397

New Issue
Closed
opened 2025-09-10 23:52:38 -05:00 by giteasync · 6 comments
giteasync commented 2025-09-10 23:52:38 -05:00
Owner
Copy Link

Originally created by @simooooone on GitHub.

Describe the bug
in vscodium/DOCS.md at the paragraph "How do I open VSCodium from the terminal?" there is a typo. Just tested that to open vscodium on my Fedora 30, I got to give "codium" command instead of "vscodium"

Please confirm that this problem is VSCodium-specific

  • This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

To Reproduce
Steps to reproduce the behavior:

  1. Go to terminal
  2. Click on type vscodium
  3. See bash error

Desktop (please complete the following information):

  • OS: Fedora 30
  • Architecture x86_64
  • Version 1.35.1
Originally created by @simooooone on GitHub. **Describe the bug** in vscodium/DOCS.md at the paragraph "How do I open VSCodium from the terminal?" there is a typo. Just tested that to open vscodium on my Fedora 30, I got to give "codium" command instead of "vscodium" **Please confirm that this problem is VSCodium-specific** - [x] This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium. **Please confirm that the issue/resolution isn't already documented** - [x] I checked [the Docs page](https://github.com/VSCodium/vscodium/blob/master/DOCS.md) and my issue is not mentioned there. **To Reproduce** Steps to reproduce the behavior: 1. Go to terminal 2. Click on type vscodium 4. See bash error **Desktop (please complete the following information):** - OS: Fedora 30 - Architecture x86_64 - Version 1.35.1
giteasync added the good first issue label 2025-09-10 23:52:38 -05:00
giteasync commented 2025-09-10 23:52:39 -05:00
Author
Owner
Copy Link

@stripedpajamas commented on GitHub:

For sure 👍 update screenshot as well if possible

@stripedpajamas commented on GitHub: For sure 👍 update screenshot as well if possible
giteasync commented 2025-09-10 23:52:39 -05:00
Author
Owner
Copy Link

@pshem commented on GitHub:

Looking at github search, there are still 16 files where vscodium is present in the repository: https://github.com/VSCodium/vscodium/search?q=vscodium&unscoped_q=vscodium

  • In the README.md. Changing it there should include a mention of the previous name for returning users
  • In the AppImage recipe (it appears the .desktop file might not have been renamed)
  • In the icons - I don't think there is a point renaming those
  • In DOCS.md
  • check_tags.sh, check_tags.ps1 and update_version.sh only use it to refer to the repository - shouldn't be changed.
  • build.sh - some paces where it's the repository URL, and some places where it's in product.json
  • sum.sh, create_zip.sh, win32-build.yml, sign_dmg.sh, sign_mac_app.sh - should be updated to match the change to the executable name
  • create_appimage.sh shouldn't be changed
  • CODE_OF_CONDUCT.md only has a vscodium email address

All in all, 9 places where the new name should be shown to users.

@pshem commented on GitHub: Looking at github search, there are still 16 files where `vscodium` is present in the repository: https://github.com/VSCodium/vscodium/search?q=vscodium&unscoped_q=vscodium - [ ] In the `README.md`. Changing it there should include a mention of the previous name for returning users - [ ] In the AppImage recipe (it appears the .desktop file might not have been renamed) - [x] In the icons - I don't think there is a point renaming those - [ ] In DOCS.md - [x] `check_tags.sh`, `check_tags.ps1` and `update_version.sh` only use it to refer to the repository - shouldn't be changed. - [ ] `build.sh` - some paces where it's the repository URL, and some places where it's in `product.json` - [ ] `sum.sh`, `create_zip.sh`, `win32-build.yml`, `sign_dmg.sh`, `sign_mac_app.sh` - should be updated to match the change to the executable name - [x] `create_appimage.sh` shouldn't be changed - [x] `CODE_OF_CONDUCT.md` only has a vscodium email address All in all, 9 places where the new name should be shown to users.
giteasync commented 2025-09-10 23:52:39 -05:00
Author
Owner
Copy Link

@stripedpajamas commented on GitHub:

Good catch-- changing the binary name from vscodium to codium was recent. Will need to update the docs to reflect the change.

@stripedpajamas commented on GitHub: Good catch-- changing the binary name from `vscodium` to `codium` was recent. Will need to update the docs to reflect the change.
giteasync commented 2025-09-10 23:52:39 -05:00
Author
Owner
Copy Link

@stripedpajamas commented on GitHub:

Most of those should not be changed. The project remains VSCodium, the binary is codium. The DOCS file should be updated in the section regarding the binary itself (as the OP has mentioned). The build.sh file will need to be updated in certain places as per #193.

@stripedpajamas commented on GitHub: Most of those should not be changed. The project remains VSCodium, the binary is `codium`. The DOCS file should be updated in the section regarding the binary itself (as the OP has mentioned). The `build.sh` file will need to be updated in certain places as per #193.
giteasync commented 2025-09-10 23:52:39 -05:00
Author
Owner
Copy Link

@simooooone commented on GitHub:

Can I fix it?

@simooooone commented on GitHub: Can I fix it?
giteasync commented 2025-09-10 23:52:39 -05:00
Author
Owner
Copy Link

@simooooone commented on GitHub:

Since I've not a Mac, I can't fix other issues apart those in DOCS.md

@simooooone commented on GitHub: Since I've not a Mac, I can't fix other issues apart those in DOCS.md
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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 good first issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
giteasync
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: VSCodium/vscodium#1397
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?