-
Notifications
You must be signed in to change notification settings - Fork 24
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
Can't enter the hash symbol when using an Italian keyboard #2
Comments
Interesting. Hmmm. Let me get this right:
Definitely, something weird is going on here. Seems like some UTF issue, as a first guess. What happens when you insert an # symbol in the editor via AltGr + à and then stop typing? Does a # show up? |
Kudos you got the Windows Version running, though. I noticed, on some (like: freshly installed) Windows machines, it currently doesn't. |
I did some further testing and noticed the same behavior also with the left square bracket (on the italian keyboard: AltGr + è). So:
I did some screen recording to better illustrates what happens.
Version pre-0.2 runs fine on my system, but I have anaconda python installed with all the dependencies required by sublimeless_zk. Yesterday I was able to run also the pre-release version cloned from GitHub and to successfully compile into an .exe. |
I hope the latest commits fixed this. See #32 |
Hello and thank you for writing this great software,
I'm trying sublimeless_zk with an Italian keyboard where the hash symbol is entered using the AltGr (third level modifier) key + à letter. The key combination works as expected for invoking the "all tags" saved search (#!) or for tag completion command (#?) even if no character is shown on the editor, but I cannot insert a new tag because typing only the # symbol doesn't result in any character showing in the editor pane and it also truncates the first letter of the tag word (e.g. if I want to insert the #zettelkasten tag by writing directly the letters sequence I obtain "ettelkasten").
If I switch to the ENG keyboard layout (on Windows 10) all works as expected, so I suspect there is an issue with the AltGr key combination.
The text was updated successfully, but these errors were encountered: