How to know what is super key?

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











up vote
1
down vote

favorite












I have this output of xmodmap command:



shift Shift_L (0x32), Shift_R (0x3e)
lock Caps_Lock (0x42)
control Control_L (0x25), Caps_Lock (0x42), Control_R (0x69)
mod1 Alt_L (0x40), Alt_R (0x6c), Meta_L (0xcd)
mod2 Num_Lock (0x4d)
mod3
mod4 Super_L (0x85), Super_R (0x86), Super_L (0xce), Hyper_L (0xcf)
mod5 ISO_Level3_Shift (0x5c), Mode_switch (0xcb)


So I wonder what's super key here? Problem is that when I try to map super key, here I assume mod4 as windows button left to a combine key using sxhkd daemon, it doesn't seem to work, for example, map to open firefox, no effect.










share|improve this question

























    up vote
    1
    down vote

    favorite












    I have this output of xmodmap command:



    shift Shift_L (0x32), Shift_R (0x3e)
    lock Caps_Lock (0x42)
    control Control_L (0x25), Caps_Lock (0x42), Control_R (0x69)
    mod1 Alt_L (0x40), Alt_R (0x6c), Meta_L (0xcd)
    mod2 Num_Lock (0x4d)
    mod3
    mod4 Super_L (0x85), Super_R (0x86), Super_L (0xce), Hyper_L (0xcf)
    mod5 ISO_Level3_Shift (0x5c), Mode_switch (0xcb)


    So I wonder what's super key here? Problem is that when I try to map super key, here I assume mod4 as windows button left to a combine key using sxhkd daemon, it doesn't seem to work, for example, map to open firefox, no effect.










    share|improve this question























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I have this output of xmodmap command:



      shift Shift_L (0x32), Shift_R (0x3e)
      lock Caps_Lock (0x42)
      control Control_L (0x25), Caps_Lock (0x42), Control_R (0x69)
      mod1 Alt_L (0x40), Alt_R (0x6c), Meta_L (0xcd)
      mod2 Num_Lock (0x4d)
      mod3
      mod4 Super_L (0x85), Super_R (0x86), Super_L (0xce), Hyper_L (0xcf)
      mod5 ISO_Level3_Shift (0x5c), Mode_switch (0xcb)


      So I wonder what's super key here? Problem is that when I try to map super key, here I assume mod4 as windows button left to a combine key using sxhkd daemon, it doesn't seem to work, for example, map to open firefox, no effect.










      share|improve this question













      I have this output of xmodmap command:



      shift Shift_L (0x32), Shift_R (0x3e)
      lock Caps_Lock (0x42)
      control Control_L (0x25), Caps_Lock (0x42), Control_R (0x69)
      mod1 Alt_L (0x40), Alt_R (0x6c), Meta_L (0xcd)
      mod2 Num_Lock (0x4d)
      mod3
      mod4 Super_L (0x85), Super_R (0x86), Super_L (0xce), Hyper_L (0xcf)
      mod5 ISO_Level3_Shift (0x5c), Mode_switch (0xcb)


      So I wonder what's super key here? Problem is that when I try to map super key, here I assume mod4 as windows button left to a combine key using sxhkd daemon, it doesn't seem to work, for example, map to open firefox, no effect.







      xmodmap super-key






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 5 hours ago









      Tuyen Pham

      34411




      34411




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          5
          down vote













          You have to use the command xev, check xev man for more information.



          Call xev from terminal, then click the "super key", after then check the output information in terminal. It will be something like this:



          KeyRelease event, serial 37, synthetic NO, window 0x4000001,
          root 0x75, subw 0x0, time 2014984514, (70,-18), root:(82,60),
          state 0x50, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
          XLookupString gives 0 bytes:
          XFilterEvent returns: False


          xev tends to generate a lot of output, especially when you move your mouse over terminal window. You may have to scroll back a while to find the output you're looking for. In the previous output, we see that the super_L has keycode 115. This is what you need to feed to xmodmap.



          xmodmap is only for remapping keys. It helps you to map keys together. It can't provide any information about the key code.






          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: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            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%2f475581%2fhow-to-know-what-is-super-key%23new-answer', 'question_page');

            );

            Post as a guest






























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            5
            down vote













            You have to use the command xev, check xev man for more information.



            Call xev from terminal, then click the "super key", after then check the output information in terminal. It will be something like this:



            KeyRelease event, serial 37, synthetic NO, window 0x4000001,
            root 0x75, subw 0x0, time 2014984514, (70,-18), root:(82,60),
            state 0x50, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
            XLookupString gives 0 bytes:
            XFilterEvent returns: False


            xev tends to generate a lot of output, especially when you move your mouse over terminal window. You may have to scroll back a while to find the output you're looking for. In the previous output, we see that the super_L has keycode 115. This is what you need to feed to xmodmap.



            xmodmap is only for remapping keys. It helps you to map keys together. It can't provide any information about the key code.






            share|improve this answer


























              up vote
              5
              down vote













              You have to use the command xev, check xev man for more information.



              Call xev from terminal, then click the "super key", after then check the output information in terminal. It will be something like this:



              KeyRelease event, serial 37, synthetic NO, window 0x4000001,
              root 0x75, subw 0x0, time 2014984514, (70,-18), root:(82,60),
              state 0x50, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
              XLookupString gives 0 bytes:
              XFilterEvent returns: False


              xev tends to generate a lot of output, especially when you move your mouse over terminal window. You may have to scroll back a while to find the output you're looking for. In the previous output, we see that the super_L has keycode 115. This is what you need to feed to xmodmap.



              xmodmap is only for remapping keys. It helps you to map keys together. It can't provide any information about the key code.






              share|improve this answer
























                up vote
                5
                down vote










                up vote
                5
                down vote









                You have to use the command xev, check xev man for more information.



                Call xev from terminal, then click the "super key", after then check the output information in terminal. It will be something like this:



                KeyRelease event, serial 37, synthetic NO, window 0x4000001,
                root 0x75, subw 0x0, time 2014984514, (70,-18), root:(82,60),
                state 0x50, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
                XLookupString gives 0 bytes:
                XFilterEvent returns: False


                xev tends to generate a lot of output, especially when you move your mouse over terminal window. You may have to scroll back a while to find the output you're looking for. In the previous output, we see that the super_L has keycode 115. This is what you need to feed to xmodmap.



                xmodmap is only for remapping keys. It helps you to map keys together. It can't provide any information about the key code.






                share|improve this answer














                You have to use the command xev, check xev man for more information.



                Call xev from terminal, then click the "super key", after then check the output information in terminal. It will be something like this:



                KeyRelease event, serial 37, synthetic NO, window 0x4000001,
                root 0x75, subw 0x0, time 2014984514, (70,-18), root:(82,60),
                state 0x50, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
                XLookupString gives 0 bytes:
                XFilterEvent returns: False


                xev tends to generate a lot of output, especially when you move your mouse over terminal window. You may have to scroll back a while to find the output you're looking for. In the previous output, we see that the super_L has keycode 115. This is what you need to feed to xmodmap.



                xmodmap is only for remapping keys. It helps you to map keys together. It can't provide any information about the key code.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited 3 hours ago









                Jeff Schaller

                33.9k851113




                33.9k851113










                answered 4 hours ago









                Goro

                9,41464488




                9,41464488



























                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f475581%2fhow-to-know-what-is-super-key%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Comments

                    Popular posts from this blog

                    What does second last employer means? [closed]

                    Installing NextGIS Connect into QGIS 3?

                    One-line joke