The Gram Code Editor - 2026-06-25

Hi, I installed gram on Fedora 43 using dnf as per instructions. When it started I was offered some basic config options but clicking them didn't select them. I also tried keyboard navigation - I could tab around the fields but not change any. I proceeded with the finish setup anyway, then tried to change from the settings menu: same problem!

Yeah this is a bug with file watchers, fixed in main but not released yet. If you restart the editor it should work, it’s the first start that is messed up :/

I'm still having the same problem after restarting

Check the log with command palette: open log, see if there are any hints there.. It might be that the editor doesn’t have permission to create file system watchers, maybe..

I see this: [notify::inotify] unable to remove watch descriptor from inotify: Os { code: 22, kind: InvalidInput, message: "Invalid argument" }

ooh. Maybe something has changed with inotify arguments in 43… will see if I can figure it out when I have time

Noob question: Does gram have a CLI mode? or is it always a GUI app?

It’s always a GUI app yeah, there is a CLI but only as a way to open files in Gram from the command line.

personally I still use neovim from the terminal together with gram, switching between them. It might be possible to provide a TUI in the future, but there is nothing right now

oh, ok, thanks. But damn! I'm having such problems with neovim since the treesitter-cli dev got burnt out and now I can't install it on Debian oldstable. ... anyway I digress!

could take a look at flow: https://flow-control.dev/ It should install anywhere and has a vim mode, though I think it’s pretty primitive still

...and written by/with Claude :-(

(FWIW I came here because of the no AI stance. )

Yeah. :/ I don’t _think_ it’s full on vibe coding there, I have had some interaction with neurocyte who is making it and yeah his stance on LLMs is more open to it than I am personally..

Generally things are looking grim for us... For gram there are dependencies that are being vibe-coded now, and even rust itself seems to be headed in that direction. And Linux, systemd, rsync…

Well, all the best anyway. Thanks for info + chat. xx

No worries! And I am hoping to release an update soon, hopefully I can figure out what the problem you’re seeing is coming from.

Hi, I appreciate the project, effort and motivation for gram, as a former zed user. I was wondering if it would be possible to make publishing a (non-generated) source archive a part of the release materials on codeberg? It makes package workflows for package managers building source easier when you can download something from, say `https://codeberg.org/grameditor/gram/releases/download/<tag>/gram-<tag>.tar.gz`, rather than the generated source archive URLs. I'd really appreciate it!

Hmm I don’t know if I quite understand, what is the problem you are seeing with https://codeberg.org/GramEditor/gram/archive/2.2.0.tar.gz ? I haven’t looked at those archives myself so I don’t know exactly what they look like :)

Well when you download them, the output filename is of course just the `<tag>.tar.gz`, which I manually rename in my package description since it could otherwise conflict with other file names, but is also not self-describing, especially in a `/var/cache/fetch` full of source archives fetched for packaging. In addition, when you extract the contents of the archive, the contained directory is just `gram` rather than `gram-2.2.0`, so i also rename that for the uniformity

I see. I wonder if I can influence that somehow. It would be annoying to have two separate source archives linked from the release.. Will look into it

There is an option to disable the generated source archives specifically for this reason, it's just on the release page below where you add assets. It's what I use on my projects, so only the archives I add appear.