KiTTY
KiTTY copied to clipboard
Mouse Scroll
Not sure if this is a issue - But i could scroll terminal output with my middle mouse scroll button. Does not work anymore?
Hi @riaanp78 ,
I've this problem too with last releases running it in Windows 10.
I have just upgraded from kitty-0.74.4.13.exe to kitty-0.76.0.7.exe.
The former was OK.
With the latter, mouse scroll seems to scroll the terminal buffer, but is not passed down to applications. So, for example, if I have vim opened in the terminal, and a large file in vim, I can only scroll the file with keyboard
See #344 for more information.
Encountering this issue with a telnet session running 76.0.7p (portableapps) on Windows 10. Scrollback using mousewheel works as expected regardless of how I initiate the session. However, if I go to "Change settings..." and click "Apply", mousewheel no longer controls scrollback. I am still able to scroll backward using the slider on the right side of the window.
I am able to restore mousewheel functionality by using the "Reset Terminal" option.
I do have the same problem when opening a shell from Midnight commander. Also I can't select text with left muse button anymore after using Midnight Commander. Only Reset terminal seems to solve that problem!
I also noted this behaviour of losing mouse wheel scrollback after using "Font settings -> Negative", in 0-.76.0.6. Also double clicking content with the left mouse button does not select it. Both issues are solved by using "Reset Terminal".
Both issues are solved by using "Reset Terminal".
Interesting. I'll check it. Thank you for reporting it.
Hi,
I confirm what @pjhitchman has commented: the issue could be solved using "Reset Terminal". I don't know the root cause of the problem.
I hope this will help to fix the bug. Regards.
I'm not sure if this is related but with the recent update to KiTTY, I can no longer scroll inside an emacs buffer. (nor in vim/vi either). emacs enables mouse reporting by sending "esc[?1000h". This works in PuTTY and was working fine in KiTTY up until I think 0.76.0.10. Works in 0.76.0.8. So it's broken in either .9 or .10.
I'm not sure if this is related but with the recent update to KiTTY, I can no longer scroll inside an emacs buffer. (nor in vim/vi either). emacs enables mouse reporting by sending "esc[?1000h". This works in PuTTY and was working fine in KiTTY up until I think 0.76.0.10. Works in 0.76.0.8. So it's broken in either .9 or .10.
This is exactly the problem. Any application which enables the mouse (vim/tmux/emacs/etc) have stopped working in Kitty 0.76.*. Personally I found is hasn't worked since the first 0.76.x.x, and still doesn't work.
Is there a chance this is a new setting we need to enable in the config? Its been a problem for what seems like year now and its getting to the point where using 0.74 as a workaround is no longer viable because of changes to SSH. (I get around it be tweaking key algorithms on the server, but that isn't always an option).
Also, as mentioned above, move this discussion to #344
Please test 0.76.0.11 which contains a fix for #344, which will likely fix this as well
testing for a few days - will report back if the scrolling issue is still there. Thank you
On Tue, Sep 13, 2022 at 12:47 AM David le Blanc @.***> wrote:
Please test 0.76.0.11 which contains a fix for #344 https://github.com/cyd01/KiTTY/issues/344, which will likely fix this as well
— Reply to this email directly, view it on GitHub https://github.com/cyd01/KiTTY/issues/359#issuecomment-1244657492, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADU2IYUZP3KMRS4ZWJBZ2A3V56XJFANCNFSM5MEP34CA . You are receiving this because you were mentioned.Message ID: @.***>
Looks like version 0.76.0.11 solved the problem!
Seems to be working for me as well
Thank you, I confirm seems to be fixed!
From: David le Blanc Sent: 12 September 2022 23:47 To: cyd01/KiTTY Cc: Michael Grant; Comment Subject: Re: [cyd01/KiTTY] Mouse Scroll (Issue #359)
Please test 0.76.0.11 which contains a fix for #344, which will likely fix this as well — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>