search

Exafunction / codeium

Other
219 stars 10 forks source link

Allow configuring the path of the codeium language server in VSCode #70

Open marius851000 opened 1 month ago

marius851000 commented 1 month ago

Hello. I am interested in using codeium in VSCodium on NixOS.

I manage my VSCodium extensions using NixOS, which mean their path a non-writeable, and so, it can’t download the Language Server. In addition, it doesn’t a global linker.

However, NixOS provide a codeium package, providing a patched language server (by modifying some elf header hard-linking a linker, something quite common when working on non-compiled-from-source programs).

That mean that, for getting codeium on NixOS with NixOS-managed extension, there needs to be:

  1. A way to specify a path to the language server (I could circumvent that by linking the executable in the binary expected by extension, but might need update every time there is an LS update on the server)
  2. A way to not perform the CRC check (as the patching of the language server does indeed change it).

ps: the name of the binary in NixOS (in the PATH) is codeium_language_server. If those two things mentioned previously are possible, I could potentially make a NixOS package.

marius851000 commented 1 month ago
  1. Also make the chmod operation non-fatal/do not make the chmod when the file is already executable (the FS where the extension is stored is read-only)
marius851000 commented 1 month ago

That put aside (by patching the extension.js file to disable that CRC check and to not execute the chmod), it work well. It’s definitivelly not good enought for me to make a package of it (especially the 1st point, and I would like to avoid having to patch obfuscated js too, which I believe is against the TOS), but I’ll keep using that for my personal use.

Thanks