vscodium: Codium not detected by github desktop

Describe the bug

Github desktop (hereafter as ghd) is not recognising VSCodium on my system

Checklist

  • This bug doesn’t happen if I use Microsoft’s Visual Studio Code. It only happens in VSCodium.
    sorry, i cant confirm that as i dont use VSCode --> refer my first comment
  • I checked the Docs page and my issue is not mentioned there.

Steps To Reproduce

  1. Open ghd
  2. Go to “Files > Options” (<kbd>^</kbd><kbd>,</kbd>)
  3. Then go to “Integrations > External Editor”
  4. See that VSCodium is not there

Expected behavior

VSCodium should be there

Screenshots

image

Environment

  • OS: Windows 10 20H2
  • Architecture: x64
  • Codium: 1.61.2
    from VSCodium-x64-updates-disabled-1.61.2.msi installed in “Program Files” (i.e. i guess for all users)
  • Ghd: 2.9.4 in “AppData/Local”
  • NP++: 7.9.5 in “Program Files”
  • Typora: 0.9.98 (beta) in “Program Files”

Additional context

Duplicate 🔍 github desktop

P.S.: issue template’s modification inspired mainly by: inkscape inbox’s template

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 23 (5 by maintainers)

Most upvoted comments

@yashpalgoyal1304

hey @LuNeder can you translate your proposed fix to windows?

I don’t use Windows, so unfortunately I have no idea how to do that.

As a workaround, you could probably use Linux instead

A workaround that works fine for me:

  • Create file /usr/bin/code
  • Add the following contents to the file: codium $1
  • Make it executable: sudo chmod 755 /usr/bin/code
  • GitHub Desktop should now detect “Visual Studio Code”, select it and whatever you choose to open will open on Codium.

WIP: https://github.com/GitMensch/desktop/commit/d2e24a69c16dc092ede782fb6a675c5315ba1a79 - as soon as I know what IDs to actually use, I’ll amend it with those and a nice commit log, then create the PR

Cool, I’ll send a PR (it will be untested as I don’t use that software, but it likely helps some users, so why not). I’ll reference it here and then close it as “external issue”.

As a workaround, you could probably use Linux instead

i so want to do that, but honestly, i don’t have enough confidence/competency to do that

If you do want to do that, maybe go with a version which is more near to MS Windows (including possible use of proprietary tools), and if the confidence is missing just go with a Live System first (you can put that on an USB drive and boot from there “until confident”).