No line breaks in first line in terminal The 2019 Stack Overflow Developer Survey Results Are...

Difference between "generating set" and free product?

How to split my screen on my Macbook Air?

Didn't get enough time to take a Coding Test - what to do now?

system() function string length limit

How to test the equality of two Pearson correlation coefficients computed from the same sample?

Segmentation fault output is suppressed when piping stdin into a function. Why?

Is this wall load bearing? Blueprints and photos attached

Windows 10: How to Lock (not sleep) laptop on lid close?

What is this lever in Argentinian toilets?

What information about me do stores get via my credit card?

Why can't wing-mounted spoilers be used to steepen approaches?

How can I define good in a religion that claims no moral authority?

Does Parliament hold absolute power in the UK?

How to politely respond to generic emails requesting a PhD/job in my lab? Without wasting too much time

Match Roman Numerals

Why does the Event Horizon Telescope (EHT) not include telescopes from Africa, Asia or Australia?

How do you keep chess fun when your opponent constantly beats you?

What can I do if neighbor is blocking my solar panels intentionally?

Can the prologue be the backstory of your main character?

Can the DM override racial traits?

Am I ethically obligated to go into work on an off day if the reason is sudden?

I could not break this equation. Please help me

Wall plug outlet change

Is above average number of years spent on PhD considered a red flag in future academia or industry positions?



No line breaks in first line in terminal



The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)gnome-terminal hides ending characters of the current path's first rowgnome-terminal hides ending characters of the current path's first row. (This question is for Ubuntu-18.04 users who are using original files)Remove terminal first messageLine gets overwritten instead of continuing on same lineReuse last line on terminalBash script to remove line breaks?Merging Home Directories Breaks Readline/.bashrc.bashrc shebang line reports command not foundWhat does the first '.' mean in '. ~/.bashrc'?Deleting first letter of each lineProblematic line breaks in bashClearing terminal screen





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







3















I've modified my Ubuntu 17.10 system to make it look like macOS. Now I'm confused about how my terminal behaves. Line breaks do not appear correctly. This video shows what I mean.



The modified file is ~/.bashrc. These are the new contents of that file:



# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything
case $- in
*i*) ;;
*) return;;
esac

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar

# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color|*-256color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi

if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}[33[01;32m]u@h[33[00m]:[33[01;34m]w[33[00m]$ '
else
PS1='${debian_chroot:+($debian_chroot)}u@h:w$ '
fi
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PS1="[e]0;${debian_chroot:+($debian_chroot)}u@h: wa]$PS1"
;;
*)
;;
esac

# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'

alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'
fi

# colored GCC warnings and errors
#export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'

# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'

# Add an "alert" alias for long running commands. Use like so:
# sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '''s/^s*[0-9]+s*//;s/[;&|]s*alert$//''')"'

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.

if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
if [ -f /usr/share/bash-completion/bash_completion ]; then
. /usr/share/bash-completion/bash_completion
elif [ -f /etc/bash_completion ]; then
. /etc/bash_completion
fi
fi

### Prompt style
export PS1="33[0;33mh:W u$ e[m"


I hope someone can understand and help with my problem.










share|improve this question

























  • Is the problem that, when you press Enter, the cursor returns to the beginning of the same line (so then when you type, you type over what was on that line before), instead of advancing to the beginning of the next line? Also, can you give details about the changes you made before the problem started? Also, if you run XTerm (type xterm in the Run... dialog, which in most desktop environments you get with Alt+F2; or just type xterm in your terminal), does it have the same problem? I recommend that you edit your question to include as much of this information as possible. Thanks!

    – Eliah Kagan
    Apr 1 '18 at 4:12











  • I've posted an answer. If pressing Enter triggers the undesired behavior to occur, as I guessed in my earlier comment, then I don't think I've fully explained your problem, but I suspect the solution I have given there will still work. Furthermore, I just watched your video a second time, and it seems to me that you may not actually be pressing Enter--you might simply be wrapping around to the beginning of the same line. If so, then the problem is fully explained.

    – Eliah Kagan
    Apr 1 '18 at 5:13


















3















I've modified my Ubuntu 17.10 system to make it look like macOS. Now I'm confused about how my terminal behaves. Line breaks do not appear correctly. This video shows what I mean.



The modified file is ~/.bashrc. These are the new contents of that file:



# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything
case $- in
*i*) ;;
*) return;;
esac

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar

# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color|*-256color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi

if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}[33[01;32m]u@h[33[00m]:[33[01;34m]w[33[00m]$ '
else
PS1='${debian_chroot:+($debian_chroot)}u@h:w$ '
fi
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PS1="[e]0;${debian_chroot:+($debian_chroot)}u@h: wa]$PS1"
;;
*)
;;
esac

# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'

alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'
fi

# colored GCC warnings and errors
#export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'

# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'

# Add an "alert" alias for long running commands. Use like so:
# sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '''s/^s*[0-9]+s*//;s/[;&|]s*alert$//''')"'

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.

if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
if [ -f /usr/share/bash-completion/bash_completion ]; then
. /usr/share/bash-completion/bash_completion
elif [ -f /etc/bash_completion ]; then
. /etc/bash_completion
fi
fi

### Prompt style
export PS1="33[0;33mh:W u$ e[m"


I hope someone can understand and help with my problem.










share|improve this question

























  • Is the problem that, when you press Enter, the cursor returns to the beginning of the same line (so then when you type, you type over what was on that line before), instead of advancing to the beginning of the next line? Also, can you give details about the changes you made before the problem started? Also, if you run XTerm (type xterm in the Run... dialog, which in most desktop environments you get with Alt+F2; or just type xterm in your terminal), does it have the same problem? I recommend that you edit your question to include as much of this information as possible. Thanks!

    – Eliah Kagan
    Apr 1 '18 at 4:12











  • I've posted an answer. If pressing Enter triggers the undesired behavior to occur, as I guessed in my earlier comment, then I don't think I've fully explained your problem, but I suspect the solution I have given there will still work. Furthermore, I just watched your video a second time, and it seems to me that you may not actually be pressing Enter--you might simply be wrapping around to the beginning of the same line. If so, then the problem is fully explained.

    – Eliah Kagan
    Apr 1 '18 at 5:13














3












3








3


1






I've modified my Ubuntu 17.10 system to make it look like macOS. Now I'm confused about how my terminal behaves. Line breaks do not appear correctly. This video shows what I mean.



The modified file is ~/.bashrc. These are the new contents of that file:



# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything
case $- in
*i*) ;;
*) return;;
esac

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar

# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color|*-256color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi

if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}[33[01;32m]u@h[33[00m]:[33[01;34m]w[33[00m]$ '
else
PS1='${debian_chroot:+($debian_chroot)}u@h:w$ '
fi
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PS1="[e]0;${debian_chroot:+($debian_chroot)}u@h: wa]$PS1"
;;
*)
;;
esac

# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'

alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'
fi

# colored GCC warnings and errors
#export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'

# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'

# Add an "alert" alias for long running commands. Use like so:
# sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '''s/^s*[0-9]+s*//;s/[;&|]s*alert$//''')"'

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.

if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
if [ -f /usr/share/bash-completion/bash_completion ]; then
. /usr/share/bash-completion/bash_completion
elif [ -f /etc/bash_completion ]; then
. /etc/bash_completion
fi
fi

### Prompt style
export PS1="33[0;33mh:W u$ e[m"


I hope someone can understand and help with my problem.










share|improve this question
















I've modified my Ubuntu 17.10 system to make it look like macOS. Now I'm confused about how my terminal behaves. Line breaks do not appear correctly. This video shows what I mean.



The modified file is ~/.bashrc. These are the new contents of that file:



# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything
case $- in
*i*) ;;
*) return;;
esac

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar

# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color|*-256color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi

if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}[33[01;32m]u@h[33[00m]:[33[01;34m]w[33[00m]$ '
else
PS1='${debian_chroot:+($debian_chroot)}u@h:w$ '
fi
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PS1="[e]0;${debian_chroot:+($debian_chroot)}u@h: wa]$PS1"
;;
*)
;;
esac

# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'

alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'
fi

# colored GCC warnings and errors
#export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'

# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'

# Add an "alert" alias for long running commands. Use like so:
# sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '''s/^s*[0-9]+s*//;s/[;&|]s*alert$//''')"'

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.

if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
if [ -f /usr/share/bash-completion/bash_completion ]; then
. /usr/share/bash-completion/bash_completion
elif [ -f /etc/bash_completion ]; then
. /etc/bash_completion
fi
fi

### Prompt style
export PS1="33[0;33mh:W u$ e[m"


I hope someone can understand and help with my problem.







command-line bash bashrc macbuntu






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 10 mins ago









Zanna

51.4k13140243




51.4k13140243










asked Apr 1 '18 at 4:00









Aryamaulana WibisonoAryamaulana Wibisono

2618




2618













  • Is the problem that, when you press Enter, the cursor returns to the beginning of the same line (so then when you type, you type over what was on that line before), instead of advancing to the beginning of the next line? Also, can you give details about the changes you made before the problem started? Also, if you run XTerm (type xterm in the Run... dialog, which in most desktop environments you get with Alt+F2; or just type xterm in your terminal), does it have the same problem? I recommend that you edit your question to include as much of this information as possible. Thanks!

    – Eliah Kagan
    Apr 1 '18 at 4:12











  • I've posted an answer. If pressing Enter triggers the undesired behavior to occur, as I guessed in my earlier comment, then I don't think I've fully explained your problem, but I suspect the solution I have given there will still work. Furthermore, I just watched your video a second time, and it seems to me that you may not actually be pressing Enter--you might simply be wrapping around to the beginning of the same line. If so, then the problem is fully explained.

    – Eliah Kagan
    Apr 1 '18 at 5:13



















  • Is the problem that, when you press Enter, the cursor returns to the beginning of the same line (so then when you type, you type over what was on that line before), instead of advancing to the beginning of the next line? Also, can you give details about the changes you made before the problem started? Also, if you run XTerm (type xterm in the Run... dialog, which in most desktop environments you get with Alt+F2; or just type xterm in your terminal), does it have the same problem? I recommend that you edit your question to include as much of this information as possible. Thanks!

    – Eliah Kagan
    Apr 1 '18 at 4:12











  • I've posted an answer. If pressing Enter triggers the undesired behavior to occur, as I guessed in my earlier comment, then I don't think I've fully explained your problem, but I suspect the solution I have given there will still work. Furthermore, I just watched your video a second time, and it seems to me that you may not actually be pressing Enter--you might simply be wrapping around to the beginning of the same line. If so, then the problem is fully explained.

    – Eliah Kagan
    Apr 1 '18 at 5:13

















Is the problem that, when you press Enter, the cursor returns to the beginning of the same line (so then when you type, you type over what was on that line before), instead of advancing to the beginning of the next line? Also, can you give details about the changes you made before the problem started? Also, if you run XTerm (type xterm in the Run... dialog, which in most desktop environments you get with Alt+F2; or just type xterm in your terminal), does it have the same problem? I recommend that you edit your question to include as much of this information as possible. Thanks!

– Eliah Kagan
Apr 1 '18 at 4:12





Is the problem that, when you press Enter, the cursor returns to the beginning of the same line (so then when you type, you type over what was on that line before), instead of advancing to the beginning of the next line? Also, can you give details about the changes you made before the problem started? Also, if you run XTerm (type xterm in the Run... dialog, which in most desktop environments you get with Alt+F2; or just type xterm in your terminal), does it have the same problem? I recommend that you edit your question to include as much of this information as possible. Thanks!

– Eliah Kagan
Apr 1 '18 at 4:12













I've posted an answer. If pressing Enter triggers the undesired behavior to occur, as I guessed in my earlier comment, then I don't think I've fully explained your problem, but I suspect the solution I have given there will still work. Furthermore, I just watched your video a second time, and it seems to me that you may not actually be pressing Enter--you might simply be wrapping around to the beginning of the same line. If so, then the problem is fully explained.

– Eliah Kagan
Apr 1 '18 at 5:13





I've posted an answer. If pressing Enter triggers the undesired behavior to occur, as I guessed in my earlier comment, then I don't think I've fully explained your problem, but I suspect the solution I have given there will still work. Furthermore, I just watched your video a second time, and it seems to me that you may not actually be pressing Enter--you might simply be wrapping around to the beginning of the same line. If so, then the problem is fully explained.

– Eliah Kagan
Apr 1 '18 at 5:13










1 Answer
1






active

oldest

votes


















5














It appears that you have added this to the end of the .bashrc file in your home directory:



export PS1="33[0;33mh:W u$ e[m"


You should use this instead:



export PS1="[33[0;33m]h:W u$ [e[m]"


That is, surround escape sequences that tell the terminal how to display text (in this case, that perform colorization) with [ and ]. This tells the Bash shell that they are not supposed to be counted when the number of visible characters you have entered is determined. (See also this question and that one.)



It's rarely useful to actually export PS1, by the way. Every newly run interactive Bash shell that should use your prompt will read from .bashrc and set the prompt for itself. Therefore I recommend omitting export and just using this line:



PS1="[33[0;33m]h:W u$ [e[m]"




Although that was the only part of your .bashrc where I noticed a problem, you may want to compare the file with the "original":



diff /etc/skel/.bashrc ~/.bashrc


That shows changes compared to the .bashrc file that would be created for a new user on your system. Usually that has the effect of showing just your own changes, but sometimes /etc/skel/.bashrc changes between Ubuntu releases, so if your user account was created prior to an upgrade, then there may be other changes. Note that not everything this shows is an error! But those are the parts that I recommend you inspect.



(You can include the output of that diff command in your question if you are not sure how to interpret it or if a particular changed line contains anything that ought to be written differently.)



Finally, although I suspect this will completely solve your problem, I should mention that usually the behavior when you press Enter is not actually affected by this. More commonly, omitting [ and ] just causes the shell to fail to wrap your lines, so that if you type something longer than the width of the terminal, it goes back to the beginning of the same line.






share|improve this answer
























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    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
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1020980%2fno-line-breaks-in-first-line-in-terminal%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









    5














    It appears that you have added this to the end of the .bashrc file in your home directory:



    export PS1="33[0;33mh:W u$ e[m"


    You should use this instead:



    export PS1="[33[0;33m]h:W u$ [e[m]"


    That is, surround escape sequences that tell the terminal how to display text (in this case, that perform colorization) with [ and ]. This tells the Bash shell that they are not supposed to be counted when the number of visible characters you have entered is determined. (See also this question and that one.)



    It's rarely useful to actually export PS1, by the way. Every newly run interactive Bash shell that should use your prompt will read from .bashrc and set the prompt for itself. Therefore I recommend omitting export and just using this line:



    PS1="[33[0;33m]h:W u$ [e[m]"




    Although that was the only part of your .bashrc where I noticed a problem, you may want to compare the file with the "original":



    diff /etc/skel/.bashrc ~/.bashrc


    That shows changes compared to the .bashrc file that would be created for a new user on your system. Usually that has the effect of showing just your own changes, but sometimes /etc/skel/.bashrc changes between Ubuntu releases, so if your user account was created prior to an upgrade, then there may be other changes. Note that not everything this shows is an error! But those are the parts that I recommend you inspect.



    (You can include the output of that diff command in your question if you are not sure how to interpret it or if a particular changed line contains anything that ought to be written differently.)



    Finally, although I suspect this will completely solve your problem, I should mention that usually the behavior when you press Enter is not actually affected by this. More commonly, omitting [ and ] just causes the shell to fail to wrap your lines, so that if you type something longer than the width of the terminal, it goes back to the beginning of the same line.






    share|improve this answer




























      5














      It appears that you have added this to the end of the .bashrc file in your home directory:



      export PS1="33[0;33mh:W u$ e[m"


      You should use this instead:



      export PS1="[33[0;33m]h:W u$ [e[m]"


      That is, surround escape sequences that tell the terminal how to display text (in this case, that perform colorization) with [ and ]. This tells the Bash shell that they are not supposed to be counted when the number of visible characters you have entered is determined. (See also this question and that one.)



      It's rarely useful to actually export PS1, by the way. Every newly run interactive Bash shell that should use your prompt will read from .bashrc and set the prompt for itself. Therefore I recommend omitting export and just using this line:



      PS1="[33[0;33m]h:W u$ [e[m]"




      Although that was the only part of your .bashrc where I noticed a problem, you may want to compare the file with the "original":



      diff /etc/skel/.bashrc ~/.bashrc


      That shows changes compared to the .bashrc file that would be created for a new user on your system. Usually that has the effect of showing just your own changes, but sometimes /etc/skel/.bashrc changes between Ubuntu releases, so if your user account was created prior to an upgrade, then there may be other changes. Note that not everything this shows is an error! But those are the parts that I recommend you inspect.



      (You can include the output of that diff command in your question if you are not sure how to interpret it or if a particular changed line contains anything that ought to be written differently.)



      Finally, although I suspect this will completely solve your problem, I should mention that usually the behavior when you press Enter is not actually affected by this. More commonly, omitting [ and ] just causes the shell to fail to wrap your lines, so that if you type something longer than the width of the terminal, it goes back to the beginning of the same line.






      share|improve this answer


























        5












        5








        5







        It appears that you have added this to the end of the .bashrc file in your home directory:



        export PS1="33[0;33mh:W u$ e[m"


        You should use this instead:



        export PS1="[33[0;33m]h:W u$ [e[m]"


        That is, surround escape sequences that tell the terminal how to display text (in this case, that perform colorization) with [ and ]. This tells the Bash shell that they are not supposed to be counted when the number of visible characters you have entered is determined. (See also this question and that one.)



        It's rarely useful to actually export PS1, by the way. Every newly run interactive Bash shell that should use your prompt will read from .bashrc and set the prompt for itself. Therefore I recommend omitting export and just using this line:



        PS1="[33[0;33m]h:W u$ [e[m]"




        Although that was the only part of your .bashrc where I noticed a problem, you may want to compare the file with the "original":



        diff /etc/skel/.bashrc ~/.bashrc


        That shows changes compared to the .bashrc file that would be created for a new user on your system. Usually that has the effect of showing just your own changes, but sometimes /etc/skel/.bashrc changes between Ubuntu releases, so if your user account was created prior to an upgrade, then there may be other changes. Note that not everything this shows is an error! But those are the parts that I recommend you inspect.



        (You can include the output of that diff command in your question if you are not sure how to interpret it or if a particular changed line contains anything that ought to be written differently.)



        Finally, although I suspect this will completely solve your problem, I should mention that usually the behavior when you press Enter is not actually affected by this. More commonly, omitting [ and ] just causes the shell to fail to wrap your lines, so that if you type something longer than the width of the terminal, it goes back to the beginning of the same line.






        share|improve this answer













        It appears that you have added this to the end of the .bashrc file in your home directory:



        export PS1="33[0;33mh:W u$ e[m"


        You should use this instead:



        export PS1="[33[0;33m]h:W u$ [e[m]"


        That is, surround escape sequences that tell the terminal how to display text (in this case, that perform colorization) with [ and ]. This tells the Bash shell that they are not supposed to be counted when the number of visible characters you have entered is determined. (See also this question and that one.)



        It's rarely useful to actually export PS1, by the way. Every newly run interactive Bash shell that should use your prompt will read from .bashrc and set the prompt for itself. Therefore I recommend omitting export and just using this line:



        PS1="[33[0;33m]h:W u$ [e[m]"




        Although that was the only part of your .bashrc where I noticed a problem, you may want to compare the file with the "original":



        diff /etc/skel/.bashrc ~/.bashrc


        That shows changes compared to the .bashrc file that would be created for a new user on your system. Usually that has the effect of showing just your own changes, but sometimes /etc/skel/.bashrc changes between Ubuntu releases, so if your user account was created prior to an upgrade, then there may be other changes. Note that not everything this shows is an error! But those are the parts that I recommend you inspect.



        (You can include the output of that diff command in your question if you are not sure how to interpret it or if a particular changed line contains anything that ought to be written differently.)



        Finally, although I suspect this will completely solve your problem, I should mention that usually the behavior when you press Enter is not actually affected by this. More commonly, omitting [ and ] just causes the shell to fail to wrap your lines, so that if you type something longer than the width of the terminal, it goes back to the beginning of the same line.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Apr 1 '18 at 5:09









        Eliah KaganEliah Kagan

        83.3k22229369




        83.3k22229369






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • 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














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1020980%2fno-line-breaks-in-first-line-in-terminal%23new-answer', 'question_page');
            }
            );

            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







            Popular posts from this blog

            Why do type traits not work with types in namespace scope?What are POD types in C++?Why can templates only be...

            Will tsunami waves travel forever if there was no land?Why do tsunami waves begin with the water flowing away...

            Should I use Docker or LXD?How to cache (more) data on SSD/RAM to avoid spin up?Unable to get Windows File...