Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't scroll in linux repo #25

Closed
iveqy opened this issue Feb 1, 2018 · 3 comments
Closed

Can't scroll in linux repo #25

iveqy opened this issue Feb 1, 2018 · 3 comments
Labels

Comments

@iveqy
Copy link

iveqy commented Feb 1, 2018

So the linux repo is pretty huge. tig is really slow here, but grv is starting quicker (the second time it's started). Anyway, scrolling in the linux commits makes grv to display some errors:

https://asciinema.org/a/WSYzGvewkcX3BAsZWqmypBjnV

@rgburke
Copy link
Owner

rgburke commented Feb 1, 2018

Thanks for reporting this, and for the demo as well. I haven't tried GRV on the linux repo yet but it looks like it would be a good stress test.

@mckellyln
Copy link

mckellyln commented Feb 25, 2018

I have a similar issue. I'm using Ubuntu 16.04.
Scrolling Commit or Diff window up to top (causing scroll) after scrolling down to bottom (causing scroll) does not display properly - some lines are not redrawn - only a few lines near the top of the window update.
Interestingly if I do this slowly, like one line at a time (not holding down arrow buttons) then it seems so far to display correctly.
xterm, xterm-256color, screen-256color terminals all show same issue.
But vt100 works ok. (of course no color, etc. so not really a solution - but perhaps it helps with terminfo/ncurses debugging ??)
ok - outside of tmux it works fine with xterm-256color - so I suppose this is looking more like a tmux/ncurses interaction (if my issue is same as here)

ok - final update - if I set term to screen-256color and restart tmux - then it works ok :-)
(I was previously using xterm-256color with tmux)

@rgburke
Copy link
Owner

rgburke commented Jun 22, 2018

This should be resolved on master. Please see #39 for more details.

@rgburke rgburke closed this as completed Jan 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants