1.5.3: Release 1.5.3 Takao Fujiwara fujiwarat released this on Jul 26, 2013.... This version changes the default hotkey from Control + space to Super + space. You can customize the hotkey with ibus-setup.
The code changes (to more than just the xml file, Jorge) are here:
Aha - it is patched back to ctrl-space in patches/ibus-xx-ctrl-space.patch as a "transitional solution in trusty" because of this bug in gnome-settings-daemon I guess:
Trusty LTS is not a release to be doing transitional solutions in....
This bug among other things has caused me to lose data in emacs, because set-mark-command doesn't work from ctrl-space like it has for what, decades? And my fingers expect it to continue to work that way. I set the mark and delete the region as a muscle macro. Very dangerous.
This needs to work right for all the desktops, rather than breaking it for everything except one desktop.
Re: #20 - it looks like it is upstream that changed to super+space, not Debian: /github. com/ibus/ ibus/releases
https:/
1.5.3: Release 1.5.3 Takao Fujiwara fujiwarat released this on Jul 26, 2013.... This version changes the default hotkey from Control + space to Super + space. You can customize the hotkey with ibus-setup.
The code changes (to more than just the xml file, Jorge) are here:
Defalut triggers key is changed to <Super>space. · f3d80dc · ibus/ibus /github. com/ibus/ ibus/commit/ f3d80dc026853c1 024cdf6bda31b14 96939cb095
https:/
So Ubuntu is overriding upstream! Why?
Aha - it is patched back to ctrl-space in patches/ ibus-xx- ctrl-space. patch as a "transitional solution in trusty" because of this bug in gnome-settings- daemon I guess:
Bug #1249208 “Avoid conflicting <Super>Space shortcut with g-s-d...” : Bugs : “ibus” package : Ubuntu /bugs.launchpad .net/ubuntu/ +source/ ibus/+bug/ 1249208
https:/
Trusty LTS is not a release to be doing transitional solutions in....
This bug among other things has caused me to lose data in emacs, because set-mark-command doesn't work from ctrl-space like it has for what, decades? And my fingers expect it to continue to work that way. I set the mark and delete the region as a muscle macro. Very dangerous.
This needs to work right for all the desktops, rather than breaking it for everything except one desktop.