xterm: Disable Left Alt from producing ø
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I'm on latest debian testing with i3wm on two different laptops.
Linux mango 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1
When I press LeftAlt + x I get "ø". And other special chars with other keys.
I want to disable it, as I assume it is what is stopping me from using Alt-x in emacs, which should be bound to "execute-extended-command" by default. But it only says "ø is undefined".
It does not seem to be the compose key though, as running:
setxkbmap -model pc105 -option compose:caps
Does not affect Alt-x's behavior. Where is this configured?
Update to clarify:
I'm using uxterm and terminal emacs "-nw". I added XTerm.vt100.metaSendsEscape: true to .Xdefaults and .Xresources but it had no effect.
Here is the output of xkbcomp $DISPLAY -
https://pastebin.com/BFnV4Zdz
keyboard-shortcuts keyboard keyboard-layout xterm
asked Mar 9 at 10:25
user640916user640916
1488
add a comment |
I'm on latest debian testing with i3wm on two different laptops.
Linux mango 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1
When I press LeftAlt + x I get "ø". And other special chars with other keys.
I want to disable it, as I assume it is what is stopping me from using Alt-x in emacs, which should be bound to "execute-extended-command" by default. But it only says "ø is undefined".
It does not seem to be the compose key though, as running:
setxkbmap -model pc105 -option compose:caps
Does not affect Alt-x's behavior. Where is this configured?
Update to clarify:
I'm using uxterm and terminal emacs "-nw". I added XTerm.vt100.metaSendsEscape: true to .Xdefaults and .Xresources but it had no effect.
Here is the output of xkbcomp $DISPLAY -
https://pastebin.com/BFnV4Zdz
keyboard-shortcuts keyboard keyboard-layout xterm
asked Mar 9 at 10:25
user640916user640916
1488
No it is not the compose key: This key works very differently e.g.«compose»followed byofollowed by/, to getø.
– ctrl-alt-delor
Mar 9 at 10:38
Have you tried«super key»+x?«super key»is the one with a logo on it.
– ctrl-alt-delor
Mar 9 at 10:39
@ctrl-alt-delor I use the windows key as modifier for i3wm. Super+x locks my screen.
– user640916
Mar 9 at 13:38
add a comment |
I'm on latest debian testing with i3wm on two different laptops.
Linux mango 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1
When I press LeftAlt + x I get "ø". And other special chars with other keys.
I want to disable it, as I assume it is what is stopping me from using Alt-x in emacs, which should be bound to "execute-extended-command" by default. But it only says "ø is undefined".
It does not seem to be the compose key though, as running:
setxkbmap -model pc105 -option compose:caps
Does not affect Alt-x's behavior. Where is this configured?
Update to clarify:
I'm using uxterm and terminal emacs "-nw". I added XTerm.vt100.metaSendsEscape: true to .Xdefaults and .Xresources but it had no effect.
Here is the output of xkbcomp $DISPLAY -
https://pastebin.com/BFnV4Zdz
keyboard-shortcuts keyboard keyboard-layout xterm
asked Mar 9 at 10:25
user640916user640916
1488
I'm on latest debian testing with i3wm on two different laptops.
Linux mango 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1
When I press LeftAlt + x I get "ø". And other special chars with other keys.
I want to disable it, as I assume it is what is stopping me from using Alt-x in emacs, which should be bound to "execute-extended-command" by default. But it only says "ø is undefined".
It does not seem to be the compose key though, as running:
setxkbmap -model pc105 -option compose:caps
Does not affect Alt-x's behavior. Where is this configured?
Update to clarify:
I'm using uxterm and terminal emacs "-nw". I added XTerm.vt100.metaSendsEscape: true to .Xdefaults and .Xresources but it had no effect.
Here is the output of xkbcomp $DISPLAY -
https://pastebin.com/BFnV4Zdz
keyboard-shortcuts keyboard keyboard-layout xterm
keyboard-shortcuts keyboard keyboard-layout xterm
asked Mar 9 at 10:25
user640916user640916
1488
asked Mar 9 at 10:25
user640916user640916
1488
edited Mar 9 at 14:14
user640916
asked Mar 9 at 10:25
user640916user640916
1488
asked Mar 9 at 10:25
user640916user640916
1488
asked Mar 9 at 10:25
user640916user640916
1488
1488
No it is not the compose key: This key works very differently e.g.«compose»followed byofollowed by/, to getø.
– ctrl-alt-delor
Mar 9 at 10:38
Have you tried«super key»+x?«super key»is the one with a logo on it.
– ctrl-alt-delor
Mar 9 at 10:39
@ctrl-alt-delor I use the windows key as modifier for i3wm. Super+x locks my screen.
– user640916
Mar 9 at 13:38
add a comment |
No it is not the compose key: This key works very differently e.g.«compose»followed byofollowed by/, to getø.
– ctrl-alt-delor
Mar 9 at 10:38
Have you tried«super key»+x?«super key»is the one with a logo on it.
– ctrl-alt-delor
Mar 9 at 10:39
@ctrl-alt-delor I use the windows key as modifier for i3wm. Super+x locks my screen.
– user640916
Mar 9 at 13:38
No it is not the compose key: This key works very differently e.g.
«compose» followed by o followed by /, to get ø.– ctrl-alt-delor
Mar 9 at 10:38
No it is not the compose key: This key works very differently e.g.
«compose» followed by o followed by /, to get ø.– ctrl-alt-delor
Mar 9 at 10:38
Have you tried
«super key» +x? «super key» is the one with a logo on it.– ctrl-alt-delor
Mar 9 at 10:39
Have you tried
«super key» +x? «super key» is the one with a logo on it.– ctrl-alt-delor
Mar 9 at 10:39
@ctrl-alt-delor I use the windows key as modifier for i3wm. Super+x locks my screen.
– user640916
Mar 9 at 13:38
@ctrl-alt-delor I use the windows key as modifier for i3wm. Super+x locks my screen.
– user640916
Mar 9 at 13:38
add a comment |
2 Answers
2
active
oldest
votes
That's curious; it's the Right Alt which is AltGr and should generate such characters, but no file under /usr/share/X11/xkb seems to map AltGr+x to ø.
I suspect that you're running emacs in a terminal emulator -- in which case you should let the terminal emulator map Alt to Esc instead; in xterm, you can do that with
*.vt100.metaSendsEscape: true
If you're not running emacs in a term emulator, then please post the whole output of xkbcomp $DISPLAY - somewhere and link it from your question.
answered Mar 9 at 11:42
mosvymosvy
9,0871833
Sorry, I should have added that myself. Yes, I run uxterm and emacs -nw but I get the ø also outside of emacs. I added the output to my question. Thank you :)
– user640916
Mar 9 at 13:40
1
if it's uxterm, you should probably useUXTerm.vt100.... Try withuxterm -xrm '*.vt100.metaSendsEscape: true', and if it works, add that to~/.Xresources.
– mosvy
Mar 9 at 13:45
add a comment |
It might be built into the application (emacs itself, or a terminal if you're using "emacs -nw"). xterm does this, for instance (as documented originally in the eightBitInput resource, or later, in metaSendsEscape), and some other programs (such as st) copy it.
The feature was implemented in xterm in 2003:
modify handling of
eightBitInputresource in UTF-8 mode to translate the value into UTF-8. Otherwise an illegal UTF-8 code is sent to the application (report by Bram Moolenaar).
answered Mar 9 at 10:48
Thomas DickeyThomas Dickey
54.1k5106179
When I run xterm instead of uxterm, alt+x indeed behaves differently. Like backspace
– user640916
Mar 9 at 13:39
add a comment |
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',
autoActivateHeartbeat: false,
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
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505298%2fxterm-disable-left-alt-from-producing-%25c3%25b8%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
That's curious; it's the Right Alt which is AltGr and should generate such characters, but no file under /usr/share/X11/xkb seems to map AltGr+x to ø.
I suspect that you're running emacs in a terminal emulator -- in which case you should let the terminal emulator map Alt to Esc instead; in xterm, you can do that with
*.vt100.metaSendsEscape: true
If you're not running emacs in a term emulator, then please post the whole output of xkbcomp $DISPLAY - somewhere and link it from your question.
answered Mar 9 at 11:42
mosvymosvy
9,0871833
Sorry, I should have added that myself. Yes, I run uxterm and emacs -nw but I get the ø also outside of emacs. I added the output to my question. Thank you :)
– user640916
Mar 9 at 13:40
1
if it's uxterm, you should probably useUXTerm.vt100.... Try withuxterm -xrm '*.vt100.metaSendsEscape: true', and if it works, add that to~/.Xresources.
– mosvy
Mar 9 at 13:45
add a comment |
That's curious; it's the Right Alt which is AltGr and should generate such characters, but no file under /usr/share/X11/xkb seems to map AltGr+x to ø.
I suspect that you're running emacs in a terminal emulator -- in which case you should let the terminal emulator map Alt to Esc instead; in xterm, you can do that with
*.vt100.metaSendsEscape: true
If you're not running emacs in a term emulator, then please post the whole output of xkbcomp $DISPLAY - somewhere and link it from your question.
answered Mar 9 at 11:42
mosvymosvy
9,0871833
Sorry, I should have added that myself. Yes, I run uxterm and emacs -nw but I get the ø also outside of emacs. I added the output to my question. Thank you :)
– user640916
Mar 9 at 13:40
1
if it's uxterm, you should probably useUXTerm.vt100.... Try withuxterm -xrm '*.vt100.metaSendsEscape: true', and if it works, add that to~/.Xresources.
– mosvy
Mar 9 at 13:45
add a comment |
That's curious; it's the Right Alt which is AltGr and should generate such characters, but no file under /usr/share/X11/xkb seems to map AltGr+x to ø.
I suspect that you're running emacs in a terminal emulator -- in which case you should let the terminal emulator map Alt to Esc instead; in xterm, you can do that with
*.vt100.metaSendsEscape: true
If you're not running emacs in a term emulator, then please post the whole output of xkbcomp $DISPLAY - somewhere and link it from your question.
answered Mar 9 at 11:42
mosvymosvy
9,0871833
That's curious; it's the Right Alt which is AltGr and should generate such characters, but no file under /usr/share/X11/xkb seems to map AltGr+x to ø.
I suspect that you're running emacs in a terminal emulator -- in which case you should let the terminal emulator map Alt to Esc instead; in xterm, you can do that with
*.vt100.metaSendsEscape: true
If you're not running emacs in a term emulator, then please post the whole output of xkbcomp $DISPLAY - somewhere and link it from your question.
answered Mar 9 at 11:42
mosvymosvy
9,0871833
edited Mar 9 at 13:48
answered Mar 9 at 11:42
mosvymosvy
9,0871833
answered Mar 9 at 11:42
mosvymosvy
9,0871833
answered Mar 9 at 11:42
mosvymosvy
9,0871833
9,0871833
Sorry, I should have added that myself. Yes, I run uxterm and emacs -nw but I get the ø also outside of emacs. I added the output to my question. Thank you :)
– user640916
Mar 9 at 13:40
1
if it's uxterm, you should probably useUXTerm.vt100.... Try withuxterm -xrm '*.vt100.metaSendsEscape: true', and if it works, add that to~/.Xresources.
– mosvy
Mar 9 at 13:45
add a comment |
Sorry, I should have added that myself. Yes, I run uxterm and emacs -nw but I get the ø also outside of emacs. I added the output to my question. Thank you :)
– user640916
Mar 9 at 13:40
1
if it's uxterm, you should probably useUXTerm.vt100.... Try withuxterm -xrm '*.vt100.metaSendsEscape: true', and if it works, add that to~/.Xresources.
– mosvy
Mar 9 at 13:45
Sorry, I should have added that myself. Yes, I run uxterm and emacs -nw but I get the ø also outside of emacs. I added the output to my question. Thank you :)
– user640916
Mar 9 at 13:40
Sorry, I should have added that myself. Yes, I run uxterm and emacs -nw but I get the ø also outside of emacs. I added the output to my question. Thank you :)
– user640916
Mar 9 at 13:40
1
1
if it's uxterm, you should probably use
UXTerm.vt100.... Try with uxterm -xrm '*.vt100.metaSendsEscape: true', and if it works, add that to ~/.Xresources.– mosvy
Mar 9 at 13:45
if it's uxterm, you should probably use
UXTerm.vt100.... Try with uxterm -xrm '*.vt100.metaSendsEscape: true', and if it works, add that to ~/.Xresources.– mosvy
Mar 9 at 13:45
add a comment |
It might be built into the application (emacs itself, or a terminal if you're using "emacs -nw"). xterm does this, for instance (as documented originally in the eightBitInput resource, or later, in metaSendsEscape), and some other programs (such as st) copy it.
The feature was implemented in xterm in 2003:
modify handling of
eightBitInputresource in UTF-8 mode to translate the value into UTF-8. Otherwise an illegal UTF-8 code is sent to the application (report by Bram Moolenaar).
answered Mar 9 at 10:48
Thomas DickeyThomas Dickey
54.1k5106179
When I run xterm instead of uxterm, alt+x indeed behaves differently. Like backspace
– user640916
Mar 9 at 13:39
add a comment |
It might be built into the application (emacs itself, or a terminal if you're using "emacs -nw"). xterm does this, for instance (as documented originally in the eightBitInput resource, or later, in metaSendsEscape), and some other programs (such as st) copy it.
The feature was implemented in xterm in 2003:
modify handling of
eightBitInputresource in UTF-8 mode to translate the value into UTF-8. Otherwise an illegal UTF-8 code is sent to the application (report by Bram Moolenaar).
answered Mar 9 at 10:48
Thomas DickeyThomas Dickey
54.1k5106179
When I run xterm instead of uxterm, alt+x indeed behaves differently. Like backspace
– user640916
Mar 9 at 13:39
add a comment |
It might be built into the application (emacs itself, or a terminal if you're using "emacs -nw"). xterm does this, for instance (as documented originally in the eightBitInput resource, or later, in metaSendsEscape), and some other programs (such as st) copy it.
The feature was implemented in xterm in 2003:
modify handling of
eightBitInputresource in UTF-8 mode to translate the value into UTF-8. Otherwise an illegal UTF-8 code is sent to the application (report by Bram Moolenaar).
answered Mar 9 at 10:48
Thomas DickeyThomas Dickey
54.1k5106179
It might be built into the application (emacs itself, or a terminal if you're using "emacs -nw"). xterm does this, for instance (as documented originally in the eightBitInput resource, or later, in metaSendsEscape), and some other programs (such as st) copy it.
The feature was implemented in xterm in 2003:
modify handling of
eightBitInputresource in UTF-8 mode to translate the value into UTF-8. Otherwise an illegal UTF-8 code is sent to the application (report by Bram Moolenaar).
answered Mar 9 at 10:48
Thomas DickeyThomas Dickey
54.1k5106179
edited Mar 9 at 11:49
answered Mar 9 at 10:48
Thomas DickeyThomas Dickey
54.1k5106179
answered Mar 9 at 10:48
Thomas DickeyThomas Dickey
54.1k5106179
answered Mar 9 at 10:48
Thomas DickeyThomas Dickey
54.1k5106179
54.1k5106179
When I run xterm instead of uxterm, alt+x indeed behaves differently. Like backspace
– user640916
Mar 9 at 13:39
add a comment |
When I run xterm instead of uxterm, alt+x indeed behaves differently. Like backspace
– user640916
Mar 9 at 13:39
When I run xterm instead of uxterm, alt+x indeed behaves differently. Like backspace
– user640916
Mar 9 at 13:39
When I run xterm instead of uxterm, alt+x indeed behaves differently. Like backspace
– user640916
Mar 9 at 13:39
add a comment |
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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505298%2fxterm-disable-left-alt-from-producing-%25c3%25b8%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
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
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
No it is not the compose key: This key works very differently e.g.
«compose»followed byofollowed by/, to getø.– ctrl-alt-delor
Mar 9 at 10:38
Have you tried
«super key»+x?«super key»is the one with a logo on it.– ctrl-alt-delor
Mar 9 at 10:39
@ctrl-alt-delor I use the windows key as modifier for i3wm. Super+x locks my screen.
– user640916
Mar 9 at 13:38