Warp
Warp copied to clipboard
Allow Full Scroll-back / setting the number of max lines
Describe the bug
Terminal.app allows for a lot more scroll-back than Warp when running commands with a lot of output. Warp trims the output a lot more than Terminal.app.
To Reproduce
Steps to reproduce:
- Run a command that produces a lot of output
Expected behaviour
Warp to allow full scroll-back (just like Terminal.app)
Screenshots
No response
Operating System
MacOS
OS Version
12.2 Beta (21D5039d)
Additional context
No response
This has been triaged. As high priority. No ETA thouguh
Has there been any updates on this? This is the only feature that I would need to fully switch over to warp
same here, whenever I run some large tests and need to debug it I had to switch to mac default terminal for it
Not 100% clear if this is the same, but when I scroll up to read the output of a long-running process, and that process outputs new lines of text, then my scroll position adjusts (as if I scrolled down); INSTEAD, I would expect my scroll position to remain static (so I can read the output).
Hi Folks, Thanks for your patience! I'm happy to say this request is on the roadmap and being worked on, we'll post any updates on this thread.
any updates on this @dannyneira ?
Yes @marwan116, this is still being worked on, no ETA quite yet as it's a little complicated given the performance issues infinite scrollback could cause.
@dannyneira Even bumping it to 10x what it is would be helpful, if infinite is difficult.
@tillkruss Yes, the current 10k limit could be 100k or more, unlimited, etc. we're investigating what options make sense and will post updates on this thread when we have them.
It is common for me to have a single command spew more than 10k lines that I need to search through. For now, ITerm will have to do, but looking forward to not having to switch, grep or output to a file.
Also hit the issue of cut output. Looks like a bug when you look at it and it is missing output from the beginning of the command. More so than in regular terminals as they will not scroll back enough to show you the command line nor previous commands.
Warp would do well to include a marker line where output has been cropped due to buffer limitations, wherever that limit ends up being.
Created a new ticket that was closed a dupe for this.
We have some xcodebuild scripts that run for a while and output fairly long logs. It appears that blocks in Warp eventually truncate these logs preventing me from seeing all parts of the log when I need to debug.
I've also had issues with not all the lines at the end being preserved in a block. This is a frequent enough issue for me that I've now benched Warp for some time. I'll come back to it in the future to re-evaluate when this has been fixed.
Right now I have to use iTerm and Warp both.
Tailing log is one of the most crucial parts of development and debugging. Waiting for this.
Any updates? Infinite scrollback is a must have for any dev!
Bump. Any updates?
Hey @tyrelh this is still being worked on, no ETA quite yet as it's a little complicated given the performance issues infinite scrollback could cause.
Any updates? We are not expecting you to make it default, just make it adjustable please 💛
an "experimental opt in" to increase the lines would be amazing
I agree, please make this adjustable. We can deal with performance by just clearing when necessary, but it makes it very difficult to not see long running test output.
bump
Yeah, bump it good. I gave up on warp because of this limitation.
I’ve had to do the same I’m afraid. I’ll be back to Warp in an instant the moment this is implemented.
On Tue, 15 Aug 2023 at 20:15, vladst3f @.***> wrote:
Yeah, bump it good. I gave up on warp because of this limitation.
— Reply to this email directly, view it on GitHub https://github.com/warpdotdev/Warp/issues/610#issuecomment-1679383392, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAILQ6E6UPEYHEW7MA2AQPLXVO4CXANCNFSM5MDLIKKQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>
-- Eduardo Turiño
@.***
I am sure that the team is really working on this but would be good to provide the status of the development of this feature, including the complexity.
Hey folks, quick update, this feature has had some work done, but we're looking to work on it more in the coming quarter (mainly to improve the performance and memory consumption). We're slowly but surely chipping away at it so we appreciate your patience. Still no official ETA on launch. 🤞
Quick preview of the feature (what we have so far in Dev):

🎉🍾🎆
I am looking forward to this change!
waiting on this as well, looking forward to infinite/no cutoff
though not perfect, i would be statisfied in short term with only the last block having unlimited lines (with 10k scrollback for all other blocks) if memory usage is really hard to improve
Sadly this limitation is why I'm still using iTerm2 and not Warp. Basically only this one thing is preventing me from switching 🙂
Moving back to iTerm, because of this!