xedit: ctrl-underscore key combination is numb

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











up vote
0
down vote

favorite












I've got a Dell Latitude and eventually use xedit under cygwin-X (and via ssh -X also on Linux machines). I need the CTRL-_ key to undo edits. That key combination is recognized by e.g. xemacs (for a different purpose).
As far as I can see the keystroke in X applications is received as ASCII 31 ("Unit Separator").
What code does xedit expect, and if it isn't ASCII 31, how can I map it to the expected one?







share|improve this question























    up vote
    0
    down vote

    favorite












    I've got a Dell Latitude and eventually use xedit under cygwin-X (and via ssh -X also on Linux machines). I need the CTRL-_ key to undo edits. That key combination is recognized by e.g. xemacs (for a different purpose).
    As far as I can see the keystroke in X applications is received as ASCII 31 ("Unit Separator").
    What code does xedit expect, and if it isn't ASCII 31, how can I map it to the expected one?







    share|improve this question





















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I've got a Dell Latitude and eventually use xedit under cygwin-X (and via ssh -X also on Linux machines). I need the CTRL-_ key to undo edits. That key combination is recognized by e.g. xemacs (for a different purpose).
      As far as I can see the keystroke in X applications is received as ASCII 31 ("Unit Separator").
      What code does xedit expect, and if it isn't ASCII 31, how can I map it to the expected one?







      share|improve this question











      I've got a Dell Latitude and eventually use xedit under cygwin-X (and via ssh -X also on Linux machines). I need the CTRL-_ key to undo edits. That key combination is recognized by e.g. xemacs (for a different purpose).
      As far as I can see the keystroke in X applications is received as ASCII 31 ("Unit Separator").
      What code does xedit expect, and if it isn't ASCII 31, how can I map it to the expected one?









      share|improve this question










      share|improve this question




      share|improve this question









      asked Jul 5 at 9:59









      Hans-Georg Scherneck

      1




      1




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote













          X applications interpret events, not keystrokes. If you ran xev, you might see something like this (underscore is a shifted key on my keyboard):



          KeyPress event, serial 34, synthetic NO, window 0xe00001,
          root 0x111, subw 0xe00002, time 1812782646, (61,35), root:(81,78),
          state 0x0, keycode 67 (keysym 0xffe3, Control_L), same_screen YES,
          XLookupString gives 0 bytes:
          XmbLookupString gives 0 bytes:
          XFilterEvent returns: False

          KeyPress event, serial 34, synthetic NO, window 0xe00001,
          root 0x111, subw 0xe00002, time 1812783382, (61,35), root:(81,78),
          state 0x4, keycode 68 (keysym 0xffe2, Shift_R), same_screen YES,
          XLookupString gives 0 bytes:
          XmbLookupString gives 0 bytes:
          XFilterEvent returns: False

          KeyPress event, serial 34, synthetic NO, window 0xe00001,
          root 0x111, subw 0xe00002, time 1812784150, (61,35), root:(81,78),
          state 0x5, keycode 35 (keysym 0x5f, underscore), same_screen YES,
          XLookupString gives 1 bytes: (1f) ""
          XmbLookupString gives 1 bytes: (1f) ""
          XFilterEvent returns: False

          KeyRelease event, serial 34, synthetic NO, window 0xe00001,
          root 0x111, subw 0xe00002, time 1812784374, (61,35), root:(81,78),
          state 0x5, keycode 35 (keysym 0x5f, underscore), same_screen YES,
          XLookupString gives 1 bytes: (1f) ""
          XFilterEvent returns: False

          KeyRelease event, serial 34, synthetic NO, window 0xe00001,
          root 0x111, subw 0xe00002, time 1812785271, (61,35), root:(81,78),
          state 0x5, keycode 68 (keysym 0xffe2, Shift_R), same_screen YES,
          XLookupString gives 0 bytes:
          XFilterEvent returns: False

          KeyRelease event, serial 34, synthetic NO, window 0xe00001,
          root 0x111, subw 0xe00002, time 1812785335, (61,35), root:(81,78),
          state 0x4, keycode 67 (keysym 0xffe3, Control_L), same_screen YES,
          XLookupString gives 0 bytes:
          XFilterEvent returns: False


          xedit uses the X Toolkit translations resource to convert those events into an action, e.g., using the default resource-setting compiled into TextTr.c:



          ":c<Key>_:" "undo()n"


          So (unless you're overriding the default resources), it's simply the control modifier plus the underscore (however your keyboard produces it).



          xedit would not recognize the analogous ASCII ^_.






          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%2f453572%2fxedit-ctrl-underscore-key-combination-is-numb%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
            1
            down vote













            X applications interpret events, not keystrokes. If you ran xev, you might see something like this (underscore is a shifted key on my keyboard):



            KeyPress event, serial 34, synthetic NO, window 0xe00001,
            root 0x111, subw 0xe00002, time 1812782646, (61,35), root:(81,78),
            state 0x0, keycode 67 (keysym 0xffe3, Control_L), same_screen YES,
            XLookupString gives 0 bytes:
            XmbLookupString gives 0 bytes:
            XFilterEvent returns: False

            KeyPress event, serial 34, synthetic NO, window 0xe00001,
            root 0x111, subw 0xe00002, time 1812783382, (61,35), root:(81,78),
            state 0x4, keycode 68 (keysym 0xffe2, Shift_R), same_screen YES,
            XLookupString gives 0 bytes:
            XmbLookupString gives 0 bytes:
            XFilterEvent returns: False

            KeyPress event, serial 34, synthetic NO, window 0xe00001,
            root 0x111, subw 0xe00002, time 1812784150, (61,35), root:(81,78),
            state 0x5, keycode 35 (keysym 0x5f, underscore), same_screen YES,
            XLookupString gives 1 bytes: (1f) ""
            XmbLookupString gives 1 bytes: (1f) ""
            XFilterEvent returns: False

            KeyRelease event, serial 34, synthetic NO, window 0xe00001,
            root 0x111, subw 0xe00002, time 1812784374, (61,35), root:(81,78),
            state 0x5, keycode 35 (keysym 0x5f, underscore), same_screen YES,
            XLookupString gives 1 bytes: (1f) ""
            XFilterEvent returns: False

            KeyRelease event, serial 34, synthetic NO, window 0xe00001,
            root 0x111, subw 0xe00002, time 1812785271, (61,35), root:(81,78),
            state 0x5, keycode 68 (keysym 0xffe2, Shift_R), same_screen YES,
            XLookupString gives 0 bytes:
            XFilterEvent returns: False

            KeyRelease event, serial 34, synthetic NO, window 0xe00001,
            root 0x111, subw 0xe00002, time 1812785335, (61,35), root:(81,78),
            state 0x4, keycode 67 (keysym 0xffe3, Control_L), same_screen YES,
            XLookupString gives 0 bytes:
            XFilterEvent returns: False


            xedit uses the X Toolkit translations resource to convert those events into an action, e.g., using the default resource-setting compiled into TextTr.c:



            ":c<Key>_:" "undo()n"


            So (unless you're overriding the default resources), it's simply the control modifier plus the underscore (however your keyboard produces it).



            xedit would not recognize the analogous ASCII ^_.






            share|improve this answer

























              up vote
              1
              down vote













              X applications interpret events, not keystrokes. If you ran xev, you might see something like this (underscore is a shifted key on my keyboard):



              KeyPress event, serial 34, synthetic NO, window 0xe00001,
              root 0x111, subw 0xe00002, time 1812782646, (61,35), root:(81,78),
              state 0x0, keycode 67 (keysym 0xffe3, Control_L), same_screen YES,
              XLookupString gives 0 bytes:
              XmbLookupString gives 0 bytes:
              XFilterEvent returns: False

              KeyPress event, serial 34, synthetic NO, window 0xe00001,
              root 0x111, subw 0xe00002, time 1812783382, (61,35), root:(81,78),
              state 0x4, keycode 68 (keysym 0xffe2, Shift_R), same_screen YES,
              XLookupString gives 0 bytes:
              XmbLookupString gives 0 bytes:
              XFilterEvent returns: False

              KeyPress event, serial 34, synthetic NO, window 0xe00001,
              root 0x111, subw 0xe00002, time 1812784150, (61,35), root:(81,78),
              state 0x5, keycode 35 (keysym 0x5f, underscore), same_screen YES,
              XLookupString gives 1 bytes: (1f) ""
              XmbLookupString gives 1 bytes: (1f) ""
              XFilterEvent returns: False

              KeyRelease event, serial 34, synthetic NO, window 0xe00001,
              root 0x111, subw 0xe00002, time 1812784374, (61,35), root:(81,78),
              state 0x5, keycode 35 (keysym 0x5f, underscore), same_screen YES,
              XLookupString gives 1 bytes: (1f) ""
              XFilterEvent returns: False

              KeyRelease event, serial 34, synthetic NO, window 0xe00001,
              root 0x111, subw 0xe00002, time 1812785271, (61,35), root:(81,78),
              state 0x5, keycode 68 (keysym 0xffe2, Shift_R), same_screen YES,
              XLookupString gives 0 bytes:
              XFilterEvent returns: False

              KeyRelease event, serial 34, synthetic NO, window 0xe00001,
              root 0x111, subw 0xe00002, time 1812785335, (61,35), root:(81,78),
              state 0x4, keycode 67 (keysym 0xffe3, Control_L), same_screen YES,
              XLookupString gives 0 bytes:
              XFilterEvent returns: False


              xedit uses the X Toolkit translations resource to convert those events into an action, e.g., using the default resource-setting compiled into TextTr.c:



              ":c<Key>_:" "undo()n"


              So (unless you're overriding the default resources), it's simply the control modifier plus the underscore (however your keyboard produces it).



              xedit would not recognize the analogous ASCII ^_.






              share|improve this answer























                up vote
                1
                down vote










                up vote
                1
                down vote









                X applications interpret events, not keystrokes. If you ran xev, you might see something like this (underscore is a shifted key on my keyboard):



                KeyPress event, serial 34, synthetic NO, window 0xe00001,
                root 0x111, subw 0xe00002, time 1812782646, (61,35), root:(81,78),
                state 0x0, keycode 67 (keysym 0xffe3, Control_L), same_screen YES,
                XLookupString gives 0 bytes:
                XmbLookupString gives 0 bytes:
                XFilterEvent returns: False

                KeyPress event, serial 34, synthetic NO, window 0xe00001,
                root 0x111, subw 0xe00002, time 1812783382, (61,35), root:(81,78),
                state 0x4, keycode 68 (keysym 0xffe2, Shift_R), same_screen YES,
                XLookupString gives 0 bytes:
                XmbLookupString gives 0 bytes:
                XFilterEvent returns: False

                KeyPress event, serial 34, synthetic NO, window 0xe00001,
                root 0x111, subw 0xe00002, time 1812784150, (61,35), root:(81,78),
                state 0x5, keycode 35 (keysym 0x5f, underscore), same_screen YES,
                XLookupString gives 1 bytes: (1f) ""
                XmbLookupString gives 1 bytes: (1f) ""
                XFilterEvent returns: False

                KeyRelease event, serial 34, synthetic NO, window 0xe00001,
                root 0x111, subw 0xe00002, time 1812784374, (61,35), root:(81,78),
                state 0x5, keycode 35 (keysym 0x5f, underscore), same_screen YES,
                XLookupString gives 1 bytes: (1f) ""
                XFilterEvent returns: False

                KeyRelease event, serial 34, synthetic NO, window 0xe00001,
                root 0x111, subw 0xe00002, time 1812785271, (61,35), root:(81,78),
                state 0x5, keycode 68 (keysym 0xffe2, Shift_R), same_screen YES,
                XLookupString gives 0 bytes:
                XFilterEvent returns: False

                KeyRelease event, serial 34, synthetic NO, window 0xe00001,
                root 0x111, subw 0xe00002, time 1812785335, (61,35), root:(81,78),
                state 0x4, keycode 67 (keysym 0xffe3, Control_L), same_screen YES,
                XLookupString gives 0 bytes:
                XFilterEvent returns: False


                xedit uses the X Toolkit translations resource to convert those events into an action, e.g., using the default resource-setting compiled into TextTr.c:



                ":c<Key>_:" "undo()n"


                So (unless you're overriding the default resources), it's simply the control modifier plus the underscore (however your keyboard produces it).



                xedit would not recognize the analogous ASCII ^_.






                share|improve this answer













                X applications interpret events, not keystrokes. If you ran xev, you might see something like this (underscore is a shifted key on my keyboard):



                KeyPress event, serial 34, synthetic NO, window 0xe00001,
                root 0x111, subw 0xe00002, time 1812782646, (61,35), root:(81,78),
                state 0x0, keycode 67 (keysym 0xffe3, Control_L), same_screen YES,
                XLookupString gives 0 bytes:
                XmbLookupString gives 0 bytes:
                XFilterEvent returns: False

                KeyPress event, serial 34, synthetic NO, window 0xe00001,
                root 0x111, subw 0xe00002, time 1812783382, (61,35), root:(81,78),
                state 0x4, keycode 68 (keysym 0xffe2, Shift_R), same_screen YES,
                XLookupString gives 0 bytes:
                XmbLookupString gives 0 bytes:
                XFilterEvent returns: False

                KeyPress event, serial 34, synthetic NO, window 0xe00001,
                root 0x111, subw 0xe00002, time 1812784150, (61,35), root:(81,78),
                state 0x5, keycode 35 (keysym 0x5f, underscore), same_screen YES,
                XLookupString gives 1 bytes: (1f) ""
                XmbLookupString gives 1 bytes: (1f) ""
                XFilterEvent returns: False

                KeyRelease event, serial 34, synthetic NO, window 0xe00001,
                root 0x111, subw 0xe00002, time 1812784374, (61,35), root:(81,78),
                state 0x5, keycode 35 (keysym 0x5f, underscore), same_screen YES,
                XLookupString gives 1 bytes: (1f) ""
                XFilterEvent returns: False

                KeyRelease event, serial 34, synthetic NO, window 0xe00001,
                root 0x111, subw 0xe00002, time 1812785271, (61,35), root:(81,78),
                state 0x5, keycode 68 (keysym 0xffe2, Shift_R), same_screen YES,
                XLookupString gives 0 bytes:
                XFilterEvent returns: False

                KeyRelease event, serial 34, synthetic NO, window 0xe00001,
                root 0x111, subw 0xe00002, time 1812785335, (61,35), root:(81,78),
                state 0x4, keycode 67 (keysym 0xffe3, Control_L), same_screen YES,
                XLookupString gives 0 bytes:
                XFilterEvent returns: False


                xedit uses the X Toolkit translations resource to convert those events into an action, e.g., using the default resource-setting compiled into TextTr.c:



                ":c<Key>_:" "undo()n"


                So (unless you're overriding the default resources), it's simply the control modifier plus the underscore (however your keyboard produces it).



                xedit would not recognize the analogous ASCII ^_.







                share|improve this answer













                share|improve this answer



                share|improve this answer











                answered Jul 5 at 20:53









                Thomas Dickey

                49k583154




                49k583154






















                     

                    draft saved


                    draft discarded


























                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f453572%2fxedit-ctrl-underscore-key-combination-is-numb%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    Peggy Mitchell

                    Palaiologos

                    The Forum (Inglewood, California)