The Gram Code Editor - 2026-03-25


  1. kebg

    Congrats! Just updated. Question about settings, specifically `settings.jsonc`. Is there a schema I can use to get the json language server to work and auto-complete settings? https://gram.liten.app/docs/languages/json/

  2. kebg

    This is/was a nice feature of Zed is while I edit settings.json, I get the auto-complete and hints.

  3. fapuro

    hi all! I'm trying to run Gram on my slack machine but the binary doesn't run due to glibc version (slack 15 has version 2.33 :/ ) and the binary: `./bin/gram: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by ./bin/gram)`. My question would be, is glibc >=2.34 a real requirement or could it work with 2.33 if I build from source?

  4. kebg

    Hmm I also can't get icons to show up in the file tree even after installing some other icon themes.

  5. kebg

    (on Linux, using the flatpak)

  6. kebg

    AH nevermind about the icons. Realized it was disabled by default.

  7. thedoctor

    > hi all! I'm trying to run Gram on my slack machine but the binary doesn't run due to glibc version (slack 15 has version 2.33 :/ ) and the binary: `./bin/gram: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by ./bin/gram)`. My question would be, is glibc >=2.34 a real requirement or could it work with 2.33 if I build from source? I'm afraid you're out of luck then. AFAIK, the glibc version is an actual requirement.

  8. krig

    Yeah I think 2.33 is just too old, unfortunately

  9. krig

    Regardings schema for settings.jsonc it’s the same as Zed - so it should work. I may have broken the LSP hack to get it to pick up the schema when I renamed from json to jsonc. So this would count as a bug I think.. please file an issue (or I’ll do it unless I forget)

  10. harper

    I've updated to gram 1.2.0, and I'm not enabling software rendering. We'll see if I get any more weird rendering issues.

  11. krig

    Sounds good! I know that there is more work to do. Surface resize handling is not fully implemented, and device loss (suspend) is also not handled well. But I have gotten my hands on a laptop with a radeon GPU now so should be able to test a bit better.

  12. harper

    Yeah I saw you said that. Hopefully finishing that stuff helps, because it happened again. I took a screenshot and opened an issue

  13. harper

    This issue happens without the system suspending, so it's not that

  14. krig

    Thank you, yeah this looks like something else

  15. harper

    It also happens without me resizing anything

  16. harper

    Oh hold up

  17. harper

    I just looked at the logs, and it's trying to run on my Nvidia GPU. No wonder it's messed up (do we care about cursing here?)

  18. krig

    oh, hang on.. there is an environment variable you should be able to set to convince it to pick the right GPU

  19. harper

    I'm more interested in disabling that GPU from the BIOS or in the kernel. I'm working on that now.

  20. krig

    that works 😄 it’s GRAM_DEVICE_ID otherwise

  21. krig

    documented here https://gram.liten.app/docs/linux/

  22. harper

    Cool, thanks

  23. harper

    Very annoying my laptop doesn't seem to have an option to disable the Nvidia GPU entirely

  24. harper

    Gotta use a kernel config ig

  25. harper

    So far so good, after using envycontrol to disable the Nvidia GPU

  26. fapuro

    on glibc 2.33: thedoctor, krig, thank you, appreciated! I'll see what I can do :)