Line wrap broken after using PS12019 Community Moderator Electionbash PS1 setupUsing tput in $PS1 is breaking line wrappingHow to wrap bash commands after adding colorBash overwrites the first line when using custom PS1 promptUpdate 'changing' variables every time PS1 is called, i.e. every new promptTerminal doesn't wrap properlyTerminal prompt overwrites current linetmux not colorizing PS1 promptUsing echo -e in PS1 causes line break issues in shellLine wrap broken when PS1 contains a newline
Why does Captain Marvel assume the people on this planet know this?
In the late 1940’s to early 1950’s what technology was available that could melt a LOT of ice?
How do I express some one as a black person?
Why is there a voltage between the mains ground and my radiator?
What are actual Tesla M60 models used by AWS?
Why doesn't this Google Translate ad use the word "Translation" instead of "Translate"?
Why the color red for the Republican Party
Can a bounded number sequence be strictly ascending?
PTIJ: How can I halachically kill a vampire?
How to clip a background including nodes according to an arbitrary shape?
Force user to remove USB token
How can The Temple of Elementary Evil reliably protect itself against kinetic bombardment?
Tricky AM-GM inequality
Offered promotion but I'm leaving. Should I tell?
2000s TV show: people stuck in primitive other world, bit of magic and bit of dinosaurs
Accepted offer letter, position changed
Replacing Windows 7 security updates with anti-virus?
Do I really need to have a scientific explanation for my premise?
Try Catch Block Affecting a Variable in an Enclosing Scope
Algorithm to convert a fixed-length string to the smallest possible collision-free representation?
Is "history" a male-biased word ("his+story")?
Do items de-spawn in Diablo?
Why don't MCU characters ever seem to have language issues?
Examples of a statistic that is not independent of sample's distribution?
Line wrap broken after using PS1
2019 Community Moderator Electionbash PS1 setupUsing tput in $PS1 is breaking line wrappingHow to wrap bash commands after adding colorBash overwrites the first line when using custom PS1 promptUpdate 'changing' variables every time PS1 is called, i.e. every new promptTerminal doesn't wrap properlyTerminal prompt overwrites current linetmux not colorizing PS1 promptUsing echo -e in PS1 causes line break issues in shellLine wrap broken when PS1 contains a newline
0
The line wrap is working weirdly when I use the following PS1:
export PS1="[33[00;32m][d T] [33[0;31m]u@H:[33[0;37m]w[$(tput sgr0)] n[33[0m]$ "
It is line wrapping onto the same line. That too within 80 characters when my terminal supports way more than that on a single line.
bash prompt
edited 1 hour ago
ilkkachu
61k1098174
asked 2 hours ago
AdityaAditya
1083
add a comment |
0
The line wrap is working weirdly when I use the following PS1:
export PS1="[33[00;32m][d T] [33[0;31m]u@H:[33[0;37m]w[$(tput sgr0)] n[33[0m]$ "
It is line wrapping onto the same line. That too within 80 characters when my terminal supports way more than that on a single line.
bash prompt
edited 1 hour ago
ilkkachu
61k1098174
asked 2 hours ago
AdityaAditya
1083
line wrapping going wrong is usually a symptom of the shell counting the prompt length wrong, usually if the non-printing parts aren't wrapped in[ .. ]. But here they seem to be. And I can't even replicate the problem with the prompt you had in the question source (the way it looked in the question in the original version was wrong, the post formatting ate backslashes from the[escapes)
– ilkkachu
1 hour ago
Just curious: why use[00;32minstead of$(tput setaf 2)? Sometimes, people avoid callingtputbecause they don't want it to be invoked each time the prompt is generated, but the way you've constructed your assignment it would only be called when PS1 is initially assigned, so falling back on the explicit assignment seems to have no benefit.
– William Pursell
1 hour ago
@WilliamPursell I copy pasted the segements from random sites I found using Google search :) I have no clue what any of this means.
– Aditya
1 hour ago
@ilkkachu, so this is on my work pc. I am guessing that when they created my account they might have put some PS1 variable or some thing else that might create a problem in a different RC file. Right now I am looking at ~/.bashrc. Are there any other files I should check for conflicts?
– Aditya
1 hour ago
@Aditya, well, you need to look at the value thatPS1finally gets set to. That's often~/.bashrc, but I set mine in~/.profile. You can useprintf "%sn" "$PS1"to see the valuePS1actually has. (Or just putPS1='foo$ 'in your.bashrc, and see if it sticks. If not, then some other file sets it.) Bash's setup of startup files is a bit complicated and more so since often some of the files are made to call other files.
– ilkkachu
1 hour ago
add a comment |
0
0
0
The line wrap is working weirdly when I use the following PS1:
export PS1="[33[00;32m][d T] [33[0;31m]u@H:[33[0;37m]w[$(tput sgr0)] n[33[0m]$ "
It is line wrapping onto the same line. That too within 80 characters when my terminal supports way more than that on a single line.
bash prompt
edited 1 hour ago
ilkkachu
61k1098174
asked 2 hours ago
AdityaAditya
1083
The line wrap is working weirdly when I use the following PS1:
export PS1="[33[00;32m][d T] [33[0;31m]u@H:[33[0;37m]w[$(tput sgr0)] n[33[0m]$ "
It is line wrapping onto the same line. That too within 80 characters when my terminal supports way more than that on a single line.
bash prompt
bash prompt
edited 1 hour ago
ilkkachu
61k1098174
asked 2 hours ago
AdityaAditya
1083
edited 1 hour ago
ilkkachu
61k1098174
asked 2 hours ago
AdityaAditya
1083
edited 1 hour ago
ilkkachu
61k1098174
edited 1 hour ago
ilkkachu
61k1098174
edited 1 hour ago
ilkkachu
61k1098174
61k1098174
asked 2 hours ago
AdityaAditya
1083
asked 2 hours ago
AdityaAditya
1083
asked 2 hours ago
AdityaAditya
1083
1083
line wrapping going wrong is usually a symptom of the shell counting the prompt length wrong, usually if the non-printing parts aren't wrapped in[ .. ]. But here they seem to be. And I can't even replicate the problem with the prompt you had in the question source (the way it looked in the question in the original version was wrong, the post formatting ate backslashes from the[escapes)
– ilkkachu
1 hour ago
Just curious: why use[00;32minstead of$(tput setaf 2)? Sometimes, people avoid callingtputbecause they don't want it to be invoked each time the prompt is generated, but the way you've constructed your assignment it would only be called when PS1 is initially assigned, so falling back on the explicit assignment seems to have no benefit.
– William Pursell
1 hour ago
@WilliamPursell I copy pasted the segements from random sites I found using Google search :) I have no clue what any of this means.
– Aditya
1 hour ago
@ilkkachu, so this is on my work pc. I am guessing that when they created my account they might have put some PS1 variable or some thing else that might create a problem in a different RC file. Right now I am looking at ~/.bashrc. Are there any other files I should check for conflicts?
– Aditya
1 hour ago
@Aditya, well, you need to look at the value thatPS1finally gets set to. That's often~/.bashrc, but I set mine in~/.profile. You can useprintf "%sn" "$PS1"to see the valuePS1actually has. (Or just putPS1='foo$ 'in your.bashrc, and see if it sticks. If not, then some other file sets it.) Bash's setup of startup files is a bit complicated and more so since often some of the files are made to call other files.
– ilkkachu
1 hour ago
add a comment |
line wrapping going wrong is usually a symptom of the shell counting the prompt length wrong, usually if the non-printing parts aren't wrapped in[ .. ]. But here they seem to be. And I can't even replicate the problem with the prompt you had in the question source (the way it looked in the question in the original version was wrong, the post formatting ate backslashes from the[escapes)
– ilkkachu
1 hour ago
Just curious: why use[00;32minstead of$(tput setaf 2)? Sometimes, people avoid callingtputbecause they don't want it to be invoked each time the prompt is generated, but the way you've constructed your assignment it would only be called when PS1 is initially assigned, so falling back on the explicit assignment seems to have no benefit.
– William Pursell
1 hour ago
@WilliamPursell I copy pasted the segements from random sites I found using Google search :) I have no clue what any of this means.
– Aditya
1 hour ago
@ilkkachu, so this is on my work pc. I am guessing that when they created my account they might have put some PS1 variable or some thing else that might create a problem in a different RC file. Right now I am looking at ~/.bashrc. Are there any other files I should check for conflicts?
– Aditya
1 hour ago
@Aditya, well, you need to look at the value thatPS1finally gets set to. That's often~/.bashrc, but I set mine in~/.profile. You can useprintf "%sn" "$PS1"to see the valuePS1actually has. (Or just putPS1='foo$ 'in your.bashrc, and see if it sticks. If not, then some other file sets it.) Bash's setup of startup files is a bit complicated and more so since often some of the files are made to call other files.
– ilkkachu
1 hour ago
line wrapping going wrong is usually a symptom of the shell counting the prompt length wrong, usually if the non-printing parts aren't wrapped in
[ .. ]. But here they seem to be. And I can't even replicate the problem with the prompt you had in the question source (the way it looked in the question in the original version was wrong, the post formatting ate backslashes from the [ escapes)– ilkkachu
1 hour ago
line wrapping going wrong is usually a symptom of the shell counting the prompt length wrong, usually if the non-printing parts aren't wrapped in
[ .. ]. But here they seem to be. And I can't even replicate the problem with the prompt you had in the question source (the way it looked in the question in the original version was wrong, the post formatting ate backslashes from the [ escapes)– ilkkachu
1 hour ago
Just curious: why use
[00;32m instead of $(tput setaf 2)? Sometimes, people avoid calling tput because they don't want it to be invoked each time the prompt is generated, but the way you've constructed your assignment it would only be called when PS1 is initially assigned, so falling back on the explicit assignment seems to have no benefit.– William Pursell
1 hour ago
Just curious: why use
[00;32m instead of $(tput setaf 2)? Sometimes, people avoid calling tput because they don't want it to be invoked each time the prompt is generated, but the way you've constructed your assignment it would only be called when PS1 is initially assigned, so falling back on the explicit assignment seems to have no benefit.– William Pursell
1 hour ago
@WilliamPursell I copy pasted the segements from random sites I found using Google search :) I have no clue what any of this means.
– Aditya
1 hour ago
@WilliamPursell I copy pasted the segements from random sites I found using Google search :) I have no clue what any of this means.
– Aditya
1 hour ago
@ilkkachu, so this is on my work pc. I am guessing that when they created my account they might have put some PS1 variable or some thing else that might create a problem in a different RC file. Right now I am looking at ~/.bashrc. Are there any other files I should check for conflicts?
– Aditya
1 hour ago
@ilkkachu, so this is on my work pc. I am guessing that when they created my account they might have put some PS1 variable or some thing else that might create a problem in a different RC file. Right now I am looking at ~/.bashrc. Are there any other files I should check for conflicts?
– Aditya
1 hour ago
@Aditya, well, you need to look at the value that
PS1 finally gets set to. That's often ~/.bashrc, but I set mine in ~/.profile. You can use printf "%sn" "$PS1" to see the value PS1 actually has. (Or just put PS1='foo$ ' in your .bashrc, and see if it sticks. If not, then some other file sets it.) Bash's setup of startup files is a bit complicated and more so since often some of the files are made to call other files.– ilkkachu
1 hour ago
@Aditya, well, you need to look at the value that
PS1 finally gets set to. That's often ~/.bashrc, but I set mine in ~/.profile. You can use printf "%sn" "$PS1" to see the value PS1 actually has. (Or just put PS1='foo$ ' in your .bashrc, and see if it sticks. If not, then some other file sets it.) Bash's setup of startup files is a bit complicated and more so since often some of the files are made to call other files.– ilkkachu
1 hour ago
add a comment |
0
active
oldest
votes
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
);
);
draft saved
draft discarded
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%2f505903%2fline-wrap-broken-after-using-ps1%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f505903%2fline-wrap-broken-after-using-ps1%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
-bash, prompt
line wrapping going wrong is usually a symptom of the shell counting the prompt length wrong, usually if the non-printing parts aren't wrapped in
[ .. ]. But here they seem to be. And I can't even replicate the problem with the prompt you had in the question source (the way it looked in the question in the original version was wrong, the post formatting ate backslashes from the[escapes)– ilkkachu
1 hour ago
Just curious: why use
[00;32minstead of$(tput setaf 2)? Sometimes, people avoid callingtputbecause they don't want it to be invoked each time the prompt is generated, but the way you've constructed your assignment it would only be called when PS1 is initially assigned, so falling back on the explicit assignment seems to have no benefit.– William Pursell
1 hour ago
@WilliamPursell I copy pasted the segements from random sites I found using Google search :) I have no clue what any of this means.
– Aditya
1 hour ago
@ilkkachu, so this is on my work pc. I am guessing that when they created my account they might have put some PS1 variable or some thing else that might create a problem in a different RC file. Right now I am looking at ~/.bashrc. Are there any other files I should check for conflicts?
– Aditya
1 hour ago
@Aditya, well, you need to look at the value that
PS1finally gets set to. That's often~/.bashrc, but I set mine in~/.profile. You can useprintf "%sn" "$PS1"to see the valuePS1actually has. (Or just putPS1='foo$ 'in your.bashrc, and see if it sticks. If not, then some other file sets it.) Bash's setup of startup files is a bit complicated and more so since often some of the files are made to call other files.– ilkkachu
1 hour ago