alt-d alt-f etc. stops working in my xterm
Something weird sometimes happens on my Debian system. Typically at the prompt line I can use combo like alt-d to delete a word, alt-f to go to the next word, etc.
But quite regularly something happens in my xterm that makes alt-d and alt-f not work anymore: suddenly they print 'ä' (alt-d) and 'æ' (alt-f).
Note that this happens in a terminal that was acting like I wanted to at first. But then somehow must send a code or something that changes the behavior of the terminal.
It happens in xterm because that's where I always work. If I go to a console by doing ctrl+alt+f1 then by default alt-d does what I want (delete word) and so does alt-f. Maybe that I could screw that one too by doing some bad manipulation: I just don't know because I don't work in text mode.
Also note that if I spawn an xterm from the "broken" xterm, then the new xterm work as I expect.
What is going on? What am I turning on that was off previously?
My .Xresources says that and, once again, when I open an xterm it behaves as I expect it, it's only later on that "something" makes that it goes back to broken "I-print-characters-with-diacritics-and-other-nonsense" mode:
$ more .Xresources
XTerm.vt100.eightBitInput: false
XTerm*eightBitInput: False
linux xterm
asked May 18 '11 at 15:48
WeezyWeezy
3451414
add a comment |
Something weird sometimes happens on my Debian system. Typically at the prompt line I can use combo like alt-d to delete a word, alt-f to go to the next word, etc.
But quite regularly something happens in my xterm that makes alt-d and alt-f not work anymore: suddenly they print 'ä' (alt-d) and 'æ' (alt-f).
Note that this happens in a terminal that was acting like I wanted to at first. But then somehow must send a code or something that changes the behavior of the terminal.
It happens in xterm because that's where I always work. If I go to a console by doing ctrl+alt+f1 then by default alt-d does what I want (delete word) and so does alt-f. Maybe that I could screw that one too by doing some bad manipulation: I just don't know because I don't work in text mode.
Also note that if I spawn an xterm from the "broken" xterm, then the new xterm work as I expect.
What is going on? What am I turning on that was off previously?
My .Xresources says that and, once again, when I open an xterm it behaves as I expect it, it's only later on that "something" makes that it goes back to broken "I-print-characters-with-diacritics-and-other-nonsense" mode:
$ more .Xresources
XTerm.vt100.eightBitInput: false
XTerm*eightBitInput: False
linux xterm
asked May 18 '11 at 15:48
WeezyWeezy
3451414
add a comment |
Something weird sometimes happens on my Debian system. Typically at the prompt line I can use combo like alt-d to delete a word, alt-f to go to the next word, etc.
But quite regularly something happens in my xterm that makes alt-d and alt-f not work anymore: suddenly they print 'ä' (alt-d) and 'æ' (alt-f).
Note that this happens in a terminal that was acting like I wanted to at first. But then somehow must send a code or something that changes the behavior of the terminal.
It happens in xterm because that's where I always work. If I go to a console by doing ctrl+alt+f1 then by default alt-d does what I want (delete word) and so does alt-f. Maybe that I could screw that one too by doing some bad manipulation: I just don't know because I don't work in text mode.
Also note that if I spawn an xterm from the "broken" xterm, then the new xterm work as I expect.
What is going on? What am I turning on that was off previously?
My .Xresources says that and, once again, when I open an xterm it behaves as I expect it, it's only later on that "something" makes that it goes back to broken "I-print-characters-with-diacritics-and-other-nonsense" mode:
$ more .Xresources
XTerm.vt100.eightBitInput: false
XTerm*eightBitInput: False
linux xterm
asked May 18 '11 at 15:48
WeezyWeezy
3451414
Something weird sometimes happens on my Debian system. Typically at the prompt line I can use combo like alt-d to delete a word, alt-f to go to the next word, etc.
But quite regularly something happens in my xterm that makes alt-d and alt-f not work anymore: suddenly they print 'ä' (alt-d) and 'æ' (alt-f).
Note that this happens in a terminal that was acting like I wanted to at first. But then somehow must send a code or something that changes the behavior of the terminal.
It happens in xterm because that's where I always work. If I go to a console by doing ctrl+alt+f1 then by default alt-d does what I want (delete word) and so does alt-f. Maybe that I could screw that one too by doing some bad manipulation: I just don't know because I don't work in text mode.
Also note that if I spawn an xterm from the "broken" xterm, then the new xterm work as I expect.
What is going on? What am I turning on that was off previously?
My .Xresources says that and, once again, when I open an xterm it behaves as I expect it, it's only later on that "something" makes that it goes back to broken "I-print-characters-with-diacritics-and-other-nonsense" mode:
$ more .Xresources
XTerm.vt100.eightBitInput: false
XTerm*eightBitInput: False
linux xterm
linux xterm
asked May 18 '11 at 15:48
WeezyWeezy
3451414
asked May 18 '11 at 15:48
WeezyWeezy
3451414
edited May 18 '11 at 15:53
Weezy
asked May 18 '11 at 15:48
WeezyWeezy
3451414
asked May 18 '11 at 15:48
WeezyWeezy
3451414
asked May 18 '11 at 15:48
WeezyWeezy
3451414
3451414
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
you need
xterm*metaSendsEscape: true
in your ~/.Xdefaults
xrdb ~/.Xdefaults
Start a new xterm, hopefully that shouldn't have the problem anymore
answered May 18 '11 at 16:49
freethinkerfreethinker
2,75031519
@freethinkey: when I start a new xterm there's never any issue: but it drives me crazy when my current xterm does it. But how comes at first it works, then someone the xterm interprets a meta as not an escape anymore even though 5 seconds before that same xterm interpreted it as an escape? (+1 btw)
– Weezy
May 18 '11 at 19:35
well not sure whats resetting the settings, you can do a ctrl+leftclick and see if "Meta Sends Escape" is ticked or not, if it happens again
– freethinker
May 19 '11 at 1:51
2
Worked for me. xterm now black on white instead of white in black as it was before.
– SabreWolfy
Oct 14 '12 at 22:36
add a comment |
add this:
% grep -i escape .Xdefaults
xterm*metaSendsEscape: true
(so, tell xterm that your alt key is sending escape)
answered May 18 '11 at 16:50
akiraakira
49k15112152
+1 too, same comment as for freethinker: how comes at first it works, then someone the xterm interprets a meta as not an escape anymore even though 5 seconds before that same xterm interpreted it as an escape?
– Weezy
May 18 '11 at 19:36
well, you can change things on-the-fly, may that be by accident or whatever: if alt stops working, check your xterm by pressing strg leftmouse and see if the option is ticked (just like @freethinker said). then investigate, if yout pressed some keys before the change happened
– akira
May 19 '11 at 5:55
2
german are we? strg? Surely that must be ctrl!? :)
– Weezy
May 19 '11 at 15:22
well, brainiac, it states 'germany' at my profile quite clearly, so ... trivial to spot, even without whats printed on the keyboard.
– akira
May 19 '11 at 16:17
add a comment |
I have the same problem here. Everything works fine on my local xterm on Debian. However, if I ssh into a RHEL server, m-b/m-f doesn't work. They still don't work even after I logged out from RHEL.
I digged the source code and find a hack, just add the following lines in your ~/.Xresources:
XTerm*VT100*Translations: #override n
Meta <KeyPress>:insert-seven-bit()
answered Feb 3 at 3:18
zhao tianleizhao tianlei
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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
});
}
});
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%2fsuperuser.com%2fquestions%2f285306%2falt-d-alt-f-etc-stops-working-in-my-xterm%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
you need
xterm*metaSendsEscape: true
in your ~/.Xdefaults
xrdb ~/.Xdefaults
Start a new xterm, hopefully that shouldn't have the problem anymore
answered May 18 '11 at 16:49
freethinkerfreethinker
2,75031519
@freethinkey: when I start a new xterm there's never any issue: but it drives me crazy when my current xterm does it. But how comes at first it works, then someone the xterm interprets a meta as not an escape anymore even though 5 seconds before that same xterm interpreted it as an escape? (+1 btw)
– Weezy
May 18 '11 at 19:35
well not sure whats resetting the settings, you can do a ctrl+leftclick and see if "Meta Sends Escape" is ticked or not, if it happens again
– freethinker
May 19 '11 at 1:51
2
Worked for me. xterm now black on white instead of white in black as it was before.
– SabreWolfy
Oct 14 '12 at 22:36
add a comment |
you need
xterm*metaSendsEscape: true
in your ~/.Xdefaults
xrdb ~/.Xdefaults
Start a new xterm, hopefully that shouldn't have the problem anymore
answered May 18 '11 at 16:49
freethinkerfreethinker
2,75031519
@freethinkey: when I start a new xterm there's never any issue: but it drives me crazy when my current xterm does it. But how comes at first it works, then someone the xterm interprets a meta as not an escape anymore even though 5 seconds before that same xterm interpreted it as an escape? (+1 btw)
– Weezy
May 18 '11 at 19:35
well not sure whats resetting the settings, you can do a ctrl+leftclick and see if "Meta Sends Escape" is ticked or not, if it happens again
– freethinker
May 19 '11 at 1:51
2
Worked for me. xterm now black on white instead of white in black as it was before.
– SabreWolfy
Oct 14 '12 at 22:36
add a comment |
you need
xterm*metaSendsEscape: true
in your ~/.Xdefaults
xrdb ~/.Xdefaults
Start a new xterm, hopefully that shouldn't have the problem anymore
answered May 18 '11 at 16:49
freethinkerfreethinker
2,75031519
you need
xterm*metaSendsEscape: true
in your ~/.Xdefaults
xrdb ~/.Xdefaults
Start a new xterm, hopefully that shouldn't have the problem anymore
answered May 18 '11 at 16:49
freethinkerfreethinker
2,75031519
answered May 18 '11 at 16:49
freethinkerfreethinker
2,75031519
answered May 18 '11 at 16:49
freethinkerfreethinker
2,75031519
answered May 18 '11 at 16:49
freethinkerfreethinker
2,75031519
2,75031519
@freethinkey: when I start a new xterm there's never any issue: but it drives me crazy when my current xterm does it. But how comes at first it works, then someone the xterm interprets a meta as not an escape anymore even though 5 seconds before that same xterm interpreted it as an escape? (+1 btw)
– Weezy
May 18 '11 at 19:35
well not sure whats resetting the settings, you can do a ctrl+leftclick and see if "Meta Sends Escape" is ticked or not, if it happens again
– freethinker
May 19 '11 at 1:51
2
Worked for me. xterm now black on white instead of white in black as it was before.
– SabreWolfy
Oct 14 '12 at 22:36
add a comment |
@freethinkey: when I start a new xterm there's never any issue: but it drives me crazy when my current xterm does it. But how comes at first it works, then someone the xterm interprets a meta as not an escape anymore even though 5 seconds before that same xterm interpreted it as an escape? (+1 btw)
– Weezy
May 18 '11 at 19:35
well not sure whats resetting the settings, you can do a ctrl+leftclick and see if "Meta Sends Escape" is ticked or not, if it happens again
– freethinker
May 19 '11 at 1:51
2
Worked for me. xterm now black on white instead of white in black as it was before.
– SabreWolfy
Oct 14 '12 at 22:36
@freethinkey: when I start a new xterm there's never any issue: but it drives me crazy when my current xterm does it. But how comes at first it works, then someone the xterm interprets a meta as not an escape anymore even though 5 seconds before that same xterm interpreted it as an escape? (+1 btw)
– Weezy
May 18 '11 at 19:35
@freethinkey: when I start a new xterm there's never any issue: but it drives me crazy when my current xterm does it. But how comes at first it works, then someone the xterm interprets a meta as not an escape anymore even though 5 seconds before that same xterm interpreted it as an escape? (+1 btw)
– Weezy
May 18 '11 at 19:35
well not sure whats resetting the settings, you can do a ctrl+leftclick and see if "Meta Sends Escape" is ticked or not, if it happens again
– freethinker
May 19 '11 at 1:51
well not sure whats resetting the settings, you can do a ctrl+leftclick and see if "Meta Sends Escape" is ticked or not, if it happens again
– freethinker
May 19 '11 at 1:51
2
2
Worked for me. xterm now black on white instead of white in black as it was before.
– SabreWolfy
Oct 14 '12 at 22:36
Worked for me. xterm now black on white instead of white in black as it was before.
– SabreWolfy
Oct 14 '12 at 22:36
add a comment |
add this:
% grep -i escape .Xdefaults
xterm*metaSendsEscape: true
(so, tell xterm that your alt key is sending escape)
answered May 18 '11 at 16:50
akiraakira
49k15112152
+1 too, same comment as for freethinker: how comes at first it works, then someone the xterm interprets a meta as not an escape anymore even though 5 seconds before that same xterm interpreted it as an escape?
– Weezy
May 18 '11 at 19:36
well, you can change things on-the-fly, may that be by accident or whatever: if alt stops working, check your xterm by pressing strg leftmouse and see if the option is ticked (just like @freethinker said). then investigate, if yout pressed some keys before the change happened
– akira
May 19 '11 at 5:55
2
german are we? strg? Surely that must be ctrl!? :)
– Weezy
May 19 '11 at 15:22
well, brainiac, it states 'germany' at my profile quite clearly, so ... trivial to spot, even without whats printed on the keyboard.
– akira
May 19 '11 at 16:17
add a comment |
add this:
% grep -i escape .Xdefaults
xterm*metaSendsEscape: true
(so, tell xterm that your alt key is sending escape)
answered May 18 '11 at 16:50
akiraakira
49k15112152
+1 too, same comment as for freethinker: how comes at first it works, then someone the xterm interprets a meta as not an escape anymore even though 5 seconds before that same xterm interpreted it as an escape?
– Weezy
May 18 '11 at 19:36
well, you can change things on-the-fly, may that be by accident or whatever: if alt stops working, check your xterm by pressing strg leftmouse and see if the option is ticked (just like @freethinker said). then investigate, if yout pressed some keys before the change happened
– akira
May 19 '11 at 5:55
2
german are we? strg? Surely that must be ctrl!? :)
– Weezy
May 19 '11 at 15:22
well, brainiac, it states 'germany' at my profile quite clearly, so ... trivial to spot, even without whats printed on the keyboard.
– akira
May 19 '11 at 16:17
add a comment |
add this:
% grep -i escape .Xdefaults
xterm*metaSendsEscape: true
(so, tell xterm that your alt key is sending escape)
answered May 18 '11 at 16:50
akiraakira
49k15112152
add this:
% grep -i escape .Xdefaults
xterm*metaSendsEscape: true
(so, tell xterm that your alt key is sending escape)
answered May 18 '11 at 16:50
akiraakira
49k15112152
answered May 18 '11 at 16:50
akiraakira
49k15112152
answered May 18 '11 at 16:50
akiraakira
49k15112152
answered May 18 '11 at 16:50
akiraakira
49k15112152
49k15112152
+1 too, same comment as for freethinker: how comes at first it works, then someone the xterm interprets a meta as not an escape anymore even though 5 seconds before that same xterm interpreted it as an escape?
– Weezy
May 18 '11 at 19:36
well, you can change things on-the-fly, may that be by accident or whatever: if alt stops working, check your xterm by pressing strg leftmouse and see if the option is ticked (just like @freethinker said). then investigate, if yout pressed some keys before the change happened
– akira
May 19 '11 at 5:55
2
german are we? strg? Surely that must be ctrl!? :)
– Weezy
May 19 '11 at 15:22
well, brainiac, it states 'germany' at my profile quite clearly, so ... trivial to spot, even without whats printed on the keyboard.
– akira
May 19 '11 at 16:17
add a comment |
+1 too, same comment as for freethinker: how comes at first it works, then someone the xterm interprets a meta as not an escape anymore even though 5 seconds before that same xterm interpreted it as an escape?
– Weezy
May 18 '11 at 19:36
well, you can change things on-the-fly, may that be by accident or whatever: if alt stops working, check your xterm by pressing strg leftmouse and see if the option is ticked (just like @freethinker said). then investigate, if yout pressed some keys before the change happened
– akira
May 19 '11 at 5:55
2
german are we? strg? Surely that must be ctrl!? :)
– Weezy
May 19 '11 at 15:22
well, brainiac, it states 'germany' at my profile quite clearly, so ... trivial to spot, even without whats printed on the keyboard.
– akira
May 19 '11 at 16:17
+1 too, same comment as for freethinker: how comes at first it works, then someone the xterm interprets a meta as not an escape anymore even though 5 seconds before that same xterm interpreted it as an escape?
– Weezy
May 18 '11 at 19:36
+1 too, same comment as for freethinker: how comes at first it works, then someone the xterm interprets a meta as not an escape anymore even though 5 seconds before that same xterm interpreted it as an escape?
– Weezy
May 18 '11 at 19:36
well, you can change things on-the-fly, may that be by accident or whatever: if alt stops working, check your xterm by pressing strg leftmouse and see if the option is ticked (just like @freethinker said). then investigate, if yout pressed some keys before the change happened
– akira
May 19 '11 at 5:55
well, you can change things on-the-fly, may that be by accident or whatever: if alt stops working, check your xterm by pressing strg leftmouse and see if the option is ticked (just like @freethinker said). then investigate, if yout pressed some keys before the change happened
– akira
May 19 '11 at 5:55
2
2
german are we? strg? Surely that must be ctrl!? :)
– Weezy
May 19 '11 at 15:22
german are we? strg? Surely that must be ctrl!? :)
– Weezy
May 19 '11 at 15:22
well, brainiac, it states 'germany' at my profile quite clearly, so ... trivial to spot, even without whats printed on the keyboard.
– akira
May 19 '11 at 16:17
well, brainiac, it states 'germany' at my profile quite clearly, so ... trivial to spot, even without whats printed on the keyboard.
– akira
May 19 '11 at 16:17
add a comment |
I have the same problem here. Everything works fine on my local xterm on Debian. However, if I ssh into a RHEL server, m-b/m-f doesn't work. They still don't work even after I logged out from RHEL.
I digged the source code and find a hack, just add the following lines in your ~/.Xresources:
XTerm*VT100*Translations: #override n
Meta <KeyPress>:insert-seven-bit()
answered Feb 3 at 3:18
zhao tianleizhao tianlei
1
add a comment |
I have the same problem here. Everything works fine on my local xterm on Debian. However, if I ssh into a RHEL server, m-b/m-f doesn't work. They still don't work even after I logged out from RHEL.
I digged the source code and find a hack, just add the following lines in your ~/.Xresources:
XTerm*VT100*Translations: #override n
Meta <KeyPress>:insert-seven-bit()
answered Feb 3 at 3:18
zhao tianleizhao tianlei
1
add a comment |
I have the same problem here. Everything works fine on my local xterm on Debian. However, if I ssh into a RHEL server, m-b/m-f doesn't work. They still don't work even after I logged out from RHEL.
I digged the source code and find a hack, just add the following lines in your ~/.Xresources:
XTerm*VT100*Translations: #override n
Meta <KeyPress>:insert-seven-bit()
answered Feb 3 at 3:18
zhao tianleizhao tianlei
1
I have the same problem here. Everything works fine on my local xterm on Debian. However, if I ssh into a RHEL server, m-b/m-f doesn't work. They still don't work even after I logged out from RHEL.
I digged the source code and find a hack, just add the following lines in your ~/.Xresources:
XTerm*VT100*Translations: #override n
Meta <KeyPress>:insert-seven-bit()
answered Feb 3 at 3:18
zhao tianleizhao tianlei
1
answered Feb 3 at 3:18
zhao tianleizhao tianlei
1
answered Feb 3 at 3:18
zhao tianleizhao tianlei
1
answered Feb 3 at 3:18
zhao tianleizhao tianlei
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f285306%2falt-d-alt-f-etc-stops-working-in-my-xterm%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
