Skip to content
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

No input for some cyrillic characters #783

Closed
eugenov opened this issue May 25, 2022 · 9 comments
Closed

No input for some cyrillic characters #783

eugenov opened this issue May 25, 2022 · 9 comments
Assignees
Labels
bug Something isn't working

Comments

@eugenov
Copy link

eugenov commented May 25, 2022

Hello!
I've noticed strange bug - I can't type cyrillic letter "р" inside terminal at last few builds. "Space" is inserting in place of "р". UTF-8 encoding, other terminals deal with it without problem.

@kingToolbox
Copy link
Owner

Hi, eugenov. I tried it and did not encounter such a problem. Could it be a font problem? You can try changing a font to see if it works. In addition, after entering the character, copy it from WindTerm to notepad to see if it is ok.

BTW:
Is there any old WindTerm version that can handle this character correctly?

@kingToolbox
Copy link
Owner

Good news, I have reproduced the bug, and I found that the old 0.9 version is ok. I will try to fix it and let you know if there is any progress. 😄

@kingToolbox kingToolbox self-assigned this May 25, 2022
@kingToolbox kingToolbox added the bug Something isn't working label May 25, 2022
@eugenov
Copy link
Author

eugenov commented May 25, 2022

Is there any old WindTerm version that can handle this character correctly?

I fear i don't remember the version the problem appeared. I've just noticed a bug and I think one of previous versions was ok. :)

@eugenov
Copy link
Author

eugenov commented Jun 21, 2022

Tried 2.4.1 and latest 2.5.0 preview 2 still has this bug.

@kingToolbox
Copy link
Owner

Sorry, I've been working hard on the auto completion feature lately, so many issues have not been fixed in time.

However I have located the source of this problem and am fixing it. This fix will be released in the WindTerm_2.5.0_Prerelease_3 version, please stay tuned, thank you.

BTW:
There are already a large number of issues waiting to be fixed. So I plan to stop the development of new features in the next 2.6.0 version, and try to fix all the bugs before continuing to develop new features. I think this decision is good for everyone. After all, the current features are sufficient for most users. 😄

@eugenov
Copy link
Author

eugenov commented Jun 22, 2022

So I plan to stop the development of new features in the next 2.6.0 version, and try to fix all the bugs before continuing to develop new features.

It's not just good decision, it's great decision, I must say.

@kingToolbox
Copy link
Owner

It's great to have your 💯 support too.

I forgot to mention that opening the WindTerm_installed_path/terminal/terms/xterm-256color.term (The exact file depends on the term of your session) and deleting the line "<Space>" : "\u0020", can circumvents this bug. Of course, it's only a temporary solution. What actually needs to be fixed is much more complicated.

This bug was introduced by the WindTerm_2.2.0_Prerelease_4 version, I don't know why I haven't been able to find this bug.

@kingToolbox
Copy link
Owner

I am happy to inform you that WindTerm_2.5.0_Prerelease_3 has been released and this bug has been finally fixed. Please download and check it, thank you. 😄

@eugenov
Copy link
Author

eugenov commented Jul 10, 2022

Thank you! Closing.

@eugenov eugenov closed this as completed Jul 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants