[Fedora-i18n-bugs] [Bug 756595] Accessibility Ctrl-space kills content assist in eclipse
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=756595
--- Comment #11 from fujiwara <tfujiwar(a)redhat.com> 2011-11-28 05:42:46 EST ---
Hmm.., interested.
OK, probably I guess you installed multiple XKB keymaps. Now we are working on
combining XKB keymaps and input methods for GNOME and other desktops.
ibus Control+Space would be bound when the multiple ibus engines are enabled.
The ibus behavior is changed between F15 and F16.
In F15, if an input method is enabled, ibus binds Control+Space.
In F16, either multiple XKB keymaps or input methods effect the keybinding.
So if you configure mono keymap and no input method, I think you would not
effect the ibus keybinding.
The purpose is that we have the similar implementation with Mac OS X and
ChromeOS.
I'd think input method settings will be available on gnome-control-center in
f17 or later and probably it would be better KDE also have the similar
implementation.
I thought Control + Space is for the global setting and the input method
keybinding is not ibus only but also other input method frameworks.
I have used Control + Space for input methods for more than ten years and it
might be compatible with MS-Windows.
You still could change default the ibus keybinding with 'ibus-setup' command.
So probably if your initial locale is en_US.UTF-8, probably the ibus keybinding
would not effect you since no default input method engines are enabled.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.