- The scrollback contents need to reside somewhere. Currently it's on disk (compressed as of 0.40, but still). We shouldn't surprise users by filling up their disks.
- Content rewrapping on resize starts to become noticably slow at around 100.000 lines of scrollback.
IMO scrollback buffer is a conveniece feature, not something you should heavily rely on to be present under all circumstances. If you're running a command that you expect to produce lot of output and you do need the whole output, you should redirect that to a file.
That being said, you can increase it for yourself even to infinite and deal with the drawbacks. Given these drawbacks, I don't think the default should be bigger than 10.000 - 50.000-ish.
Beware that:
- The scrollback contents need to reside somewhere. Currently it's on disk (compressed as of 0.40, but still). We shouldn't surprise users by filling up their disks.
- Content rewrapping on resize starts to become noticably slow at around 100.000 lines of scrollback.
IMO scrollback buffer is a conveniece feature, not something you should heavily rely on to be present under all circumstances. If you're running a command that you expect to produce lot of output and you do need the whole output, you should redirect that to a file.
That being said, you can increase it for yourself even to infinite and deal with the drawbacks. Given these drawbacks, I don't think the default should be bigger than 10.000 - 50.000-ish.