The Gram Code Editor - 2026-10-16


  1. Savoita

    I am looking at the Flatpak integration in Gram, and it seems like.... it just immediately tries to exit the sandbox?

  2. koru

    Savoita, why not install using a package manager?

  3. Savoita

    I am using secureblue, and Gram is not available via Flathub, Homebrew for Linux, or (maybe?) `rpm-ostree`. It may be possible to do the latter, but I prefer to use Flatpak where possible, because of the improved sandboxing provided. ✎

  4. Savoita

    I am using secureblue, and Gram is not available via Flathub, Homebrew for Linux, or (maybe?) `rpm-ostree`. It may be possible to do the latter, but I prefer to use Flatpak where possible, because of the improved sandboxing provided. ✏

  5. Savoita

    Currently, it seems that Gram (probably because Zed did it) uses the `org.freedesktop.Flatpak` permission to allow itself to immediately exit the sandbox. So I'm trying to figure out how difficult it would be to remove that permission, and keep Gram within the Flatpak sandbox.

  6. Savoita

    I notice the hyperlinks on the [CONTRIBUTING.md](https://codeberg.org/GramEditor/gram/src/branch/main/CONTRIBUTING.md), under "Bird's-eye view of the code base", direct to a 404 (for example, `cli` directs to `https://codeberg.org/crates/cli` rather than `https://codeberg.org/GramEditor/gram/src/branch/main/crates/cli`). Is that intentional, or is it something I might be able to PR a fix for? ✎

  7. Savoita

    I notice the hyperlinks on the CONTRIBUTING.md, under "Bird's-eye view of the code base", direct to a 404 (for example, `cli` directs to `https://codeberg.org/crates/cli` rather than `https://codeberg.org/GramEditor/gram/src/branch/main/crates/cli`). Is that intentional, or is it something I might be able to PR a fix for? ✏

  8. koru

    Thank you, I open PR to fix that.

    👍 2
  9. randomeel

    hello

  10. krig

    Hello!

  11. willowispll

    configured gram with nix, its my main editor now!