The Gram Code Editor - 2026-09-23


  1. nicoco

    Hmm there is trailing whitespace on some changelog entries, someone's not using format on save :)

  2. nicoco

    it's a bit awkward to include the PR number in the changelog, since you can't know it before opening the pull request

  3. nicoco

    I have a WIP that adds this button ⏬

  4. nicoco

    https://chat.slidge.im:5281/file_share/01a0cd52-ba93-772b-b905-c6d6fa71b066/81efed9f-770f-4a08-b117-654c74bef797.png

  5. nicoco

    When viewing a commit diff. I think it is super useful when you review something and want to amend it. Right now I have been using the awkward right-click on filename-> ✎

  6. nicoco

    When viewing a commit diff. I think it is super useful when you review something and want to amend it. Right now I have been using the awkward right-click on filename->reveal in project panel->double click on the path->find the part I want to amend ✏

  7. nicoco

    So I am convinced that the feature is useful, I am just not too sure about the wording "Open Current File" sounds weird, and whether this is the right place to have this button, vs a context menu next-to or repacing "reveal in project panel". thoughts? ✎

  8. nicoco

    So I am convinced that the feature is useful, I am just not too sure about the wording ("Open Current File" sounds weird, maybe?), and whether this is the right place to have this button, vs a context menu next-to or repacing "reveal in project panel". thoughts? ✏

  9. krig

    Oh yeah that is awesome! I wanted to add that

  10. krig

    It’d maybe be nice to combine the open file options into a combo button / dropdown. Maybe like in the git panel there is the … button, we could have that. But intuitively for me the main action should be “open this file in the current tree”, and “view at revision” should be an extended action. We can revise that once the basic feature is merged though

  11. nicoco

    yeah, I'll submit a working PR to start with, nicer UI can be while iterating

  12. krig

    awesome

  13. nicoco

    Is there a way to edit gram with gram without the whole machine becoming irresponsive? 😬 I am very not versed into rust (yet, maybe), but `cargo check ...` background tasks are eating my 8 cores

  14. nicoco

    maybe their "nice" value can be changed, or I can limit how many cores it uses somehow

  15. krig

    ooh well my solution is to work on a Mac M4 ._. it’s painful. I do have a longer term idea of splitting the repo into smaller pieces with something like gpui as a separate project that can hopefully stabilize a bit.. and then also moving all the language support into extensions over time. Try to make the code base smaller. But short term it’s just painful.

  16. nicoco

    yeah, on my work laptop I have a bazilion fast cores it's probably easier next time I'm on it. I should investigate the rust toolchain, I would be very surprised if I couldn't manually set the number of threads used, I'd be fine with it being a slower but not blocking the whole machine :)

  17. krig

    oh yeah that should be possible with an env var

  18. ashleytg

    i just wanted to say...

  19. ashleytg

    i love gram :3

  20. ashleytg

    it's WAY better than zed-

  21. ashleytg

    i hated the ai features in zed 😭

  22. krig

    Thank you! Me too 😅 Well, I never tried it. But just seeing the AI stuff in VS Code pissed me off enough to end up here, haha

  23. ashleytg

    i switch to Gram from VS code because i got frustrated with the weekly updates were about ai, not QOL, or even just bug fixes... unless ofc, the QOL or bug fixes had to do with ai