Allow Full Scroll-back / setting the number of max lines

[fishcharlie]

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:

1. 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

[elviskahoro]

This has been triaged. As high priority. No ETA thouguh

[Michael-Choi]

Has there been any updates on this? This is the only feature that I would need to fully switch over to warp

[szhou42]

same here, whenever I run some large tests and need to debug it I had to switch to mac default terminal for it

[evangrim]

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).

[dannyneira]

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.

[marwan116]

any updates on this @dannyneira ?

[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.

[tillkruss]

@dannyneira Even bumping it to 10x what it is would be helpful, if infinite is difficult.

[dannyneira]

@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.

[arkD]

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.

[kaos]

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.

[jblaker]

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.

[shampoobera]

bump

[vladst3f]

Yeah, bump it good. I gave up on warp because of this limitation.

[eturino]

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 <#610 (comment)>, 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 ======== ***@***.***

[bountyC0d3r]

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.

[dannyneira]

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):

[sorens]

🎉🍾🎆

I am looking forward to this change!

[j-ro]

waiting on this as well, looking forward to infinite/no cutoff

[scullionw]

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

[jannolii]

Sadly this limitation is why I'm still using iTerm2 and not Warp. Basically only this one thing is preventing me from switching 🙂

[rafaelcdelgado]

Moving back to iTerm, because of this!

[romansme]

its crazy that this issue is open for almost 2 years, CRAZY

[silva96]

its crazy that this issue is open for almost 2 years, CRAZY

being the #1 reason devs abandon warp, makes it even crazier.

[QuenKar]

any update? It seems that unlimited rows is still not supported until now?

[faultaddr]

2 years... warp ,bye bye

[Lokavidu]

ok I think I waited long enough, bye warp

[dannyneira]

Sorry closed by accident, reopening, this is still on the radar with no firm ETA.

[bountyC0d3r]

You better keep it closed... it has been almost 2 years now and still no ETA, we even don't know if there will be a fix for this issue or not.

[nihaals]

Maybe this should be locked?

[ev01ve]

I left because of this issue. Iterm2 + Atuin is a better solution anyway. If you need the AI stuff add Fig.

What are people using Warp for, that cannot be done better with Iterm2 + Atuin + Fig?

[nabinkhadka]

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):

What happened to this partial solution?

[dannyneira]

The partial solution has caused some performance and memory consumption issues, so we've decided to hold off on release until we can work thru those issues. Locking this issue to prevent spam. We are aware of the demand and appreciate your patience with us not having a firm ETA on this. We'll post any updates on the thread.

[dannyneira]

Hi Folks, quick update on this request. We have made some early progress noted above, but will be dedicating more resources to get this over the finish line later this year, most likely Q3 2024. We appreciate your patience with our small (but growing) team and we'll post more updates as we have them.