Ttyjfyk

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

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

share|improve this question

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;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
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @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
  

  
  
  
  

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

share|improve this question

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;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
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @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
  

  
  
  
  

add a comment | 

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

share|improve this question

edited 1 hour ago

ilkkachu

61k1098174

asked 2 hours ago

AdityaAditya

1083

export PS1="[33[00;32m][d T] [33[0;31m]u@H:[33[0;37m]w[$(tput sgr0)] n[33[0m]$ "

share|improve this question

edited 1 hour ago

ilkkachu

61k1098174

asked 2 hours ago

AdityaAditya

1083

share|improve this question

edited 1 hour ago

ilkkachu

61k1098174

asked 2 hours ago

AdityaAditya

1083

edited 1 hour ago

ilkkachu

61k1098174

edited 1 hour ago

ilkkachu

61k1098174

asked 2 hours ago

AdityaAditya

1083

asked 2 hours ago

AdityaAditya

1083