Increase default scrollback limit #8593
Replies: 4 comments 11 replies
-
|
you are free to change it yourself the default does not need changed It doesn't matter if most machines have alot of ram today that is a 10x increase. I often have 3 separate instances of ghostty with 5+ tabs or splits running at the same time in all 3 that means the scrollback resources went from 5 * 3 * 10 = 150MB to 5 * 3 * 100 = 1.5G that is a huge difference. 1G is a big factor for many people especially. A real usecase from me. I compile large c++ projects frequently 1G is the difference of builds crashing from OOM or not crashing. They can already take upwards of a few mins to compile with 20+ cores. That is a huge sacrifice to my workflow |
Beta Was this translation helpful? Give feedback.
-
|
My 2¢ is that if you ever find yourself needing more than 10MB of scrollback you should Maybe this will make sense once #111 and #189 are in place, but I think 10MB is more than overkill for the vast majority of users. You're always free to change the limit for your personal config. |
Beta Was this translation helpful? Give feedback.
-
|
I'll throw another use-case into the discussion. I just hit this issue while trying to do a system upgrade (to Fedora 43 beta). Lots of package updates, and DNF put the deleted/downgraded packages at the top of the list, which was cut off. Not so common to do a major system update like this. I had to look for the scrollback-limit config in order to actually see what was going to be happening to my system during an update. A little frustrating, but I think with a settings UI it wouldn't have been too bad, since I could easily find the option through the program. I think the biggest frustration I had was that I didn't quickly know how to see what the default was for scrollback-limit, so I had no clue what to set the buffer to. I didn't see a default listed on the option reference. Not sure if it's listed there and I just can't find. Also, I have a free spinning scroll wheel, so it was pretty easy to get to the top of scrollback buffer. Just bringing it up since it was assumed to be hard to go far back without a scrollbar. Just depends on the mouse. I'm not for updating the default, but maybe this is helpful user experience feedback for future changes to the app. Loving ghostty (especially 1.2.0 with the more stable font rendering). Edit: Found how to see the defaults for config options: |
Beta Was this translation helpful? Give feedback.
-
|
I guess there's a plan for unlimited scrollback-limit. But can't we just persist stuff beyond |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Switched from Warp recently and was surprised to discover that the default scrollback limit is just 10MB.
Working with long agentic flows, it's great to be able to go back in time (especially as Codex CLI and Claude Code continue to increase the number of turns they run before ceding control back to the user).
I'm guessing most developers have machines with a decent amount of RAM, so I want to propose two solutions:
Has anyone else run into this issue upon first install?
Beta Was this translation helpful? Give feedback.
All reactions