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

CTRL-space bad choice for keyboard shortcut #1748

Closed
fujiwarat opened this Issue May 23, 2015 · 10 comments

Comments

Projects
None yet
2 participants
@fujiwarat
Member

fujiwarat commented May 23, 2015

What version of the product are you using? On what operating system?

OS (Linux distributions, UNIX or ...):Linux Mint 17
Architecture (i386, x86_64):x86_64
IBus version:1.5.5
Input method name and version:
Python version:2.7.6
dbus version:?
dbus-python version:?
gtk version (if bug is about gtk applications):
qt version (if bug is about qt applications):

What steps will reproduce the problem?

1. Install Linux Mint XFCE
2. Start emacs
3. Mark a block using CTRL-space
4. Get confused why CTRL-space does not work

1. Go to duolingo.com
2. Go to a listening lesson
3. Press CTRL-space to listen to the audio at a slower speed
4. Get confused why CTRL-space does not work

What is the expected output? What do you see instead?

I expect CTRL-space to be given to emacs/duolingo.

I see that CTRL-space is intercepted.


Please provide any additional information below.

My suggestion is that you include a couple of other modifiers, so you do not use a
key-combination that is already used for other things or at the very least give a pop-up
first time it is used, so people will not have to spend a lot of time figuring out
what has happened to their system and which part is to blame.

In my case it does not even change the keyboard layout as I only have a single input
method installed.

Original issue reported on code.google.com by ole.tange on 2014-07-25 10:21:02

@fujiwarat

This comment has been minimized.

Show comment
Hide comment
@fujiwarat

fujiwarat May 23, 2015

Member
The workaround (for others finding this bug): Rightclick the keyboard icon. Go to Preferences.
Select another keyboard shortcut for "next input method".

Original issue reported on code.google.com by ole.tange on 2014-07-25 10:23:20

Member

fujiwarat commented May 23, 2015

The workaround (for others finding this bug): Rightclick the keyboard icon. Go to Preferences.
Select another keyboard shortcut for "next input method".

Original issue reported on code.google.com by ole.tange on 2014-07-25 10:23:20

@fujiwarat

This comment has been minimized.

Show comment
Hide comment
@fujiwarat

fujiwarat May 23, 2015

Member
I am not sure about this bug, you can always change default choice for keyboard shortcut
by ibus settings 

Original issue reported on code.google.com by anish.developer on 2014-07-25 10:23:39

Member

fujiwarat commented May 23, 2015

I am not sure about this bug, you can always change default choice for keyboard shortcut
by ibus settings 

Original issue reported on code.google.com by anish.developer on 2014-07-25 10:23:39

@fujiwarat

This comment has been minimized.

Show comment
Hide comment
@fujiwarat

fujiwarat May 23, 2015

Member
True: But only if I know ibus is intercepting the CTRL-space.

And that is the issue: How will I know that ibus does that and that it is not some
other system that is eating my CTRL-space?

I honestly started out by thinking it was Konsole that had the problem, until I discovered
the problem also existed in Chromium. Then I figured those were probably not to blame,
but the problem was elsewhere. Then I did 'xev' to see if X got the keypresses, and
it did. Then I was thinking maybe someone changed the Danish keymap to not include
CTRL-space, and only then did I discover ibus. As soon as I saw the preferences for
ibus it was obvious what happened, but I spent at least 1 hour getting to that stage.

What would you do, if e.g. the 'a' key stopped working after a full upgrade of your
system? Would you immediately know where to fix it? Even if you do not know what packages
the upgrade included?

If ibus had given me a pop up the first time it intercepted CTRL-space, I would have
been aware, that CTRL-space was intercepted by ibus. The pop-up could even give me
a checkbox to simply disable it, if I do not want to use it.

It is pretty clear that I do not have the need for changing input methods. This will
be the case for many other people.

Why not use a shortcut that is not used by most Emacs users, and which predates ibus
by decades? Or: Why not leave the shortcut disabled by default? People who need to
shortcut is more likely to go searching for it.

It seems there are lots of solutions to the problem that will keep everybody happy.

Original issue reported on code.google.com by ole.tange on 2014-07-25 11:52:52

Member

fujiwarat commented May 23, 2015

True: But only if I know ibus is intercepting the CTRL-space.

And that is the issue: How will I know that ibus does that and that it is not some
other system that is eating my CTRL-space?

I honestly started out by thinking it was Konsole that had the problem, until I discovered
the problem also existed in Chromium. Then I figured those were probably not to blame,
but the problem was elsewhere. Then I did 'xev' to see if X got the keypresses, and
it did. Then I was thinking maybe someone changed the Danish keymap to not include
CTRL-space, and only then did I discover ibus. As soon as I saw the preferences for
ibus it was obvious what happened, but I spent at least 1 hour getting to that stage.

What would you do, if e.g. the 'a' key stopped working after a full upgrade of your
system? Would you immediately know where to fix it? Even if you do not know what packages
the upgrade included?

If ibus had given me a pop up the first time it intercepted CTRL-space, I would have
been aware, that CTRL-space was intercepted by ibus. The pop-up could even give me
a checkbox to simply disable it, if I do not want to use it.

It is pretty clear that I do not have the need for changing input methods. This will
be the case for many other people.

Why not use a shortcut that is not used by most Emacs users, and which predates ibus
by decades? Or: Why not leave the shortcut disabled by default? People who need to
shortcut is more likely to go searching for it.

It seems there are lots of solutions to the problem that will keep everybody happy.

Original issue reported on code.google.com by ole.tange on 2014-07-25 11:52:52

@fujiwarat

This comment has been minimized.

Show comment
Hide comment
@fujiwarat

fujiwarat May 23, 2015

Member
The default keybinding has been Super+space but not Ctrl+space since ibus 1.5.3.

Do you suggest ibus keybinding is disabled when only one input method engine is enabled?
If more than two IMEs are enabled, ibus panel icon switches the engine icons by keybinding.
ibus cannot notice if other applications bind the same shortcut keys.

Original issue reported on code.google.com by takao.fujiwara1 on 2014-07-28 03:43:31

  • Labels added: Component-ibus
Member

fujiwarat commented May 23, 2015

The default keybinding has been Super+space but not Ctrl+space since ibus 1.5.3.

Do you suggest ibus keybinding is disabled when only one input method engine is enabled?
If more than two IMEs are enabled, ibus panel icon switches the engine icons by keybinding.
ibus cannot notice if other applications bind the same shortcut keys.

Original issue reported on code.google.com by takao.fujiwara1 on 2014-07-28 03:43:31

  • Labels added: Component-ibus
@fujiwarat

This comment has been minimized.

Show comment
Hide comment
@fujiwarat

fujiwarat May 23, 2015

Member
If the default has been Super+space since 1.5.3, and I run 1.5.5, then someone between
me and you have changed the default (maybe the package manager?).

I understand that ibus cannot detect if other applications bind to the same shortcut,
and that is not what I am concerned about. I see several solutions that would make
me happy:

* Figure out how CTRL+space became the default in the LinuxMint package, and have that
changed back to Super+space (which I have never heard is used by other programs).
* Disable the shortcut if there is only one input method engine
* Give a pop-up dialog box the first time the user activates the shortcut, so that
the user is aware that this shortcut is run by ibus and how to disable it if that is
not what the user wants.
* Disable the shortcut by default - I would imagine the people that have the need for
multiple input engines would have to select the input engines anyway, so they will
see the preferences anyway and see that they can select a shortcut.

Original issue reported on code.google.com by ole.tange on 2014-07-29 08:46:42

Member

fujiwarat commented May 23, 2015

If the default has been Super+space since 1.5.3, and I run 1.5.5, then someone between
me and you have changed the default (maybe the package manager?).

I understand that ibus cannot detect if other applications bind to the same shortcut,
and that is not what I am concerned about. I see several solutions that would make
me happy:

* Figure out how CTRL+space became the default in the LinuxMint package, and have that
changed back to Super+space (which I have never heard is used by other programs).
* Disable the shortcut if there is only one input method engine
* Give a pop-up dialog box the first time the user activates the shortcut, so that
the user is aware that this shortcut is run by ibus and how to disable it if that is
not what the user wants.
* Disable the shortcut by default - I would imagine the people that have the need for
multiple input engines would have to select the input engines anyway, so they will
see the preferences anyway and see that they can select a shortcut.

Original issue reported on code.google.com by ole.tange on 2014-07-29 08:46:42

@fujiwarat

This comment has been minimized.

Show comment
Hide comment
@fujiwarat

fujiwarat May 23, 2015

Member
I am looking into the "Figure out how CTRL+space became the default in the LinuxMint
package, and have that changed back to Super+space (which I have never heard is used
by other programs)." and it seems the package has a patch called ./debian/patches/ibus-xx-ctrl-space.patch
I am pretty sure that is the one causing the problem.

Original issue reported on code.google.com by ole.tange on 2014-07-29 08:51:47

Member

fujiwarat commented May 23, 2015

I am looking into the "Figure out how CTRL+space became the default in the LinuxMint
package, and have that changed back to Super+space (which I have never heard is used
by other programs)." and it seems the package has a patch called ./debian/patches/ibus-xx-ctrl-space.patch
I am pretty sure that is the one causing the problem.

Original issue reported on code.google.com by ole.tange on 2014-07-29 08:51:47

@fujiwarat

This comment has been minimized.

Show comment
Hide comment
@fujiwarat

fujiwarat May 23, 2015

Member
I think it's good for you to try a new user account instead of the current user account
to check the default keybinding.

> ./debian/patches/ibus-xx-ctrl-space.patch I am pretty sure that is the one causing
the problem.

That patch was needed for GNOME 3.10 or older. gnome has been changed the keybinding
from null to Super+space since 3.12 and ibus also done from Ctrl+space to Super+space.

Original issue reported on code.google.com by takao.fujiwara1 on 2014-07-29 10:49:08

Member

fujiwarat commented May 23, 2015

I think it's good for you to try a new user account instead of the current user account
to check the default keybinding.

> ./debian/patches/ibus-xx-ctrl-space.patch I am pretty sure that is the one causing
the problem.

That patch was needed for GNOME 3.10 or older. gnome has been changed the keybinding
from null to Super+space since 3.12 and ibus also done from Ctrl+space to Super+space.

Original issue reported on code.google.com by takao.fujiwara1 on 2014-07-29 10:49:08

@fujiwarat

This comment has been minimized.

Show comment
Hide comment
@fujiwarat

fujiwarat May 23, 2015

Member
> ./debian/patches/ibus-xx-ctrl-space.patch I am pretty sure that is the one causing
the problem.

If that patch is the problem, I will close this bug.

Original issue reported on code.google.com by takao.fujiwara1 on 2014-07-31 10:25:32

Member

fujiwarat commented May 23, 2015

> ./debian/patches/ibus-xx-ctrl-space.patch I am pretty sure that is the one causing
the problem.

If that patch is the problem, I will close this bug.

Original issue reported on code.google.com by takao.fujiwara1 on 2014-07-31 10:25:32

@fujiwarat

This comment has been minimized.

Show comment
Hide comment
@fujiwarat

fujiwarat May 23, 2015

Member
It is. Close the bug.

Original issue reported on code.google.com by ole.tange on 2014-07-31 11:35:07

Member

fujiwarat commented May 23, 2015

It is. Close the bug.

Original issue reported on code.google.com by ole.tange on 2014-07-31 11:35:07

@fujiwarat

This comment has been minimized.

Show comment
Hide comment
@fujiwarat

fujiwarat May 23, 2015

Member
(No text was entered with this change)

Original issue reported on code.google.com by takao.fujiwara1 on 2014-08-01 02:36:50

Member

fujiwarat commented May 23, 2015

(No text was entered with this change)

Original issue reported on code.google.com by takao.fujiwara1 on 2014-08-01 02:36:50

@fujiwarat fujiwarat closed this May 23, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment