Databases
StackOverflow2013
Postsdbo
PO.bashrc break, second line entered in shell eats up first line
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO.bashrc break, second line entered in shell eats up first line
    primarykey
    data
    text
    <p>I've using a .bashrc from one of peepcode's screencast.</p> <pre><code># If not running interactively, don't do anything [ -z "$PS1" ] &amp;&amp; return # check the window size after each command and, if necessary, # update the values of LINES and COLUMNS. shopt -s checkwinsize # set variable identifying the chroot you work in (used in the prompt below) if [ -z "$debian_chroot" ] &amp;&amp; [ -r /etc/debian_chroot ]; then debian_chroot=$(cat /etc/debian_chroot) fi # set a fancy prompt (non-color, overwrite the one in /etc/profile) PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ ' # Commented out, don't overwrite xterm -T "title" -n "icontitle" by default. # If this is an xterm set the title to user@host:dir #case "$TERM" in #xterm*|rxvt*) # PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME}: ${PWD}\007"' # ;; #*) # ;; #esac # enable bash completion in interactive shells #if [ -f /etc/bash_completion ] &amp;&amp; ! shopt -oq posix; then # . /etc/bash_completion #fi # sudo hint if [ ! -e "$HOME/.sudo_as_admin_successful" ]; then case " $(groups) " in *\ admin\ *) if [ -x /usr/bin/sudo ]; then cat &lt;&lt;-EOF To run a command as administrator (user "root"), use "sudo &lt;command&gt;". See "man sudo_root" for details. EOF fi esac fi # if the command-not-found package is installed, use it if [ -x /usr/lib/command-not-found -o -x /usr/share/command-not-found ]; then function command_not_found_handle { # check because c-n-f could've been removed in the meantime if [ -x /usr/lib/command-not-found ]; then /usr/bin/python /usr/lib/command-not-found -- $1 return $? elif [ -x /usr/share/command-not-found ]; then /usr/bin/python /usr/share/command-not-found -- $1 return $? else return 127 fi } fi . ~/bin/bash_colors.sh #load bash aliases if [ -f ~/.bash_aliases ]; then . ~/.bash_aliases fi # Unbreak broken, non-colored terminal export TERM='xterm-color' alias ls='ls -G' alias ll='ls -lG' export LSCOLORS="ExGxBxDxCxEgEdxbxgxcxd" export GREP_OPTIONS="--color" # Erase duplicates in history export HISTCONTROL=erasedups # Store 10k history entries export HISTSIZE=10000 # Append to the history file when exiting instead of overwriting it shopt -s histappend function minutes_since_last_commit { now=`date +%s` last_commit=`git log --pretty=format:'%at' -1` seconds_since_last_commit=$((now-last_commit)) minutes_since_last_commit=$((seconds_since_last_commit/60)) echo $minutes_since_last_commit } grb_git_prompt() { local g="$(__gitdir)" if [ -n "$g" ]; then local MINUTES_SINCE_LAST_COMMIT=`minutes_since_last_commit` if [ "$MINUTES_SINCE_LAST_COMMIT" -gt 30 ]; then local COLOR=${RED} elif [ "$MINUTES_SINCE_LAST_COMMIT" -gt 10 ]; then local COLOR=${YELLOW} else local COLOR=${GREEN} fi local SINCE_LAST_COMMIT="${COLOR}$(minutes_since_last_commit)m${NORMAL}" # The __git_ps1 function inserts the current git branch where %s is local GIT_PROMPT=`__git_ps1 "(%s|${SINCE_LAST_COMMIT})"` echo ${GIT_PROMPT} fi } export PS1='$(grb_git_prompt)$ ' gd() { git diff $* | view -; } gdc() { gd --cached $*; } source ~/bin/git-completion.bash </code></pre> <p>I can confirm the error is in grb_git_promit. What happens is the second lines typed in shell is overwriting the first line. Can anyone could help me with this?</p> <p>EDIT:</p> <pre><code>grb_git_prompt() { local g="$(__gitdir)" if [ -n "$g" ]; then local MINUTES_SINCE_LAST_COMMIT=`minutes_since_last_commit` if [ "$MINUTES_SINCE_LAST_COMMIT" -gt 30 ]; then local COLOR="\[\033[0;31m\]" elif [ "$MINUTES_SINCE_LAST_COMMIT" -gt 10 ]; then local COLOR="\[\033[0;37m\]" else local COLOR="\[\033[0;32m\]" fi local SINCE_LAST_COMMIT="${COLOR}$(minutes_since_last_commit)m$" # The __git_ps1 function inserts the current git branch where %s is echo "$(__git_ps1 '(%s|')${SINCE_LAST_COMMIT}" fi } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USsent-hil
    1. USsent-hil
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PO.bashrc break, second line entered in shell eats up first line
      1. USCiarán
      1. VTFavorite
    2. VO
      singulars
      1. PO.bashrc break, second line entered in shell eats up first line
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO.bashrc break, second line entered in shell eats up first line
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI don't completely understand the problem, but I tested this and it is working fine for me.
      singulars
      1. PO.bashrc break, second line entered in shell eats up first line
      1. USJamal Fanaian
    2. COWhen I type a long command say "gedit /really/long/filename/that/takes/up/two/lines/in/bash/shell" it becomes "bash shell ally/long/filename/that/takes/up/two/lines/in." I'm not sure if I'm explaining it properly, basically when the command becomes two lines, instead of going to second line, it begins to eat up the first line. If you google "bash line wrapping overwrites beginning of line" you'll know what I'm talking about. (I did, but couldn't find any answers.)
      singulars
      1. PO.bashrc break, second line entered in shell eats up first line
      1. USsent-hil
    3. CO@Senthil: Where do `RED`, `YELLOW`, `GREEN`, and `NORMAL` come from? I bet your problem is in there, since those are presumably terminal escape sequences. If they're being automatically generated somehow, check to make sure that `TERM` has an appropriate value. Also, I suspect that you might want to quote them when assigning: `COLOR="${RED}"`. You could of course confirm whether or not this is the problem by removing the color from the prompt.
      singulars
      1. PO.bashrc break, second line entered in shell eats up first line
      1. USCascabel
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload