-
-
Notifications
You must be signed in to change notification settings - Fork 288
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
[windows-] update windows-curses version to 2.4 #2119 #2563
Conversation
Tested with Python 3.12. |
@daviewales Does the trade-off feel worth it to you? Improving support of keystrokes, but losing mouseclicks? Saul and I don't use Windows, so this is up to the community that does. |
To add to the tradeoff: #2267 I'd say that launching on 3.12 is fairly essential! |
Ah, good call! |
(seen in the windows_curses repo as Issues # 69 and # 70) This will be fixed soon, as a fix has been submitted as PR # 71 in the Until then, for any affected user, I'd recommend using Python 3.12. -- EDIT to update, 2025-01-11: |
@daviewales, do you remember whether mouse clicks in visidata have ever worked on Windows? (I cannot.) If so, with which versions of visidata, Python, and windows_curses has it worked? |
I can't say for sure, but I believe mouse support worked at least with Python 3.10 on a previous version of Visidata in Windows Terminal. If my memory is correct, then the latest version of Visidata prior to this change had working mouse support. (Some v3 version?) |
I added a possible fix for the mouse not working in Windows 10: #2676 (comment) |
Thanks! |
windows-curses
has released their version 2.4.0. They have updated the version of PDCurses they use, to fix problems inputting some keypresses. This version change should fix #1841, #2062, #2119, and #2267.@daviewales could you see if installing
windows_curses
2.4.0 works well with visidata? In particular, that visidata starts up as usual, without silently exiting immediately, and that the keypresses"
and]
are detected?