Create a gist now

Instantly share code, notes, and snippets.

What would you like to do?
Default .bashrc for ubuntu
# ~/.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
[ -z "$PS1" ] && return
# don't put duplicate lines in the history. See bash(1) for more options
# ... or force ignoredups and ignorespace
HISTCONTROL=ignoredups:ignorespace
# 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
# 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) 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)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[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: \w\a\]$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
# 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 [ -f /etc/bash_completion ] && ! shopt -oq posix; then
. /etc/bash_completion
fi
@kalashnikovisme

This comment has been minimized.

Show comment Hide comment
@kalashnikovisme

kalashnikovisme Sep 26, 2013

thnx!

thnx!

@lahwran

This comment has been minimized.

Show comment Hide comment
@lahwran

lahwran Oct 6, 2013

oh I love you. first hit on google.

lahwran commented Oct 6, 2013

oh I love you. first hit on google.

@julienbourdeau

This comment has been minimized.

Show comment Hide comment
@julienbourdeau

julienbourdeau Oct 27, 2013

Thank you, very useful !

Thank you, very useful !

@brackendawson

This comment has been minimized.

Show comment Hide comment
@brackendawson

brackendawson Oct 31, 2013

Mario you boss! :-D

Mario you boss! :-D

@searchs

This comment has been minimized.

Show comment Hide comment
@searchs

searchs Jul 31, 2014

Real thumbs up!

searchs commented Jul 31, 2014

Real thumbs up!

@Shawful

This comment has been minimized.

Show comment Hide comment
@Shawful

Shawful Sep 22, 2014

YES! Thank you!

Shawful commented Sep 22, 2014

YES! Thank you!

@hemedani

This comment has been minimized.

Show comment Hide comment
@hemedani

hemedani Mar 6, 2015

tanks

hemedani commented Mar 6, 2015

tanks

@ScarHelsing

This comment has been minimized.

Show comment Hide comment
@ScarHelsing

ScarHelsing Apr 26, 2015

Thanks, bro!

Thanks, bro!

@bdhoine

This comment has been minimized.

Show comment Hide comment
@bdhoine

bdhoine Aug 4, 2015

why not use the /etc/skel/.bashrc file?

bdhoine commented Aug 4, 2015

why not use the /etc/skel/.bashrc file?

@minils

This comment has been minimized.

Show comment Hide comment
@minils

minils Oct 27, 2015

Thanks!
Came here for this:
PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '

minils commented Oct 27, 2015

Thanks!
Came here for this:
PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '

@ahmadsocrat

This comment has been minimized.

Show comment Hide comment
@ahmadsocrat

ahmadsocrat Nov 21, 2015

Thank you, I don't know why the hell Cubuntu have replaced this one with their crap bashrc file!!

Thank you, I don't know why the hell Cubuntu have replaced this one with their crap bashrc file!!

@amansubhan

This comment has been minimized.

Show comment Hide comment
@amansubhan

amansubhan Feb 15, 2016

Thanx... my profile is back in shape :D

Thanx... my profile is back in shape :D

@richardn-jm

This comment has been minimized.

Show comment Hide comment
@richardn-jm

richardn-jm Oct 5, 2016

bdhoine commented on 4 Aug 2015
why not use the /etc/skel/.bashrc file?

indeed. just use that

bdhoine commented on 4 Aug 2015
why not use the /etc/skel/.bashrc file?

indeed. just use that

@VictorFursa

This comment has been minimized.

Show comment Hide comment
@VictorFursa

VictorFursa Oct 11, 2016

Thanks you

Thanks you

@enmanuelr

This comment has been minimized.

Show comment Hide comment
@enmanuelr

enmanuelr Nov 3, 2016

You're awesome. Thanks.

You're awesome. Thanks.

@MatthewPeterKelly

This comment has been minimized.

Show comment Hide comment
@MatthewPeterKelly

MatthewPeterKelly Nov 7, 2016

This is excellent. Thanks!

This is excellent. Thanks!

@rafiksemaan

This comment has been minimized.

Show comment Hide comment
@rafiksemaan

rafiksemaan Feb 23, 2017

Thank you !!

Thank you !!

@Sal7yGoa7

This comment has been minimized.

Show comment Hide comment
@Sal7yGoa7

Sal7yGoa7 Jun 26, 2017

Thank you! I'm sure I did what most of the others above me did...I overwrote my .bashrc file (yes, I'm a noob). I'm not great at keyboarding. Thanks for the helpful copy and paste ease you provided.

Thank you! I'm sure I did what most of the others above me did...I overwrote my .bashrc file (yes, I'm a noob). I'm not great at keyboarding. Thanks for the helpful copy and paste ease you provided.

@leezx

This comment has been minimized.

Show comment Hide comment
@leezx

leezx Oct 18, 2017

Thank you!

leezx commented Oct 18, 2017

Thank you!

@demahum

This comment has been minimized.

Show comment Hide comment
@demahum

demahum Oct 26, 2017

Can you provide a source for this? Of course it is good nonetheless, but it would be good to have some other place to find similar things (such as official Ubuntu repository). Gist is somehow unofficial.

demahum commented Oct 26, 2017

Can you provide a source for this? Of course it is good nonetheless, but it would be good to have some other place to find similar things (such as official Ubuntu repository). Gist is somehow unofficial.

@K23Nikhil

This comment has been minimized.

Show comment Hide comment
@K23Nikhil

K23Nikhil Jan 11, 2018

How can replace this file? Actually i have done some changes in bashrc file and due to I'm not able to edit it can anyone suggest me

How can replace this file? Actually i have done some changes in bashrc file and due to I'm not able to edit it can anyone suggest me

@ohnezeit

This comment has been minimized.

Show comment Hide comment
@ohnezeit

ohnezeit Jan 19, 2018

K23BNikhil
Have you tried going in through terminal and trying sudo nano .bashrc?
have you checked the owner/permissions of the file? ls -al
if you are not the owner, or the permissions are not "-rw-r--r-- (your UN) (Your UN)"
To fix permissions: sudo chmod 644 .bashrc ?
To fix the Owner: sudo chown (Your UN) .bashrc

if none of that works... perhaps delete it and make a new .bashrc file? (Not sure how well that would or wouldn't work) But it is probably a permissions issue. Hopefully you can get it worked out.

BTW, Mario, thank you for posting this, very helpful.

ohnezeit commented Jan 19, 2018

K23BNikhil
Have you tried going in through terminal and trying sudo nano .bashrc?
have you checked the owner/permissions of the file? ls -al
if you are not the owner, or the permissions are not "-rw-r--r-- (your UN) (Your UN)"
To fix permissions: sudo chmod 644 .bashrc ?
To fix the Owner: sudo chown (Your UN) .bashrc

if none of that works... perhaps delete it and make a new .bashrc file? (Not sure how well that would or wouldn't work) But it is probably a permissions issue. Hopefully you can get it worked out.

BTW, Mario, thank you for posting this, very helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment