Custom ComposeKey sequences in 18.04How can I add a custom compose key sequence?How can I add a custom compose key sequence?Custom compose key sequences without xim (e.g. in Sublime Text 2)How to remap XF86Sleep key to space---xmodmap, xkbcomp & udev failCompose sequences with multicharacter result don't workHow to set a Compose Key in Ubuntu 18.04Keyboard not responding on Ubuntu 18.04 LTSCompose key doesn't work in 18.04Enabling Compose key with Tweaks doesn't work on Ubuntu 18.04How do I toggle input modes with Mozc?Compose key broken in Ubuntu 18.04 in X, but not in the console

Denied boarding due to overcrowding, Sparpreis ticket. What are my rights?

Does a dangling wire really electrocute me if I'm standing in water?

What happens when a metallic dragon and a chromatic dragon mate?

"My colleague's body is amazing"

Does the average primeness of natural numbers tend to zero?

Prime joint compound before latex paint?

Manga about a female worker who got dragged into another world together with this high school girl and she was just told she's not needed anymore

Does bootstrapped regression allow for inference?

Is every set a filtered colimit of finite sets?

Is there a familial term for apples and pears?

How would photo IDs work for shapeshifters?

Is there any use for defining additional entity types in a SOQL FROM clause?

Are objects structures and/or vice versa?

Is it wise to hold on to stock that has plummeted and then stabilized?

Is it wise to focus on putting odd beats on left when playing double bass drums?

Symmetry in quantum mechanics

When blogging recipes, how can I support both readers who want the narrative/journey and ones who want the printer-friendly recipe?

Does it makes sense to buy a new cycle to learn riding?

Copycat chess is back

Why was the "bread communication" in the arena of Catching Fire left out in the movie?

extract characters between two commas?

How did the USSR manage to innovate in an environment characterized by government censorship and high bureaucracy?

How to make payment on the internet without leaving a money trail?

What is the offset in a seaplane's hull?



Custom ComposeKey sequences in 18.04


How can I add a custom compose key sequence?How can I add a custom compose key sequence?Custom compose key sequences without xim (e.g. in Sublime Text 2)How to remap XF86Sleep key to space---xmodmap, xkbcomp & udev failCompose sequences with multicharacter result don't workHow to set a Compose Key in Ubuntu 18.04Keyboard not responding on Ubuntu 18.04 LTSCompose key doesn't work in 18.04Enabling Compose key with Tweaks doesn't work on Ubuntu 18.04How do I toggle input modes with Mozc?Compose key broken in Ubuntu 18.04 in X, but not in the console






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








2















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:



xim 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?










share|improve this question



















  • 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 '18 at 12:03











  • I used Gnome Tweaks, see the updated question.

    – m93a
    May 20 '18 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 '18 at 16:11

















2















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:



xim 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?










share|improve this question



















  • 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 '18 at 12:03











  • I used Gnome Tweaks, see the updated question.

    – m93a
    May 20 '18 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 '18 at 16:11













2












2








2








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:



xim 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?










share|improve this question
















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:



xim 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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 20 '18 at 14:52







m93a

















asked May 18 '18 at 0:18









m93am93a

196113




196113







  • 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 '18 at 12:03











  • I used Gnome Tweaks, see the updated question.

    – m93a
    May 20 '18 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 '18 at 16:11












  • 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 '18 at 12:03











  • I used Gnome Tweaks, see the updated question.

    – m93a
    May 20 '18 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 '18 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 '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 '18 at 12:03













I used Gnome Tweaks, see the updated question.

– m93a
May 20 '18 at 14:53





I used Gnome Tweaks, see the updated question.

– m93a
May 20 '18 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 '18 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 '18 at 16:11










1 Answer
1






active

oldest

votes


















1














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 SPACE


    Attempts 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



Regarding gtk-im-context-simple, Jens Mühlenhoff notes (1, 2):




In the API documentation:



GtkIMContextSimple reads additional compose sequences from the first of the following files that is found:



  • ~/.config/gtk-3.0/Compose


  • ~/.XCompose, /usr/share/X11/locale/$locale/Compose (for locales that have a nontrivial Compose file)


So the gtk-im-context-simple method has a built-in table and it loads compose sequences from several additional locations. That means it could possible load shorter sequences that you don't expect.







share|improve this answer

























  • 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 '18 at 9:23












  • Have you tried adding export GTK_IM_MODULE=gtk-im-context-simple to ~/.profile?

    – xiota
    May 18 '18 at 12:01











  • I tried it but some sequences (especially the longer ones) just don't work.

    – m93a
    May 20 '18 at 14:10






  • 1





    In the API documentation you can find a paragraph "GtkIMContextSimple reads additional compose sequences from the first of the following files that is found: ~/.config/gtk-3.0/Compose, ~/.XCompose, /usr/share/X11/locale/$locale/Compose (for locales that have a nontrivial Compose file)." developer.gnome.org/gtk3/stable/GtkIMContextSimple.html

    – Jens Mühlenhoff
    5 hours ago






  • 1





    So the gtk-im-context-simple method has a built-in table and it loads compose sequences from several additional locations. That means it could possible load shorter sequences that you don't expect. The name "simple" is a bit misleading here really. It would be nice if there was a tool that looks for sequence collissions based on the same algorithm that gtk-im-context-simple uses to load it's tables.

    – Jens Mühlenhoff
    5 hours ago











Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















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















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














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 SPACE


    Attempts 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



Regarding gtk-im-context-simple, Jens Mühlenhoff notes (1, 2):




In the API documentation:



GtkIMContextSimple reads additional compose sequences from the first of the following files that is found:



  • ~/.config/gtk-3.0/Compose


  • ~/.XCompose, /usr/share/X11/locale/$locale/Compose (for locales that have a nontrivial Compose file)


So the gtk-im-context-simple method has a built-in table and it loads compose sequences from several additional locations. That means it could possible load shorter sequences that you don't expect.







share|improve this answer

























  • 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 '18 at 9:23












  • Have you tried adding export GTK_IM_MODULE=gtk-im-context-simple to ~/.profile?

    – xiota
    May 18 '18 at 12:01











  • I tried it but some sequences (especially the longer ones) just don't work.

    – m93a
    May 20 '18 at 14:10






  • 1





    In the API documentation you can find a paragraph "GtkIMContextSimple reads additional compose sequences from the first of the following files that is found: ~/.config/gtk-3.0/Compose, ~/.XCompose, /usr/share/X11/locale/$locale/Compose (for locales that have a nontrivial Compose file)." developer.gnome.org/gtk3/stable/GtkIMContextSimple.html

    – Jens Mühlenhoff
    5 hours ago






  • 1





    So the gtk-im-context-simple method has a built-in table and it loads compose sequences from several additional locations. That means it could possible load shorter sequences that you don't expect. The name "simple" is a bit misleading here really. It would be nice if there was a tool that looks for sequence collissions based on the same algorithm that gtk-im-context-simple uses to load it's tables.

    – Jens Mühlenhoff
    5 hours ago















1














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 SPACE


    Attempts 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



Regarding gtk-im-context-simple, Jens Mühlenhoff notes (1, 2):




In the API documentation:



GtkIMContextSimple reads additional compose sequences from the first of the following files that is found:



  • ~/.config/gtk-3.0/Compose


  • ~/.XCompose, /usr/share/X11/locale/$locale/Compose (for locales that have a nontrivial Compose file)


So the gtk-im-context-simple method has a built-in table and it loads compose sequences from several additional locations. That means it could possible load shorter sequences that you don't expect.







share|improve this answer

























  • 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 '18 at 9:23












  • Have you tried adding export GTK_IM_MODULE=gtk-im-context-simple to ~/.profile?

    – xiota
    May 18 '18 at 12:01











  • I tried it but some sequences (especially the longer ones) just don't work.

    – m93a
    May 20 '18 at 14:10






  • 1





    In the API documentation you can find a paragraph "GtkIMContextSimple reads additional compose sequences from the first of the following files that is found: ~/.config/gtk-3.0/Compose, ~/.XCompose, /usr/share/X11/locale/$locale/Compose (for locales that have a nontrivial Compose file)." developer.gnome.org/gtk3/stable/GtkIMContextSimple.html

    – Jens Mühlenhoff
    5 hours ago






  • 1





    So the gtk-im-context-simple method has a built-in table and it loads compose sequences from several additional locations. That means it could possible load shorter sequences that you don't expect. The name "simple" is a bit misleading here really. It would be nice if there was a tool that looks for sequence collissions based on the same algorithm that gtk-im-context-simple uses to load it's tables.

    – Jens Mühlenhoff
    5 hours ago













1












1








1







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 SPACE


    Attempts 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



Regarding gtk-im-context-simple, Jens Mühlenhoff notes (1, 2):




In the API documentation:



GtkIMContextSimple reads additional compose sequences from the first of the following files that is found:



  • ~/.config/gtk-3.0/Compose


  • ~/.XCompose, /usr/share/X11/locale/$locale/Compose (for locales that have a nontrivial Compose file)


So the gtk-im-context-simple method has a built-in table and it loads compose sequences from several additional locations. That means it could possible load shorter sequences that you don't expect.







share|improve this answer















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 SPACE


    Attempts 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



Regarding gtk-im-context-simple, Jens Mühlenhoff notes (1, 2):




In the API documentation:



GtkIMContextSimple reads additional compose sequences from the first of the following files that is found:



  • ~/.config/gtk-3.0/Compose


  • ~/.XCompose, /usr/share/X11/locale/$locale/Compose (for locales that have a nontrivial Compose file)


So the gtk-im-context-simple method has a built-in table and it loads compose sequences from several additional locations. That means it could possible load shorter sequences that you don't expect.








share|improve this answer














share|improve this answer



share|improve this answer








edited 4 hours ago

























answered May 18 '18 at 2:37









xiotaxiota

1,1821523




1,1821523












  • 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 '18 at 9:23












  • Have you tried adding export GTK_IM_MODULE=gtk-im-context-simple to ~/.profile?

    – xiota
    May 18 '18 at 12:01











  • I tried it but some sequences (especially the longer ones) just don't work.

    – m93a
    May 20 '18 at 14:10






  • 1





    In the API documentation you can find a paragraph "GtkIMContextSimple reads additional compose sequences from the first of the following files that is found: ~/.config/gtk-3.0/Compose, ~/.XCompose, /usr/share/X11/locale/$locale/Compose (for locales that have a nontrivial Compose file)." developer.gnome.org/gtk3/stable/GtkIMContextSimple.html

    – Jens Mühlenhoff
    5 hours ago






  • 1





    So the gtk-im-context-simple method has a built-in table and it loads compose sequences from several additional locations. That means it could possible load shorter sequences that you don't expect. The name "simple" is a bit misleading here really. It would be nice if there was a tool that looks for sequence collissions based on the same algorithm that gtk-im-context-simple uses to load it's tables.

    – Jens Mühlenhoff
    5 hours ago

















  • 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 '18 at 9:23












  • Have you tried adding export GTK_IM_MODULE=gtk-im-context-simple to ~/.profile?

    – xiota
    May 18 '18 at 12:01











  • I tried it but some sequences (especially the longer ones) just don't work.

    – m93a
    May 20 '18 at 14:10






  • 1





    In the API documentation you can find a paragraph "GtkIMContextSimple reads additional compose sequences from the first of the following files that is found: ~/.config/gtk-3.0/Compose, ~/.XCompose, /usr/share/X11/locale/$locale/Compose (for locales that have a nontrivial Compose file)." developer.gnome.org/gtk3/stable/GtkIMContextSimple.html

    – Jens Mühlenhoff
    5 hours ago






  • 1





    So the gtk-im-context-simple method has a built-in table and it loads compose sequences from several additional locations. That means it could possible load shorter sequences that you don't expect. The name "simple" is a bit misleading here really. It would be nice if there was a tool that looks for sequence collissions based on the same algorithm that gtk-im-context-simple uses to load it's tables.

    – Jens Mühlenhoff
    5 hours ago
















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 '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 '18 at 9:23














Have you tried adding export GTK_IM_MODULE=gtk-im-context-simple to ~/.profile?

– xiota
May 18 '18 at 12:01





Have you tried adding export GTK_IM_MODULE=gtk-im-context-simple to ~/.profile?

– xiota
May 18 '18 at 12:01













I tried it but some sequences (especially the longer ones) just don't work.

– m93a
May 20 '18 at 14:10





I tried it but some sequences (especially the longer ones) just don't work.

– m93a
May 20 '18 at 14:10




1




1





In the API documentation you can find a paragraph "GtkIMContextSimple reads additional compose sequences from the first of the following files that is found: ~/.config/gtk-3.0/Compose, ~/.XCompose, /usr/share/X11/locale/$locale/Compose (for locales that have a nontrivial Compose file)." developer.gnome.org/gtk3/stable/GtkIMContextSimple.html

– Jens Mühlenhoff
5 hours ago





In the API documentation you can find a paragraph "GtkIMContextSimple reads additional compose sequences from the first of the following files that is found: ~/.config/gtk-3.0/Compose, ~/.XCompose, /usr/share/X11/locale/$locale/Compose (for locales that have a nontrivial Compose file)." developer.gnome.org/gtk3/stable/GtkIMContextSimple.html

– Jens Mühlenhoff
5 hours ago




1




1





So the gtk-im-context-simple method has a built-in table and it loads compose sequences from several additional locations. That means it could possible load shorter sequences that you don't expect. The name "simple" is a bit misleading here really. It would be nice if there was a tool that looks for sequence collissions based on the same algorithm that gtk-im-context-simple uses to load it's tables.

– Jens Mühlenhoff
5 hours ago





So the gtk-im-context-simple method has a built-in table and it loads compose sequences from several additional locations. That means it could possible load shorter sequences that you don't expect. The name "simple" is a bit misleading here really. It would be nice if there was a tool that looks for sequence collissions based on the same algorithm that gtk-im-context-simple uses to load it's tables.

– Jens Mühlenhoff
5 hours ago

















draft saved

draft discarded
















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














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















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Möglingen Índice Localización Historia Demografía Referencias Enlaces externos Menú de navegación48°53′18″N 9°07′45″E / 48.888333333333, 9.129166666666748°53′18″N 9°07′45″E / 48.888333333333, 9.1291666666667Sitio web oficial Mapa de Möglingen«Gemeinden in Deutschland nach Fläche, Bevölkerung und Postleitzahl am 30.09.2016»Möglingen

Virtualbox - Configuration error: Querying “UUID” failed (VERR_CFGM_VALUE_NOT_FOUND)“VERR_SUPLIB_WORLD_WRITABLE” error when trying to installing OS in virtualboxVirtual Box Kernel errorFailed to open a seesion for the virtual machineFailed to open a session for the virtual machineUbuntu 14.04 LTS Virtualbox errorcan't use VM VirtualBoxusing virtualboxI can't run Linux-64 Bit on VirtualBoxUnable to insert the virtual optical disk (VBoxguestaddition) in virtual machine for ubuntu server in win 10VirtuaBox in Ubuntu 18.04 Issues with Win10.ISO Installation

Torre de la Isleta Índice Véase también Referencias Bibliografía Enlaces externos Menú de navegación38°25′58″N 0°23′02″O / 38.43277778, -0.3838888938°25′58″N 0°23′02″O / 38.43277778, -0.38388889Torre de la Illeta de l’Horta o Torre Saleta. Base de datos de bienes inmuebles. Patrimonio Cultural. Secretaría de Estado de CulturaFicha BIC Torre de la Illeta de l’Horta. Dirección General de Patrimonio Cultural. Generalitat ValencianaLugares de interés. Ayuntamiento del CampelloTorre de la Isleta en CastillosNet.org