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
aborted zsh completion not fully cleared #931
Comments
Are you sure you have 7a4c66b? Does this show the same problem (compare inside and outside tmux):
|
I have 7a4c66b and no, your command line doesn't show any problems. |
Does this also happen in xterm? Make sure TERM is the same outside tmux in both terminals. |
Never mind, this is the same bug in Konsole. I thought you couldn't scroll more than the scroll region, but it looks like you can't scroll the whole scroll region either. Compare this in xterm:
And:
With a scroll region of 3-20 we need to scroll 18 lines to remove the whole thing. 17 is not enough. So 7a4c66b is wrong, and I am going to revert it. tmux needs a working indn if it is specified in terminfo. What did the Konsole guys say to your bug report? You should be able to work around this for now by doing:
|
Yes, it also happens in xterm. |
Commit cb5fcb3 doesn't fix this issue for xterm. |
Show me logs from using xterm with latest master please (only need the server log). |
Sorry, false alarm (had an unnoticed tmux instance running in the background). |
OK cool. I don't think there is a practical way to detect this bug, I think it will need to be fixed in Konsole. |
I would be good if you could open a Konsole bug yourself, because I don't understand the issue sufficiently: |
Ah, found the konsole bug: https://bugs.kde.org/show_bug.cgi?id=379318 |
Yes I think this bug report is fine. If you can figure out how to build Konsole you could try this, which copies the check in Screen::scrollDown() to Screen::scrollUp():
|
Actually that was a very old tree, try this:
|
Thanks. I have created: https://git.reviewboard.kde.org/r/130133/diff/1#index_header (there was an off by one error in your patch, which caused exactly the same issue that I've described above)
|
Not a tmux bug. Lets close this issue. |
For more information, see <tmux/tmux#931>.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
log.tar.zip
Start tmux -> dmesg -> type man m[tab]
type [backspace] to abort:
The text was updated successfully, but these errors were encountered: