The Gram Code Editor - 2026-03-21


  1. krig

    Yeah if we can build on OBS that would probably be great, they have good infrastructure for all of that.

  2. krig

    Apologies for not being super active here, I need to set up my own XMPP host at some point :D just using the wed interface right now.

  3. krig

    Thought I'd mention here that I am working on releasing 1.1.0. I think things are in a better state than 1.0.0 at least, and I don't think we have any breaking changes? Even the WGPU migration should not break anything, if it does I would count that as a bug. If any of you disagree let me know and I'll tag it 2.0.0 instead. Doing some tests to generate some of the packaging using my forgejo runner, if that works out I will tag the release later today.

  4. Frysog

    Hello, is there any plan musl binaries for gram ? There is an aports in alpine testing repository, but it doesn't build the remote server, so you can't remotely connect to musl machines.

  5. harper

    > Thought I'd mention here that I am working on releasing 1.1.0. I think things are in a better state than 1.0.0 at least, and I don't think we have any breaking changes? Even the WGPU migration should not break anything, if it does I would count that as a bug. If any of you disagree let me know and I'll tag it 2.0.0 instead. Doing some tests to generate some of the packaging using my forgejo runner, if that works out I will tag the release later today. Oh, I should mention that I'm having weird rendering issues on main

  6. harper

    Let me see if I still get those on an older commit (I can't build 1.0 for musl)

  7. harper

    Probably not worth delaying a release for ofc

  8. harper

    > Hello, is there any plan musl binaries for gram ? There is an aports in alpine testing repository, but it doesn't build the remote server, so you can't remotely connect to musl machines. CI has already been set up to build for musl, I believe

  9. krig

    yeah the remote-server binary should be building for musl so that should work with an alpine remote

  10. krig

    weird rendering issues is bad :( what GPU do you have?

  11. krig

    think I am going to release 1.1 anyway, it should work better for most people I hope..

  12. Frysog

    > CI has already been set up to build for musl, I believe > yeah the remote-server binary should be building for musl so that should work with an alpine remote That's awesome. I will try when 1.1.0 releases. Thanks

  13. harper

    > weird rendering issues is bad :( what GPU do you have? So far I haven't seen it happen on the last commit before the WGPU switch. I have an older Intel iGPU (HD graphics 530) paired with an GTX 960M that i don't bother with drivers for, and shouldn't be relevant.

  14. harper

    To be clear, so far it does seem likely to be a 1.1 regression

  15. krig

    Ah.. yes, older Intel GPU would be an issue. I have an Intel Iris (old macbook pro) and it won't even run unless I switch to software rendering

  16. krig

    there is some indication that zed got it to work on those GPUs with the version of wgpu we are on so it should be fixable, hopefully

    👍 1
  17. harper

    Certainly fixable at some level of the stack

  18. krig

    I can run with this btw (not perfect but at least it runs): LIBGL_ALWAYS_SOFTWARE=1 gram --foreground

  19. krig

    hm, ok.. the chat mangled that :D I added it to the README as well

  20. krig

    1.1.0 released https://gram.liten.app/posts/release-1-1-0/

  21. Frysog

    UI Font sizing is broken in 1.1.0 Only gram mono scales correctly. Every other mono fonts you can choose from system is oversized

  22. Frysog

    The breadcrumb font is also oversized for some reason. This is certainly caused by #69