Skip to content
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

Textern may want to change the default Ctrl+Shift+E keybinding due to a Firefox and GTK3 change #30

Closed
siebenmann opened this issue May 25, 2018 · 1 comment

Comments

@siebenmann
Copy link

@siebenmann siebenmann commented May 25, 2018

The short version is Firefox bug 1451818.

The long version: sufficiently modern versions of GTK+ 3 use Ctrl+Shift+E in text entry widgets to let you enter emoji, as documented here. On systems with a recent enough GTK+ 3, the latest versions of Firefox have changed the generated keycode and key for Ctrl+Shift+E from the usual value of 69 and 'E' to 229 and 'Process', which is apparently the standard behavior in other browsers and also what Firefox's code may call for.

Textern could perhaps sort of cope with this by changing what keycode it's looking for to recognize this too, but that would require changes to shortcuts.js to recognize this and also block using Ctrl+Shift+E to enter emoji. I'd suggest switching to Ctrl+Alt+E, which seems to work reliably for me and which doesn't conflict with anything that I can see.

@jlebon jlebon closed this in 635e3d6 May 26, 2018
@jlebon

This comment has been minimized.

Copy link
Owner

@jlebon jlebon commented May 26, 2018

Thanks for filing this! I've heard others hit it as well, though your detailed report has finally convinced me to do this.

I'd suggest switching to Ctrl+Alt+E, which seems to work reliably for me and which doesn't conflict with anything that I can see.

This is of course subjective, though I went with Ctrl+Shift+D. I find Ctrl+Alt combinations less natural to type than Ctrl+Shift (though that's probably because I'm not an Emacs user :)).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.