Custom ComposeKey sequences in 18.04
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
1
down vote
favorite
How do I add user-defined compose key rules in Ubuntu 18.04? I turned my Compose key on using Gnome Tweaks (it's on CapsLock), created a .XCompose
starting with these lines:
include "%L" # import the default Compose file for your locale
# IPA
<Multi_key> <a> <h> : "ÃÂ"
<Multi_key> <A> <h> : "â±Â"
# Some more lines
<Multi_key> <ampersand> <underscore> <m> : "ü"
# Math
<Multi_key> <minus> <0> : "âÂÂ"
<Multi_key> <asterisk> <1> : "âÂÂ
"
<Multi_key> <x> <x> : "ÃÂ"
# ...
I followed this advice, installed uim
and set it as GTK_
and QT_IM_MODULE
but every sequence starting with the <minus> <0>
line gets ignored. When I tried xim
, it did a bit better but it made gedit
glitch:
.
When I tried GTK_IM_MODULE=gtk-im-context-simple
, most of the sequences started working, but some of them just don't.
<Multi_key> <minus> <0> : "âÂÂ" # doesn't work
<Multi_key> <asterisk> <1> : "âÂÂ
" # doesn't work
<Multi_key> <e> <m> <o> <colon> <space> : "ð¶" # works
<Multi_key> <e> <m> <o> <colon> <Up> : "ðÂÂÂ" # works
<Multi_key> <e> <m> <o> <x> <asterisk> <space> : "ðÂÂÂ" # doesn't work
<Multi_key> <e> <m> <o> <c> <a> <l> <l> : "ð¤Â" # doesn't work
<Multi_key> <e> <m> <o> <o> <k> : "ðÂÂÂ" # works
<Multi_key> <w> <t> <f> : "à ² _à ² " # doesn't work
<Multi_key> <w> <h> <y> : "áÂÂ(à ² çÂÂà ² áÂÂ)" # doesn't work
<Multi_key> <0> <space> : "âÂÂ" # zero-width space doesn't work
.
What should I do to make my Compose key work properly?
keyboard 18.04 compose-key
add a comment |Â
up vote
1
down vote
favorite
How do I add user-defined compose key rules in Ubuntu 18.04? I turned my Compose key on using Gnome Tweaks (it's on CapsLock), created a .XCompose
starting with these lines:
include "%L" # import the default Compose file for your locale
# IPA
<Multi_key> <a> <h> : "ÃÂ"
<Multi_key> <A> <h> : "â±Â"
# Some more lines
<Multi_key> <ampersand> <underscore> <m> : "ü"
# Math
<Multi_key> <minus> <0> : "âÂÂ"
<Multi_key> <asterisk> <1> : "âÂÂ
"
<Multi_key> <x> <x> : "ÃÂ"
# ...
I followed this advice, installed uim
and set it as GTK_
and QT_IM_MODULE
but every sequence starting with the <minus> <0>
line gets ignored. When I tried xim
, it did a bit better but it made gedit
glitch:
.
When I tried GTK_IM_MODULE=gtk-im-context-simple
, most of the sequences started working, but some of them just don't.
<Multi_key> <minus> <0> : "âÂÂ" # doesn't work
<Multi_key> <asterisk> <1> : "âÂÂ
" # doesn't work
<Multi_key> <e> <m> <o> <colon> <space> : "ð¶" # works
<Multi_key> <e> <m> <o> <colon> <Up> : "ðÂÂÂ" # works
<Multi_key> <e> <m> <o> <x> <asterisk> <space> : "ðÂÂÂ" # doesn't work
<Multi_key> <e> <m> <o> <c> <a> <l> <l> : "ð¤Â" # doesn't work
<Multi_key> <e> <m> <o> <o> <k> : "ðÂÂÂ" # works
<Multi_key> <w> <t> <f> : "à ² _à ² " # doesn't work
<Multi_key> <w> <h> <y> : "áÂÂ(à ² çÂÂà ² áÂÂ)" # doesn't work
<Multi_key> <0> <space> : "âÂÂ" # zero-width space doesn't work
.
What should I do to make my Compose key work properly?
keyboard 18.04 compose-key
1
Can you add info about what you did to turn on the compose key? That is, what is the location of the settings you changed and which settings you selected? (Wondering if you used the GUI or edited/etc/default/keyboard
or something else?)
â xiota
May 18 at 12:03
I used Gnome Tweaks, see the updated question.
â m93a
May 20 at 14:53
I put keyboard settings in/etc/default/keyboard
. Don't know if it makes a difference. You can also try putting theinclude
at the end of the config to see if it makes a difference. Otherwise, it looks like multi-character output and sequences longer than 5 won't work.
â xiota
May 20 at 16:11
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
How do I add user-defined compose key rules in Ubuntu 18.04? I turned my Compose key on using Gnome Tweaks (it's on CapsLock), created a .XCompose
starting with these lines:
include "%L" # import the default Compose file for your locale
# IPA
<Multi_key> <a> <h> : "ÃÂ"
<Multi_key> <A> <h> : "â±Â"
# Some more lines
<Multi_key> <ampersand> <underscore> <m> : "ü"
# Math
<Multi_key> <minus> <0> : "âÂÂ"
<Multi_key> <asterisk> <1> : "âÂÂ
"
<Multi_key> <x> <x> : "ÃÂ"
# ...
I followed this advice, installed uim
and set it as GTK_
and QT_IM_MODULE
but every sequence starting with the <minus> <0>
line gets ignored. When I tried xim
, it did a bit better but it made gedit
glitch:
.
When I tried GTK_IM_MODULE=gtk-im-context-simple
, most of the sequences started working, but some of them just don't.
<Multi_key> <minus> <0> : "âÂÂ" # doesn't work
<Multi_key> <asterisk> <1> : "âÂÂ
" # doesn't work
<Multi_key> <e> <m> <o> <colon> <space> : "ð¶" # works
<Multi_key> <e> <m> <o> <colon> <Up> : "ðÂÂÂ" # works
<Multi_key> <e> <m> <o> <x> <asterisk> <space> : "ðÂÂÂ" # doesn't work
<Multi_key> <e> <m> <o> <c> <a> <l> <l> : "ð¤Â" # doesn't work
<Multi_key> <e> <m> <o> <o> <k> : "ðÂÂÂ" # works
<Multi_key> <w> <t> <f> : "à ² _à ² " # doesn't work
<Multi_key> <w> <h> <y> : "áÂÂ(à ² çÂÂà ² áÂÂ)" # doesn't work
<Multi_key> <0> <space> : "âÂÂ" # zero-width space doesn't work
.
What should I do to make my Compose key work properly?
keyboard 18.04 compose-key
How do I add user-defined compose key rules in Ubuntu 18.04? I turned my Compose key on using Gnome Tweaks (it's on CapsLock), created a .XCompose
starting with these lines:
include "%L" # import the default Compose file for your locale
# IPA
<Multi_key> <a> <h> : "ÃÂ"
<Multi_key> <A> <h> : "â±Â"
# Some more lines
<Multi_key> <ampersand> <underscore> <m> : "ü"
# Math
<Multi_key> <minus> <0> : "âÂÂ"
<Multi_key> <asterisk> <1> : "âÂÂ
"
<Multi_key> <x> <x> : "ÃÂ"
# ...
I followed this advice, installed uim
and set it as GTK_
and QT_IM_MODULE
but every sequence starting with the <minus> <0>
line gets ignored. When I tried xim
, it did a bit better but it made gedit
glitch:
.
When I tried GTK_IM_MODULE=gtk-im-context-simple
, most of the sequences started working, but some of them just don't.
<Multi_key> <minus> <0> : "âÂÂ" # doesn't work
<Multi_key> <asterisk> <1> : "âÂÂ
" # doesn't work
<Multi_key> <e> <m> <o> <colon> <space> : "ð¶" # works
<Multi_key> <e> <m> <o> <colon> <Up> : "ðÂÂÂ" # works
<Multi_key> <e> <m> <o> <x> <asterisk> <space> : "ðÂÂÂ" # doesn't work
<Multi_key> <e> <m> <o> <c> <a> <l> <l> : "ð¤Â" # doesn't work
<Multi_key> <e> <m> <o> <o> <k> : "ðÂÂÂ" # works
<Multi_key> <w> <t> <f> : "à ² _à ² " # doesn't work
<Multi_key> <w> <h> <y> : "áÂÂ(à ² çÂÂà ² áÂÂ)" # doesn't work
<Multi_key> <0> <space> : "âÂÂ" # zero-width space doesn't work
.
What should I do to make my Compose key work properly?
keyboard 18.04 compose-key
edited May 20 at 14:52
asked May 18 at 0:18
m93a
14112
14112
1
Can you add info about what you did to turn on the compose key? That is, what is the location of the settings you changed and which settings you selected? (Wondering if you used the GUI or edited/etc/default/keyboard
or something else?)
â xiota
May 18 at 12:03
I used Gnome Tweaks, see the updated question.
â m93a
May 20 at 14:53
I put keyboard settings in/etc/default/keyboard
. Don't know if it makes a difference. You can also try putting theinclude
at the end of the config to see if it makes a difference. Otherwise, it looks like multi-character output and sequences longer than 5 won't work.
â xiota
May 20 at 16:11
add a comment |Â
1
Can you add info about what you did to turn on the compose key? That is, what is the location of the settings you changed and which settings you selected? (Wondering if you used the GUI or edited/etc/default/keyboard
or something else?)
â xiota
May 18 at 12:03
I used Gnome Tweaks, see the updated question.
â m93a
May 20 at 14:53
I put keyboard settings in/etc/default/keyboard
. Don't know if it makes a difference. You can also try putting theinclude
at the end of the config to see if it makes a difference. Otherwise, it looks like multi-character output and sequences longer than 5 won't work.
â xiota
May 20 at 16:11
1
1
Can you add info about what you did to turn on the compose key? That is, what is the location of the settings you changed and which settings you selected? (Wondering if you used the GUI or edited
/etc/default/keyboard
or something else?)â xiota
May 18 at 12:03
Can you add info about what you did to turn on the compose key? That is, what is the location of the settings you changed and which settings you selected? (Wondering if you used the GUI or edited
/etc/default/keyboard
or something else?)â xiota
May 18 at 12:03
I used Gnome Tweaks, see the updated question.
â m93a
May 20 at 14:53
I used Gnome Tweaks, see the updated question.
â m93a
May 20 at 14:53
I put keyboard settings in
/etc/default/keyboard
. Don't know if it makes a difference. You can also try putting the include
at the end of the config to see if it makes a difference. Otherwise, it looks like multi-character output and sequences longer than 5 won't work.â xiota
May 20 at 16:11
I put keyboard settings in
/etc/default/keyboard
. Don't know if it makes a difference. You can also try putting the include
at the end of the config to see if it makes a difference. Otherwise, it looks like multi-character output and sequences longer than 5 won't work.â xiota
May 20 at 16:11
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
The link you point to is basically correct, with a few caveats:
Compose inserts the character corresponding to the first (shortest) match. Suppose
.XCompose
contains the following entries:<Multi_key> <space> : " " nobreakspace # NO-BREAK SPACE
<Multi_key> <space> <space> : "âÂÂ" U2002 # EN SPACE
<Multi_key> <space> <space> <space> : "âÂÂ" U2003 # EM SPACEAttempts to use EN-SPACE or EM-SPACE will never work.
To get Compose to work with GTK, add the following line to
.profile
:export GTK_IM_MODULE=gtk-im-context-simple
My problem isn't that my rules are overwritten with shorter ones -- they simply don't work at all, they just do nothing. And it seems to me that which rules work and which don't changes during the session. For example just a while ago I could useminus minus period
to write a dash, but now it just doesn't work. (I would add a thinking emoji but -- you know, my compose key doesn't work...)
â m93a
May 18 at 9:23
Have you tried addingexport GTK_IM_MODULE=gtk-im-context-simple
to~/.profile
?
â xiota
May 18 at 12:01
I tried it but some sequences (especially the longer ones) just don't work.
â m93a
May 20 at 14:10
Oh and sometimes my keyboard just stops working altogether since I setgtk-im-context-simple
. Only reboot fixes it... ðÂÂÂ
â m93a
May 20 at 17:40
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
The link you point to is basically correct, with a few caveats:
Compose inserts the character corresponding to the first (shortest) match. Suppose
.XCompose
contains the following entries:<Multi_key> <space> : " " nobreakspace # NO-BREAK SPACE
<Multi_key> <space> <space> : "âÂÂ" U2002 # EN SPACE
<Multi_key> <space> <space> <space> : "âÂÂ" U2003 # EM SPACEAttempts to use EN-SPACE or EM-SPACE will never work.
To get Compose to work with GTK, add the following line to
.profile
:export GTK_IM_MODULE=gtk-im-context-simple
My problem isn't that my rules are overwritten with shorter ones -- they simply don't work at all, they just do nothing. And it seems to me that which rules work and which don't changes during the session. For example just a while ago I could useminus minus period
to write a dash, but now it just doesn't work. (I would add a thinking emoji but -- you know, my compose key doesn't work...)
â m93a
May 18 at 9:23
Have you tried addingexport GTK_IM_MODULE=gtk-im-context-simple
to~/.profile
?
â xiota
May 18 at 12:01
I tried it but some sequences (especially the longer ones) just don't work.
â m93a
May 20 at 14:10
Oh and sometimes my keyboard just stops working altogether since I setgtk-im-context-simple
. Only reboot fixes it... ðÂÂÂ
â m93a
May 20 at 17:40
add a comment |Â
up vote
0
down vote
The link you point to is basically correct, with a few caveats:
Compose inserts the character corresponding to the first (shortest) match. Suppose
.XCompose
contains the following entries:<Multi_key> <space> : " " nobreakspace # NO-BREAK SPACE
<Multi_key> <space> <space> : "âÂÂ" U2002 # EN SPACE
<Multi_key> <space> <space> <space> : "âÂÂ" U2003 # EM SPACEAttempts to use EN-SPACE or EM-SPACE will never work.
To get Compose to work with GTK, add the following line to
.profile
:export GTK_IM_MODULE=gtk-im-context-simple
My problem isn't that my rules are overwritten with shorter ones -- they simply don't work at all, they just do nothing. And it seems to me that which rules work and which don't changes during the session. For example just a while ago I could useminus minus period
to write a dash, but now it just doesn't work. (I would add a thinking emoji but -- you know, my compose key doesn't work...)
â m93a
May 18 at 9:23
Have you tried addingexport GTK_IM_MODULE=gtk-im-context-simple
to~/.profile
?
â xiota
May 18 at 12:01
I tried it but some sequences (especially the longer ones) just don't work.
â m93a
May 20 at 14:10
Oh and sometimes my keyboard just stops working altogether since I setgtk-im-context-simple
. Only reboot fixes it... ðÂÂÂ
â m93a
May 20 at 17:40
add a comment |Â
up vote
0
down vote
up vote
0
down vote
The link you point to is basically correct, with a few caveats:
Compose inserts the character corresponding to the first (shortest) match. Suppose
.XCompose
contains the following entries:<Multi_key> <space> : " " nobreakspace # NO-BREAK SPACE
<Multi_key> <space> <space> : "âÂÂ" U2002 # EN SPACE
<Multi_key> <space> <space> <space> : "âÂÂ" U2003 # EM SPACEAttempts to use EN-SPACE or EM-SPACE will never work.
To get Compose to work with GTK, add the following line to
.profile
:export GTK_IM_MODULE=gtk-im-context-simple
The link you point to is basically correct, with a few caveats:
Compose inserts the character corresponding to the first (shortest) match. Suppose
.XCompose
contains the following entries:<Multi_key> <space> : " " nobreakspace # NO-BREAK SPACE
<Multi_key> <space> <space> : "âÂÂ" U2002 # EN SPACE
<Multi_key> <space> <space> <space> : "âÂÂ" U2003 # EM SPACEAttempts to use EN-SPACE or EM-SPACE will never work.
To get Compose to work with GTK, add the following line to
.profile
:export GTK_IM_MODULE=gtk-im-context-simple
edited May 18 at 2:58
answered May 18 at 2:37
xiota
1,0461422
1,0461422
My problem isn't that my rules are overwritten with shorter ones -- they simply don't work at all, they just do nothing. And it seems to me that which rules work and which don't changes during the session. For example just a while ago I could useminus minus period
to write a dash, but now it just doesn't work. (I would add a thinking emoji but -- you know, my compose key doesn't work...)
â m93a
May 18 at 9:23
Have you tried addingexport GTK_IM_MODULE=gtk-im-context-simple
to~/.profile
?
â xiota
May 18 at 12:01
I tried it but some sequences (especially the longer ones) just don't work.
â m93a
May 20 at 14:10
Oh and sometimes my keyboard just stops working altogether since I setgtk-im-context-simple
. Only reboot fixes it... ðÂÂÂ
â m93a
May 20 at 17:40
add a comment |Â
My problem isn't that my rules are overwritten with shorter ones -- they simply don't work at all, they just do nothing. And it seems to me that which rules work and which don't changes during the session. For example just a while ago I could useminus minus period
to write a dash, but now it just doesn't work. (I would add a thinking emoji but -- you know, my compose key doesn't work...)
â m93a
May 18 at 9:23
Have you tried addingexport GTK_IM_MODULE=gtk-im-context-simple
to~/.profile
?
â xiota
May 18 at 12:01
I tried it but some sequences (especially the longer ones) just don't work.
â m93a
May 20 at 14:10
Oh and sometimes my keyboard just stops working altogether since I setgtk-im-context-simple
. Only reboot fixes it... ðÂÂÂ
â m93a
May 20 at 17:40
My problem isn't that my rules are overwritten with shorter ones -- they simply don't work at all, they just do nothing. And it seems to me that which rules work and which don't changes during the session. For example just a while ago I could use
minus minus period
to write a dash, but now it just doesn't work. (I would add a thinking emoji but -- you know, my compose key doesn't work...)â m93a
May 18 at 9:23
My problem isn't that my rules are overwritten with shorter ones -- they simply don't work at all, they just do nothing. And it seems to me that which rules work and which don't changes during the session. For example just a while ago I could use
minus minus period
to write a dash, but now it just doesn't work. (I would add a thinking emoji but -- you know, my compose key doesn't work...)â m93a
May 18 at 9:23
Have you tried adding
export GTK_IM_MODULE=gtk-im-context-simple
to ~/.profile
?â xiota
May 18 at 12:01
Have you tried adding
export GTK_IM_MODULE=gtk-im-context-simple
to ~/.profile
?â xiota
May 18 at 12:01
I tried it but some sequences (especially the longer ones) just don't work.
â m93a
May 20 at 14:10
I tried it but some sequences (especially the longer ones) just don't work.
â m93a
May 20 at 14:10
Oh and sometimes my keyboard just stops working altogether since I set
gtk-im-context-simple
. Only reboot fixes it... ðÂÂÂâ m93a
May 20 at 17:40
Oh and sometimes my keyboard just stops working altogether since I set
gtk-im-context-simple
. Only reboot fixes it... ðÂÂÂâ m93a
May 20 at 17:40
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1037597%2fcustom-composekey-sequences-in-18-04%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
Can you add info about what you did to turn on the compose key? That is, what is the location of the settings you changed and which settings you selected? (Wondering if you used the GUI or edited
/etc/default/keyboard
or something else?)â xiota
May 18 at 12:03
I used Gnome Tweaks, see the updated question.
â m93a
May 20 at 14:53
I put keyboard settings in
/etc/default/keyboard
. Don't know if it makes a difference. You can also try putting theinclude
at the end of the config to see if it makes a difference. Otherwise, it looks like multi-character output and sequences longer than 5 won't work.â xiota
May 20 at 16:11