-
Notifications
You must be signed in to change notification settings - Fork 28
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
Unable to input anything until switching windows #29
Comments
Yes, I can confirm I have been bugged by this for a long time. Thank you raising this. |
Thank you very much for reporting the issue. I have tried the command I am curious that which input mode do you use? |
I did not expect this kind of response. Thank you for taking interest. The screencast was... disheartening. ;) This is what I have in
I do not see a
This is a fresh install, and I have only been using scim for about a day. I have already noticed a correlation between the non-responsive state and ctrl+key combinations... Then again, this could be my imagination. I use a lot of ctrl+key stuff on the terminal. |
I have since discovered that maximizing and unmaximizing the problem window is an even more effective method. |
scim provides two gtk immodules, By the way I have tried both |
I am opening this issue because scim appeals to me very much. While other input method platforms grow larger and slower, scim remains simple and lean.
Is it being maintained? I see some commits. I know somebody is working.
Anyway, there is one major issue that prevents me from being able to use scim. It has been described elsewhere as a loss of focus, but in my experience window focus is never lost. Rather, scim suddenly stops sending input to the focused window. This has a tendency to happen when using Ctrl keyboard shortcuts, e.g.
Ctrl + u
in a terminal window running a shell.Switching focus to another window, pressing a key or two, and switching back to the original window usually solves the issue. When it does not, switching again and pressing even more keys almost always does. Wash, rinse, repeat.
Other than this, scim is pretty much perfect (to me, at least). You can configure it with text files for crying out loud--a convenience that scim's alternatives seem to have completely forgotten.
Thank you and take care.
P.S. I have also experienced this issue on a Debian system back in 2014. And I can almost always reproduce the issue after running the following command:
The text was updated successfully, but these errors were encountered: