Custom compose key configuration does not work

[mlainz]

• VSCode Version: Code 1.16.0 (787b31c, 2017-09-06T16:19:37.192Z)
• OS Version: Linux x64 4.9.0-3-amd64
• Extensions:

Extension	Author (truncated)	Version
latex-workshop	Jam	3.5.2
spellright	ban	1.1.40
jupyter	don	1.1.3
unicode-latex	oij	1.0.2

I have configured some custom keybindings for entering unicode symbols using the compose key. They work on other programs but not on vscode.

For example, the default "compose" + "." + "." does type "…", as expected.
However my custom "compose" + "g" + "a", which should type "α", as it does in other programs, does not work.

A fix or a workarround would be welcomed.

Steps to Reproduce:

1. Create an .XCompose file in the home directory with the line
   <Multi_key> <g> <a> : "α"
2. Restart X.
3. "compose" + "g" + "a" types "α" in most programs.
4. "compose" + "g" + "a" doesn't do anything on vscode.

Reproduces without extensions: Yes

[alexdima]

@mlainz Is this a problem only with the editor or does this reproduce also when wanting to use this key combination in e.g. the find widget input or the search viewlet input boxes ?

Also, do these work in Chromium ?

[mlainz]

The key combination doesn't work anywhere on vscode.

I tried on Chromium and exactly the same happens (standard key combinations work, custom ones don't).

I guess it's a Chromium/electron problem, then.

[mlainz]

Yes, the bug is referenced here.

[alexdima]

This is an upstream issue (possibly within Chromium), and there are no known workarounds that we could implement on our side. This means there is no possible code change for us to do in VS Code sources to improve things.

To keep the number of issues in our inbox at a manageable level, we’re closing issues that have been on the backlog for a long time but haven’t gained traction or that are not actionable. Thank you for your time and understanding.

[alexdima]

Reopened due to comment #43526 (comment) from @timtro

The issue is identical to this one, #34277. The issue was closed because Chrome displayed the same behaviour, indicating an upstream problem. However, I am currently able to use my custom compose combinations from ~/.XCompose in Chrome. I'm wondering if this is something we can fix now.

[mattpalermo]

I am having the same issue in the Atom text editor as well as vscode so perhaps this issue should be addressed upstream in the electron framework?

A thread of my issue: https://askubuntu.com/questions/1038657/how-can-custom-compose-key-combinations-be-defined-for-all-applications

[mattpalermo]

Good news everyone! This bug is fixed in Atom 1.28 which means that upgrading to Electron 2.0 will (should) fix this problem. It looks like Electron 2.0 upgraded to Chrome 61 which must have been enough to fix the problem.

[mlainz]

I think the bug is already fixed in the last update.

[mattpalermo]

Did vscode upgrade to electron 2.0 or did something else happen?

[alexdima]

Yes, the latest stable version of VSCode is on Electron 2.0.7