GTK and Qt apps seem to interpret XCompose differently

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
2
down vote

favorite
1












I'm using Ubuntu 18.04. By default, typing something like ^+2 produces ², which I don't want: I want it to be ^2. I found out that to accomplish that, one has to set GTK_IM_MODULE=xim and QT_IM_MODULE=xim to use XIM, and then a custom .XCompose file can be set up in the home directory. In my case, I replaced the old rule



<dead_circumflex> <2> : "²" twosuperior # SUPERSCRIPT TWO



with



<dead_circumflex> <2> : "^2" twosuperior # SUPERSCRIPT TWO



This seems to work fine with GTK apps (like Firefox or Gedit, or Chrome, which I don't think actually uses GTK) but not with QT (I've tested TeXStudio and Mathematica): typing ^+2 just produces ^.



Earlier, QT_IM_MODULE was not set to xim and QT programs were producing the default ², so clearly .XCompose is being read now; is it possible that QT interprets the rule differently somehow?










share|improve this question















This question has an open bounty worth +50
reputation from Javier ending ending at 2018-12-19 12:13:25Z">in 4 days.


This question has not received enough attention.















  • In "(I've tested TeXStudio and Mathematica): typing ^+2 just produces ^." shouldn't that be "... just produces ^2."?
    – DK Bose
    Dec 6 at 1:59










  • @DKBose No, producing ^2 would be the intended behavior, but I only get ^.
    – Javier
    Dec 6 at 2:03










  • I have Kubuntu 18.04 and typed ^+2 in Kate and got ^2 not ² nor just ^. Hence my query.
    – DK Bose
    Dec 6 at 2:11














up vote
2
down vote

favorite
1












I'm using Ubuntu 18.04. By default, typing something like ^+2 produces ², which I don't want: I want it to be ^2. I found out that to accomplish that, one has to set GTK_IM_MODULE=xim and QT_IM_MODULE=xim to use XIM, and then a custom .XCompose file can be set up in the home directory. In my case, I replaced the old rule



<dead_circumflex> <2> : "²" twosuperior # SUPERSCRIPT TWO



with



<dead_circumflex> <2> : "^2" twosuperior # SUPERSCRIPT TWO



This seems to work fine with GTK apps (like Firefox or Gedit, or Chrome, which I don't think actually uses GTK) but not with QT (I've tested TeXStudio and Mathematica): typing ^+2 just produces ^.



Earlier, QT_IM_MODULE was not set to xim and QT programs were producing the default ², so clearly .XCompose is being read now; is it possible that QT interprets the rule differently somehow?










share|improve this question















This question has an open bounty worth +50
reputation from Javier ending ending at 2018-12-19 12:13:25Z">in 4 days.


This question has not received enough attention.















  • In "(I've tested TeXStudio and Mathematica): typing ^+2 just produces ^." shouldn't that be "... just produces ^2."?
    – DK Bose
    Dec 6 at 1:59










  • @DKBose No, producing ^2 would be the intended behavior, but I only get ^.
    – Javier
    Dec 6 at 2:03










  • I have Kubuntu 18.04 and typed ^+2 in Kate and got ^2 not ² nor just ^. Hence my query.
    – DK Bose
    Dec 6 at 2:11












up vote
2
down vote

favorite
1









up vote
2
down vote

favorite
1






1





I'm using Ubuntu 18.04. By default, typing something like ^+2 produces ², which I don't want: I want it to be ^2. I found out that to accomplish that, one has to set GTK_IM_MODULE=xim and QT_IM_MODULE=xim to use XIM, and then a custom .XCompose file can be set up in the home directory. In my case, I replaced the old rule



<dead_circumflex> <2> : "²" twosuperior # SUPERSCRIPT TWO



with



<dead_circumflex> <2> : "^2" twosuperior # SUPERSCRIPT TWO



This seems to work fine with GTK apps (like Firefox or Gedit, or Chrome, which I don't think actually uses GTK) but not with QT (I've tested TeXStudio and Mathematica): typing ^+2 just produces ^.



Earlier, QT_IM_MODULE was not set to xim and QT programs were producing the default ², so clearly .XCompose is being read now; is it possible that QT interprets the rule differently somehow?










share|improve this question













I'm using Ubuntu 18.04. By default, typing something like ^+2 produces ², which I don't want: I want it to be ^2. I found out that to accomplish that, one has to set GTK_IM_MODULE=xim and QT_IM_MODULE=xim to use XIM, and then a custom .XCompose file can be set up in the home directory. In my case, I replaced the old rule



<dead_circumflex> <2> : "²" twosuperior # SUPERSCRIPT TWO



with



<dead_circumflex> <2> : "^2" twosuperior # SUPERSCRIPT TWO



This seems to work fine with GTK apps (like Firefox or Gedit, or Chrome, which I don't think actually uses GTK) but not with QT (I've tested TeXStudio and Mathematica): typing ^+2 just produces ^.



Earlier, QT_IM_MODULE was not set to xim and QT programs were producing the default ², so clearly .XCompose is being read now; is it possible that QT interprets the rule differently somehow?







xorg keyboard-layout gtk qt






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 5 at 18:35









Javier

612




612






This question has an open bounty worth +50
reputation from Javier ending ending at 2018-12-19 12:13:25Z">in 4 days.


This question has not received enough attention.








This question has an open bounty worth +50
reputation from Javier ending ending at 2018-12-19 12:13:25Z">in 4 days.


This question has not received enough attention.













  • In "(I've tested TeXStudio and Mathematica): typing ^+2 just produces ^." shouldn't that be "... just produces ^2."?
    – DK Bose
    Dec 6 at 1:59










  • @DKBose No, producing ^2 would be the intended behavior, but I only get ^.
    – Javier
    Dec 6 at 2:03










  • I have Kubuntu 18.04 and typed ^+2 in Kate and got ^2 not ² nor just ^. Hence my query.
    – DK Bose
    Dec 6 at 2:11
















  • In "(I've tested TeXStudio and Mathematica): typing ^+2 just produces ^." shouldn't that be "... just produces ^2."?
    – DK Bose
    Dec 6 at 1:59










  • @DKBose No, producing ^2 would be the intended behavior, but I only get ^.
    – Javier
    Dec 6 at 2:03










  • I have Kubuntu 18.04 and typed ^+2 in Kate and got ^2 not ² nor just ^. Hence my query.
    – DK Bose
    Dec 6 at 2:11















In "(I've tested TeXStudio and Mathematica): typing ^+2 just produces ^." shouldn't that be "... just produces ^2."?
– DK Bose
Dec 6 at 1:59




In "(I've tested TeXStudio and Mathematica): typing ^+2 just produces ^." shouldn't that be "... just produces ^2."?
– DK Bose
Dec 6 at 1:59












@DKBose No, producing ^2 would be the intended behavior, but I only get ^.
– Javier
Dec 6 at 2:03




@DKBose No, producing ^2 would be the intended behavior, but I only get ^.
– Javier
Dec 6 at 2:03












I have Kubuntu 18.04 and typed ^+2 in Kate and got ^2 not ² nor just ^. Hence my query.
– DK Bose
Dec 6 at 2:11




I have Kubuntu 18.04 and typed ^+2 in Kate and got ^2 not ² nor just ^. Hence my query.
– DK Bose
Dec 6 at 2:11










1 Answer
1






active

oldest

votes

















up vote
0
down vote













If you don't need the dead key feature of ^ key, you can remap the key to a regular ^ with xmodmap. Check which keycode is assigned to the key using xev and use something like xmodmap -e 'keycode 15 = asciicircum'.






share|improve this answer




















    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    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',
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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%2funix.stackexchange.com%2fquestions%2f486211%2fgtk-and-qt-apps-seem-to-interpret-xcompose-differently%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








    up vote
    0
    down vote













    If you don't need the dead key feature of ^ key, you can remap the key to a regular ^ with xmodmap. Check which keycode is assigned to the key using xev and use something like xmodmap -e 'keycode 15 = asciicircum'.






    share|improve this answer
























      up vote
      0
      down vote













      If you don't need the dead key feature of ^ key, you can remap the key to a regular ^ with xmodmap. Check which keycode is assigned to the key using xev and use something like xmodmap -e 'keycode 15 = asciicircum'.






      share|improve this answer






















        up vote
        0
        down vote










        up vote
        0
        down vote









        If you don't need the dead key feature of ^ key, you can remap the key to a regular ^ with xmodmap. Check which keycode is assigned to the key using xev and use something like xmodmap -e 'keycode 15 = asciicircum'.






        share|improve this answer












        If you don't need the dead key feature of ^ key, you can remap the key to a regular ^ with xmodmap. Check which keycode is assigned to the key using xev and use something like xmodmap -e 'keycode 15 = asciicircum'.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 50 mins ago









        L29Ah

        521114




        521114



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • 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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2funix.stackexchange.com%2fquestions%2f486211%2fgtk-and-qt-apps-seem-to-interpret-xcompose-differently%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

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?