-
Notifications
You must be signed in to change notification settings - Fork 13
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
feat: scrollback buffer reflow ("soft wrap") #78
Comments
Reproduced: #!/bin/bash
for ((i = 0; i < 90; i++)); do
echo -n "123456789|"
done
echo reproduced-300-wrap.movSetting |
Hey @neg-serg thanks for the issue, so the problem is around the number of columns I have set for Neovim (currently 300). When kitty-scrollback.nvim reads the scrollback buffer into neovim's terminal it hard wraps at 300. When I increase When you say workaround with tmux, what exactly do you mean? |
#78 (comment) hard wrapping at 300 stopped working at some point. #267 should restore the behavior of hard wrapping at 300 columns kitty-scrollback-issue-update.mp4This is a happy medium between working around Neovim's limitation and avoiding a large column setting which impacts performance. Anecdotally > 300 reduced performance. |
The scrollback buffer is hardwrapped due to Neovim limitations (see neovim/neovim#2514).
Example:
kitty-scrollback-issue-update.mp4
vim.o.columns
) to reduce issues with hardwrapping (this will not prevent it but try and have a happy medium with hardwrapping issues and performance) fix: defer setting 'columns' to hardwrap at 300 columns #267Original Issue:
Steps to reproduce:
Generate extremely long newline, for example:
There is only one long string here, but it's impossible to select with pager as the single line. In the same time with the mouse it remains be possible via kitty scroll-back.
Is there any way to get around this problem?
This can often be seen in practice when parsing absurdly large log lines. After this, they are very inconvenient to copy using the keyboard, which adds manual work. The problem can be worked around using tmux, but it increase overall latency.
The text was updated successfully, but these errors were encountered: