-
val
i was literally just considering forking and ripping out all the ai slop, collab, etc from zed, and then I discovered gram! I just installed and it is already running *faster* than zed, and i dont even need to specify any extra settings to stop lsp downloads and stuff :D
-
krig
nice 😄
-
sylfn
Hi there! A friend told me to try Gram and it feels nice (and even better than Zed when I tried it about a year ago) and has most of the features I use. I'm on 2.1.2 from nixpkgs, with plenty of RAM available and a recent-ish integrated graphics card. The problems I have stumbled upon are: 1. Ctrl+Q does not allow quitting if there is a window that has A. no directories opened in it, B. unsaved unnamed buffers. These buffers are not restored in case of crash (simulated by pkill -15 gram) either. If the window has any directory open in it, then it's fine. 2. Large files (> 10MB) hang Gram on opening with no indication that something is happening 3. Long files (> 1M lines) hang Gram on editing lines. Synthetic file for test can be obtained with `yes aaaaaaaaaaaaaaaaaaaaa | head -10000000` 4. Markdown preview does not use monospace font for "code" and "pre" 5. Markdown preview scrollbar is offset from right border, making it a harder target to click on (see Fitts's law and how hard it is to click on GitLab's scrollbar since about a year ago). 6. Markdown preview scrollbar does not exist? I can only click on "thumb", but not on the "track" (using CSS terms; in other words, I can click only on the moving part, but not on where the moving part could be to scroll there) 7. "New", "Split pane", "Zoom In" group of buttons (on the right of opened tabs list) hides when menu is opened and briefly appears when menu section changes (e.g. from "Gram" to "File")