Atom ignores my personal compose key bindings in .XCompose


#1

Using Ubuntu 18.04, I can define personal compose key bindings in a file in .XCompose Compose(5). This works great in every application other than Atom. In atom only the default combinations work. What could Atom be doing differently from everything else?

I want to use this so that I can easily type the ◊ character while I explore Pollen.


#2

Good news everyone! This problem is fixed in v1.28.0! The upgrade to Chrome 61 in Electron 2.0 must have fixed this problem. I can’t figure out when exactly it was fixed but thank you forever unknown Chrome engineer!