Fixing historical command-line corruption from PS1 escape sequence
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I (believe) I am having an issue with the following PS1 not properly having an escape sequence:
x1b[35mabcx1b[0m x1b[33mxyzx1b[0m x1b[34mwx1b[0m$
The prompt looks okay until I begin to use historical command-lines and then bash seems to lose where the start of the line is. I thought that this stack overflow question would help, but I really don't know where my escape sequence is missing. Is it that I'm missing closing brackets? Also, I'm a little confused why I have x1b instead of .
Please help!
bash corruption ps1
asked Nov 22 '18 at 0:30
Brian BruggemanBrian Bruggeman
2,21112030
add a comment |
I (believe) I am having an issue with the following PS1 not properly having an escape sequence:
x1b[35mabcx1b[0m x1b[33mxyzx1b[0m x1b[34mwx1b[0m$
The prompt looks okay until I begin to use historical command-lines and then bash seems to lose where the start of the line is. I thought that this stack overflow question would help, but I really don't know where my escape sequence is missing. Is it that I'm missing closing brackets? Also, I'm a little confused why I have x1b instead of .
Please help!
bash corruption ps1
asked Nov 22 '18 at 0:30
Brian BruggemanBrian Bruggeman
2,21112030
add a comment |
I (believe) I am having an issue with the following PS1 not properly having an escape sequence:
x1b[35mabcx1b[0m x1b[33mxyzx1b[0m x1b[34mwx1b[0m$
The prompt looks okay until I begin to use historical command-lines and then bash seems to lose where the start of the line is. I thought that this stack overflow question would help, but I really don't know where my escape sequence is missing. Is it that I'm missing closing brackets? Also, I'm a little confused why I have x1b instead of .
Please help!
bash corruption ps1
asked Nov 22 '18 at 0:30
Brian BruggemanBrian Bruggeman
2,21112030
I (believe) I am having an issue with the following PS1 not properly having an escape sequence:
x1b[35mabcx1b[0m x1b[33mxyzx1b[0m x1b[34mwx1b[0m$
The prompt looks okay until I begin to use historical command-lines and then bash seems to lose where the start of the line is. I thought that this stack overflow question would help, but I really don't know where my escape sequence is missing. Is it that I'm missing closing brackets? Also, I'm a little confused why I have x1b instead of .
Please help!
bash corruption ps1
bash corruption ps1
asked Nov 22 '18 at 0:30
Brian BruggemanBrian Bruggeman
2,21112030
asked Nov 22 '18 at 0:30
Brian BruggemanBrian Bruggeman
2,21112030
edited Nov 22 '18 at 0:43
Brian Bruggeman
asked Nov 22 '18 at 0:30
Brian BruggemanBrian Bruggeman
2,21112030
asked Nov 22 '18 at 0:30
Brian BruggemanBrian Bruggeman
2,21112030
asked Nov 22 '18 at 0:30
Brian BruggemanBrian Bruggeman
2,21112030
2,21112030
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You're missing the brackets comletely (both opening and closing). Try using
\[x1b[35m\]abc\[x1b[0m\] \[x1b[33m\]xyz\[x1b[0m\] \[x1b[34m\]w\[x1b[0m\]$
That is, put \[ and \] around every escape sequence in the prompt.
My personal solution is to use a two-line prompt (so there's a n in PS1) where the second line is short and has no escapes. So bash has no trouble figuring out how wide it is:
PS1='33[0;31m[h${debian_chroot:+($debian_chroot)}] 33[0;32m[u] 33[0;33m[w$(__git_ps1 " (%s)")]33[0;39mn --> '
answered Nov 22 '18 at 0:36
Chris DoddChris Dodd
82.4k782162
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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%2fstackoverflow.com%2fquestions%2f53422316%2ffixing-historical-command-line-corruption-from-ps1-escape-sequence%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
You're missing the brackets comletely (both opening and closing). Try using
\[x1b[35m\]abc\[x1b[0m\] \[x1b[33m\]xyz\[x1b[0m\] \[x1b[34m\]w\[x1b[0m\]$
That is, put \[ and \] around every escape sequence in the prompt.
My personal solution is to use a two-line prompt (so there's a n in PS1) where the second line is short and has no escapes. So bash has no trouble figuring out how wide it is:
PS1='33[0;31m[h${debian_chroot:+($debian_chroot)}] 33[0;32m[u] 33[0;33m[w$(__git_ps1 " (%s)")]33[0;39mn --> '
answered Nov 22 '18 at 0:36
Chris DoddChris Dodd
82.4k782162
add a comment |
You're missing the brackets comletely (both opening and closing). Try using
\[x1b[35m\]abc\[x1b[0m\] \[x1b[33m\]xyz\[x1b[0m\] \[x1b[34m\]w\[x1b[0m\]$
That is, put \[ and \] around every escape sequence in the prompt.
My personal solution is to use a two-line prompt (so there's a n in PS1) where the second line is short and has no escapes. So bash has no trouble figuring out how wide it is:
PS1='33[0;31m[h${debian_chroot:+($debian_chroot)}] 33[0;32m[u] 33[0;33m[w$(__git_ps1 " (%s)")]33[0;39mn --> '
answered Nov 22 '18 at 0:36
Chris DoddChris Dodd
82.4k782162
add a comment |
You're missing the brackets comletely (both opening and closing). Try using
\[x1b[35m\]abc\[x1b[0m\] \[x1b[33m\]xyz\[x1b[0m\] \[x1b[34m\]w\[x1b[0m\]$
That is, put \[ and \] around every escape sequence in the prompt.
My personal solution is to use a two-line prompt (so there's a n in PS1) where the second line is short and has no escapes. So bash has no trouble figuring out how wide it is:
PS1='33[0;31m[h${debian_chroot:+($debian_chroot)}] 33[0;32m[u] 33[0;33m[w$(__git_ps1 " (%s)")]33[0;39mn --> '
answered Nov 22 '18 at 0:36
Chris DoddChris Dodd
82.4k782162
You're missing the brackets comletely (both opening and closing). Try using
\[x1b[35m\]abc\[x1b[0m\] \[x1b[33m\]xyz\[x1b[0m\] \[x1b[34m\]w\[x1b[0m\]$
That is, put \[ and \] around every escape sequence in the prompt.
My personal solution is to use a two-line prompt (so there's a n in PS1) where the second line is short and has no escapes. So bash has no trouble figuring out how wide it is:
PS1='33[0;31m[h${debian_chroot:+($debian_chroot)}] 33[0;32m[u] 33[0;33m[w$(__git_ps1 " (%s)")]33[0;39mn --> '
answered Nov 22 '18 at 0:36
Chris DoddChris Dodd
82.4k782162
answered Nov 22 '18 at 0:36
Chris DoddChris Dodd
82.4k782162
answered Nov 22 '18 at 0:36
Chris DoddChris Dodd
82.4k782162
answered Nov 22 '18 at 0:36
Chris DoddChris Dodd
82.4k782162
82.4k782162
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f53422316%2ffixing-historical-command-line-corruption-from-ps1-escape-sequence%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
