The Gram Code Editor - 2026-03-24

thedoctor: thanks! haven't done "actions" in a while, and in woodpecker CI you can use a plugin "just for its container" and change what you run in it, so I got confused

Just a small note, having `.gram/settings.jsonc` checked in makes sense, but is slightly annoying. I have "format_on_save" toggled on as my global settings. But apparently it was not used for the yaml forgejo action workflow. so, to avoid unwanted changes for my PR, I toggled it off for the project. and now I have untracked changes for `.gram/settings.jsonc`. 🤷‍♀️

it should really be opt in to use project-specific settings

just haven’t had time to fix that

> Hm, I think I am giving up on appimage for now.. can’t get it to build in CI or on my local machine :/ Hm, what errors do you get? I downloaded `pkg2appimage` as an AppImage from GitHub and put it in `~/.local/bin` (and made it executable). Once that's in place a call to `script/bundle-linux --appimage` works on my machine. ↺

> it should really be opt in to use project-specific settings That wouldn't solve my very specific (and tiny) annoyance: I have "format_on_save": "on" in my global settings, I like that as a default, but I need to turn it off to avoid formatting that release.yaml. I think a "fix" here would be to let gram format the yaml files of its own repo, or add "format_on_save": "off" to the project-specific files. Anyway, that's beyond yak-shaving probably, let's just forget it :) ↺

regarding appimage it looks like there is a problem running them inside docker. Not that they failed to build. See here https://github.com/AppImage/AppImageKit/issues/828

hmm I see.. yeah there was a workaround so it didn’t require FUSE to build, but it still didn’t succeed for me

> regarding appimage it looks like there is a problem running them inside docker. Not that they failed to build. See here https://github.com/AppImage/AppImageKit/issues/828 Wow, this is *old*. I mean, personally, I think AppImage is a very weird package format and not really worth pursuing all that much. I just thought it might be nice to have, if it's low-hanging fruit. If it's just too much hassle to get going, uploading a manual build to releases would be an option, directing users to bundle one for themselves or even just leaving it altogether. ↺

yeah that’s my feeling too… looking at pkg2appimage they recommend not using any ubuntu repo newer than 18.04, and that’s the latest update

I think flatpak -> flathub is the way to go. Am tempted to remove the snap support as well, haven’t tested it and all I know about snaps is that it’s a mess 😄

I'm on Ubuntu and ripped out all the snap plumbing wholesale so there's that. I have no idea whether snap is a good fit for an editor, I'm inclined to say the same thing about low-hanging fruit but I have no idea if snaps are worth it. Flatpak is a bit weird because of the sandboxing but, as far as I can tell, the current implementation just sidesteps this and works fine so that's nice.

my current headache is getting my new fancy runner up.. it has ipv6 which is causing all kinds of issues with podman and rootless containers. and I’m too stubborn to back out of this hole I have dug for myself

yeah I have tested the flatpak and it seems to work, so that’s good enough for me for now 😄

> yeah I have tested the flatpak and it seems to work, so that’s good enough for me for now 😄 You said, there's an open PR for Flathub, right? Can you post a link? ↺

No I got as far as cloning the flathub repo and messing that up, so there is no PR yet

if that’s something you are willing to have a look at, that would be great!

would be nice to get the worst wgpu bugs fixed and tag a new release first though

Ah, I see. I could take a look but I can't promise anything. I have no experience with flatpak packaging. Zed does have a package on Flathub, I suppose it's too naive to just copy that and replace "zed" with "gram" everywhere?

oh I think we have everything needed in that sense, if you run the flatpak build from the gram repo it also produces a json file, and I think that’s the thing needed to submit to flathub

so yeah I don’t _think_ we need to copy anything from zed

they want some screenshots, those are available from the website..

anyway there is no pressure, only do it if you want to :)

I'll look into it of or when I have then time 🙂 Anyway, it looks like the `bundle-flatpak` script basically just pulls in the prebuilt binaries, is that valid for Flathub?

yeah not sure how that all works to be honest..

> All source available submissions must be built entirely from source code. This requirement applies to the main application component defined in the manifest, as well as any runtime dependencies included in the manifest. From here: https://docs.flathub.org/docs/for-app-authors/requirements#building-from-source

Hello, Pablo here, I have some questions about the language servers. First, i noticed i can use my own version of them, thank you very much for that, but i would like clarification of what "let the editor install them for you" means. It will try to use my systems package manager, its own, where do they end up? Can i put them in containers and use docker/podman to run them directly from Gram?

It will download them to its own storage (where exactly depends on the OS), usually by grabbing the latest tagged release from Github. But exactly what and how depends on the language server, each one has its own implementation and some you have to install yourself

No containers as far as I know, no

On Mac they will be stored in ~/Library/Application Support/Gram, on Linux I think it’s ~/.local/share/gram

Thank you.

It's usually either a standalone binary or something like a node application.

Hey all, for extensions that do not have an extension.toml file (like the Tailwind ext: https://zed.dev/docs/languages/tailwindcss), how would we install those in Gram? From looking at Zed's list of open extensions, it seems like a lot of them are built-in?

The tailwind one is built in, yes

you can add it to a language in the settings file, but it’s not exposed in the UI yet

https://gram.liten.app/docs/languages/tailwindcss/

Oh thanks! Somehow missed that part of the docs.

I keep finding things I haven’t seen still 😅

1.2.0 released now, since it seems the wgpu patches to solve the issues some people had at least. And now the Debian repository is up and running :)