-
Notifications
You must be signed in to change notification settings - Fork 32
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
Fix for keyboard weirdness #59
Comments
Had some time, so did a little bisecting. commit 6c1f95c4fa9f9f105879c2d99dd72a5bf335c046 on sep 4 2019 is ok. (the 3.9 tag) So windows curses could go back to 3.9, could go to immediately before or after the problem, or could go to HEAD. I could put in a PR for any of those @stephanosio? |
@stephanosio ping? |
@gotyaoi I apologise for the late reply. I will look into updating PDCurses to the latest master (5c62af03e9a05e3a3ae8c8354c1234b772dcf4b0). |
windows-curses 2.4.0a2 has been released with the updated PDCurses. @gotyaoi Please let me know if this fixes the issue. |
@stephanosio 2.4.0a5 produces proper results for apostrophe and close square bracket for me. I cannot test for the italian keyboard situation in #51 though. |
Fixed by v2.4.0. Please comment if this issue persists. |
Relating to #41 and #51, after doing some troubleshooting on my end, this can be solved by updating PDCurses to the 3.9 tag, sha: 6c1f95c4fa9f9f105879c2d99dd72a5bf335c046. As the gitmodules in this repo points to a fork, that for will need to be updated (or we can point to the main wmcbrine repo).
Tested on windows 11 10.0.22631, python 3.12.3.
The text was updated successfully, but these errors were encountered: