The Gram Code Editor - 2026-05-28

Hi, documentation at https://codeberg.org/GramEditor/gram/src/branch/main/docs/linux.md says: "Note: At the time of this writing RPM package signing does not work. In order to be able to install Gram you need to set gpgcheck=0 inside /etc/yum.repos.d/rpm.repo." 1. Is it OK to fill an issue in CB so I can be subscribed to it and be notified when it will be resolved? 2. Is this issues being actively in progress or is it left inactive as low priority?

Hi! As far as I know this is not being worked on, but I bet there is a codeberg issue for this already.. don’t have a link handy though

@brainchild Hi, and welcome :) The format on save-setting is confusing but I don’t think changing the defaults will do much to make it less so, and it will be a breaking change for everyone. So I am inclined not to change the defaults. However, I do think the settings UI needs to be improved to make it clearer which settings can be overriden per language and if they are and where

Thanks Krig for reply, in gram repo there are only 19 issues open. I searched for gpgcheck and rpm and haven't found anything relevant open. Is it ok to open new one then?

uh, I see now it is a codeberg issue not gram. Isn't there a workaround to publish RPM repo without using codeberg limitation here? it also feels there could be an open issue in Gram repo, just for newcomers wanting to subscribe to it, nobody will search CB repos for that issue.

I made my comment there: https://codeberg.org/GramEditor/gram/issues/288 - if needed, we can continue discussion there ideally

Ah yeah it’s not something we can fix ourselves