The Gram Code Editor - 2026-09-29


  1. krig

    yeah doesn’t look good…

  2. frafav

    I realized gram doesn't highlight the files by git status, they all have the same colors in the left panel. I tried playing around with the config, but nothing really changes. I wonder if I'm doing something wrong. I'm on 3.3.0, I immediately thought of trying to compile from git, but maybe there are more rational approaches :P

  3. krig

    There is a Git Panel setting for Status Style: choose Label Color. But that’s in the git panel. In the project panel it should show by color if Git Status is enabled under Project Panel in the settings

  4. krig

    if that doesn’t work the problem could be your theme

  5. frafav

    I'm using the stock theme, pretty much all stock. I hate customize things in general, unless I have a strong argument to tweak I leave it be. I was using the bin version, I'm recompiling just in case some recent update broke stuff without me noticing...

  6. krig

    hm. Should work with the default theme. Probably one of the panel settings then.. not sure what the defaults are there

  7. frafav

    actually I should start fresh, because now that I think about it, I actually messed up with the settings, tried to use the hx-style... but i felt a bit strange, it was like using helix just with more panel 😅. I'm not ready for it yet. So I'll reset the config and see how it goes (after it finishes compiling)

  8. krig

    yeah it’s easy to lose control 😅 there are a lot of settings

  9. frafav

    nope, still the file color/highlight doesn't change. I'd expect to see a file that I change and it's mentioned in `git status` to have a somewhat different color, but it doesn't. I recompiled v 3.3.0 and reset the ~/.config/gram/settings.jsonc (removed the one I had before)

  10. koru

    > yeah doesn’t look good… krig, what you think about sourcehut or self-hosted instance (like does LibreWolf, they mirror to Codeberg)? ↺

  11. nicoco

    It has been a few years (and I am still a paying customer), but sourcehut was crucially lacking "org" features when I used it for slidge. This is what made me migrate to codeberg.

  12. nicoco

    I love the snapiness of their UI and most things about it, but forgejo's proper commenting UI for patches is very valuable IMHO.

  13. harper

    Agreed

  14. krig

    @frafav Well, I am not sure what the defaults are. So you may have to turn on git status coloring for the project panel to get it working

  15. krig

    but it should work!

  16. frafav

    I've reset everything, just in case, even the files at ~/.local/share/gram I changed a random file in the project, I can see it listed in git status, but the style doesn't change in the project panel (see pic https://www.pasteboard.co/ZoEMYGYDQobn.png)

  17. krig

    I have a sourcehut account, but although I like it philosophically, sourcehut still doesn’t quite make sense to me (as in I can’t figure out how to use it effectively). Plus what I’d really want is something more decentralized. The nice thing about radicle in theory is that issues and PRs are stored in the git repository, and i can mirror all my dependencies on my own node but it’s still not an island like running my own forego..

  18. nicoco

    does srht have orgs now? I know that I hated that I had no way of getting my project out of *my* namespace, especially since my plan was to make a community-thing, not a me-thing.

  19. nicoco

    hosting forges is PITA in the era of AI crawlers. gajim just moved from their selfhosted gitlab instance to gitlab.com recently because it was too much work to maintain their instance.

  20. krig

    @frafav not sure what might be going on then :/

  21. nicoco

    I love the idea of decentralisation and federation, obviously, but hosting the forge is going to drain hours of work from someone (krig, likely ^^)

  22. frafav

    I'll try compiling from git. I'm on gentoo with a very minimal installation, maybe I'm missing some core-thing. but the log doesn't seems to point to any git-related issue

  23. krig

    I just tried running a completely “clean” instance (with GRAM_STATELESS=1 gram) and the colors work for me out of the box. @frafav which platform are you on?

  24. krig

    ah, I see. It could be a git version mismatch perhaps.. but that seems odd

  25. koru

    > I love the idea of decentralisation and federation, obviously, but hosting the forge is going to drain hours of work from someone (krig, likely ^^) We still don't have federated Forgejo (ForgeFed), sad. ↺

  26. frafav

    @krig linux, gentoo using wayland (gnome 50)

  27. krig

    take a look at the logs (I think they are in ~/.cache/gram/logs/Gram.log) and see if there is anything weird going on @frafav

  28. krig

    right now I am hoping that either codeberg figures federation out, or I can hold on there long enough for an alternative to pop up

  29. krig

    lots of people thinking about github alternatives right now at least

  30. koru

    > I'll try compiling from git. I'm on gentoo with a very minimal installation, maybe I'm missing some core-thing. but the log doesn't seems to point to any git-related issue frafav, is that ebuild related issue? ↺

  31. frafav

    @koru, I don't think so. Both the gram-bin and gram ebuild gave me a completely fully working editor, it just this color thing that is having issues

  32. koru

    > lots of people thinking about github alternatives right now at least I recently saw new git forge, but don't remember the name, but idea was like Radicle. ↺

  33. harper

    There's Tangled, but it's taken VC money

  34. koru

    Yes, that is. Thank you!

    👍 1
  35. frafav

    hm, the log are not that clear, when I edit any file it says "WARN [project.format.local.code-actions] No code actions were resolved, continuing"

  36. krig

    yeah tangled is weird, seemed promising but there are weird VC/LLM vibes and it’s kind of fake-decentralized in the same way that bluesky is

  37. harper

    Agreed on the vibes. I don't think I mind ATProto though (the protocol for Bluesky and Tangled, among others)

  38. krig

    I’m very suspicious of it, mostly because I don’t understand it :D

  39. frafav

    ahhh, "solved it"

  40. koru

    > yeah tangled is weird, seemed promising but there are weird VC/LLM vibes and it’s kind of fake-decentralized in the same way that bluesky is But I like idea of re-create "general" Git forge UI: https://tangled.org/tangled.org/core ↺

  41. harper

    Blacksky has done some great work on actually-independent infrastructure that still interoperates

  42. krig

    yeah I haven’t given up on tangled completely.. but yeah, vibes are not great

  43. harper

    Beyond just the Personal Data Server, I mean

  44. harper

    I was so excited about Tangled at first

  45. frafav

    it's my .gitignore that was creating issues. for some reason this works in Zed. Basically my .gitignore is set up to ignore anything :P, so it would be impossible to add a file unless using -f

  46. krig

    aaah right so everything was getting ignored

  47. krig

    that makes some kind of sense :D

  48. krig

    interesting that it’s handled differently in zed.. not sure what may have changed there

  49. frafav

    yes, but git doesn't ignore the tracked files, regardless of the .gitignore, so coloring/highlight-ignoring should only be applied to the untracked files

  50. frafav

    I guess I can live with it.. now that I have all that free space in the right panel I can have the git panel open all the time, and I have an even richer info, the diff stats, with the number of lines changed

  51. frafav

    but curiously, the window & layout git status "Show Git Status In Tabs" works correctly, so it changes the style of the tabs when three are uncommitted changes. omg how many configurations options are there 😵

  52. krig

    way too many.. there’s a bunch of settings that aren’t exposed in the UI too 💀

  53. krig

    but yeah interesting, I guess the problem is that gitignore is applied before checking if a file is tracked.. I’ll write that down

  54. krig

    should be fixable

  55. frafav

    I think it could be in entry_git_aware_label_color https://codeberg.org/GramEditor/gram/src/commit/main/crates/editor/src/items.rs#L1715 the `if ignored` condition doesn't allow for tracked files to display

  56. frafav

    hu, apologies, I didn't know it would see the underscores as markdow :)

  57. krig

    it depends on the client I think.. but a commonmark-compliant markdown implementation shouldn’t parse underscores in the middle of a word. tsk tsk 😄

  58. frafav

    in zed it's almost the same method: https://github.com/zed-industries/zed/blob/9307bb7dc5bd249290a2877231837bf4b54b8b7e/crates/editor/src/items.rs#L2266 but the `if ignored` is the last condition

  59. frafav

    I wonder i there is a reason for the reordering

  60. frafav

    it's also missing the deleted status, so maybe there are also other reasons for the change

  61. frafav

    hm, there is only one way to find out :P

  62. frafav

    if only codeberg would work today 🙄

  63. frafav

    an no, I can't fork the gram repo in codeberg, it gets out of my quota, I guess `quota_model.EvaluateForUser`... well. I think I should actually work on my stuff, I'll try again tonight.

  64. koru

    frafav, you don't need fork to contirbute. use AGit https://forgejo.org/docs/latest/user/git-cli/agit-support

  65. ashleytg

    gram keeps crashing... 😭

  66. ashleytg

    every time i have more than one gram window open, it crashes 💔

  67. ashleytg

    the specifications are more specific, like one ore more windows have to be open for a while, then i try to open another one

  68. ashleytg

    lol.. moving all my stuff over to Nix... saw > "disable_ai": true, rewrote the : to an = (Nix), but then realized... GRAM DOESN'T HAVE AI :D

  69. krig

    nothing to disable!

  70. ashleytg

    yea :3

  71. ashleytg

    very exciting

  72. frafav

    well, I checked and it works, it also restored the deleted color status, taking the full function as it was in Zed, I used the AGit feature to submit a PR, hopefully it's OK