-
Notifications
You must be signed in to change notification settings - Fork 1
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
Idea: keymap/xkbswitch analogue #19
Comments
@Yodzorah , in my experience, this problem arises when user combines mode-based app (such as QB or vim) with multiple keyboard layouts. On the other hand, |
So do I. I'm sorry if due to my lack of English vocabulary I couldn't express this point clearly. The README of vim-xkbswitch seem to explain this a lot more clearly than me:
The P.S. Truth to be told, I already use this as a dirty-hacked patch on my local installation of QB. Looking through that code today, it seem like I was really raged off by this issue and didn't really paid attention to the quality of code. 😊 |
@Mikle-Bond Works very nicely, thanks for sharing. I intended to implement something similar on my own, but found this topic. I've extended the feature to passthrough mode (in addition to insert mode). In what sense do you consider it dirty-hacked? The only problem with xkb-switch is that it does not work in some (all?) Wayland-based window managers such as Sway. That's the major point that keeps me from switching to Sway entirely, as I can't use xkb-switch plugin in vim there. |
When using more than one keyboard layout within QB, writing text can be a hassle. Vim also has such problems, as well as several solutions, such as embedded keymap/iminsert settings, or external plugin vim-xkbswitch (you can read it's readme to get a better idea of what I'm talking about).
Basically, I wish to port vim-xkbswitch to qutebrowser-extensions. Or, at least, have some substitution for it.
It seems like minimal requirement is API should provide means to connect to
mode_manager
's signalsentered
andleft
for this to work. Probably also some other changes to support helping in //?-search.The text was updated successfully, but these errors were encountered: