GNOME Bugzilla – Bug 725038
.XCompose is ignored
Last modified: 2015-05-13 20:26:01 UTC
Created attachment 270088 [details] Custom compose file I have a .XCompose file in my home directory to create custom compose sequences, but the file is ignored and only the default compose sequences are available. .XCompose should be read and respected.
Completely correct, you'll need to load it yourself, such as with such a script: https://git.gnome.org/browse/gnome-settings-daemon/tree/plugins/common/input-device-example.sh
Just a clarification: ~/.XCompose is loaded and processed by Xlib and/or the application toolkit. There's nothing for the desktop environment to do about it.
(In reply to comment #2) > Just a clarification: ~/.XCompose is loaded and processed by Xlib and/or the > application toolkit. There's nothing for the desktop environment to do about > it. My mistake, .Xmodmap is loaded through a script as in comment 1, .XCompose isn't.
(In reply to Rui Matos from comment #2) > Just a clarification: ~/.XCompose is loaded and processed by Xlib and/or the > application toolkit. There's nothing for the desktop environment to do about > it. Is this an issue for gtk+, then?
(In reply to Seán de Búrca from comment #4) > Is this an issue for gtk+, then? It's an application issue.
(In reply to Rui Matos from comment #5) > (In reply to Seán de Búrca from comment #4) > > Is this an issue for gtk+, then? > > It's an application issue. Obviously this doesn't mean that every application needs to explicitly declare that it supports custom user .XCompose. As it currently stands, none of my GNOME-based applications support ~/.XCompose, so the question becomes where in the stack this belongs, and I don't think "in every application" is the correct answer.