Extend range of neovide_scroll_animation_far_lines

[unphased]

I am in love with the smooth scrolling because I find it really helps me soak in the code while i edit it and to think about it in a spatial way.

I found one of the best things neovide does is give me a better sense of immersion in my code files as a space to inhabit by hopping around locations in the code. being able to smoothly move between locations helps me better contextualize those locations compared to not scrolling.

I find that I want even more out of the scroll animation lines distance setting. currently we can set this config setting to any value from 0 to a high value, but no matter how high i set the value,

• only an amount of lines capped by the height of the screen will be shown scrolling once hopping beyond a screen's worth of vert distance
• if we scroll too fast, intermediate content starts getting skipped
• some time is spent with blank background shown whenever content skipping happens

I feel like in the experience of using neovide, the illusion of having all the code accessible to us is so close to being complete, but only if we keep the scroll velocity low. I would very much appreciate being able to avoid having any artifacts appear regardless of scroll velocity. I also believe scroll velocity should be uncapped. If I hop from the top of the file to the bottom of the file, I am bothered not by megabytes flitting before my eyes, indeed the intuitive perception of relative speed here would be a wonderful perfect way to estimate and immersively, viscerally feel the filesize of the file. Indeed it will provide useful information to me how much code is traversed with each hop performed by any cursor position change. That intuition of spatial awareness is something that is robbed from me by cutting the transit short to a single screen height!

The behavior as it is now surely comes from a pragmatic approach to make the rendering scalable, so we could open million line files (itself already challenging for neovim itself to consume, though, depending on plugins) without having their content all in the GPU.

I hope that if an analysis is made, GPU memory consumption should be quite low even for millions of line files, and going beyond a few million lines would be made unscalable by neovim itself. I haven't looked into the code yet, but I wonder if doing it this way could simplify some complexity that exists? I have also seen some flickering during scrolling sometimes.

I'd like to know if the maintainers are interested in exploring this, if so I'd be happy to take a dive in the code and see what improvements could be made.