I am looking to console.log a large data object and my buffer/scrollback is cut off; meaning I cannot see the beginning/top of the console.log object. I've tried increasing my scrollback config option, but no matter what change I make to the scrollback value, I get the same result. :/
I am also experiencing this issue on MacOS 10.13.6 with everything else being the same. It appears that the scrollback
option doesn't actually increase the buffer size. I have also tried setting it to 3000
and 10000
with no success.
same here on MacOS 10.14.1 (18B75)
Same here on MacOS 10.13.6
Also unable to apply scrollback MacOS 10.14
Also unhappy! macOS 10.14.1
Same in macOS 10.14.2
same in macOS 10.14.1
Any update on this? Same thing is happening for me on macOS 10.14, I'm guessing this has to do with https://github.com/zeit/hyper/pull/3038#issuecomment-470605698
This is still an issue as of today for me on macOS 10.14.4.
Same here using Ubuntu 18.04.1
I'm facing the same issue with macOS 10.14.5 and Hyper 3.0.2 (stable).
I'm seeing the same issue on macOS 10.14.5 and Hyper 3.0.2 (stable).
The scrollback
config has no effect whatsoever - tested in zsh by running:
$ for i in {1..10000}; echo $i
Output shows that exactly 1000 lines exist from the top of the screen to the top of the buffer regardless of the config value.
I have this issue on both macOS 10.14.5 and Ubuntu 18.04
+1 here
Same on _macOS Mojave 10.14.6 (18G87)_ and _Hyper 3.0.2 (stable)_ limited to 1071 lines despite adding scrollback: 2000
to _.hyper.js_
How is this not a priority? A single console.log response object fills my scrollback....
This is indeed pretty frustrating!
Still a problem in 3.0.2
macOS 10.14.6 (18G3020)
I am also seeing this on Linux with 3.1.0-canary-4 and 3.0.2.
Still issue, MacOS 10.15.7, Hyper 3.0.2. This is a blocker to user adoption and maintaining users in real world scenarios.
Working around limitation this is tedious and cumbersome.
I don't see this issue in new ci builds https://github.com/vercel/hyper/actions/runs/504157911#artifacts
tested on macOs 10.15.7
Most helpful comment
Still a problem in 3.0.2
macOS 10.14.6 (18G3020)