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
# append to the history file, don't overwrite it
shopt -s histappend
# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
# 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)
# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color) color_prompt=yes;;
# 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
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.)
if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
unset color_prompt force_color_prompt
# If this is an xterm set the title to user@host:dir
case "$TERM" in
PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
# 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'
# 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
# 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

lahwran commented Oct 6, 2013

oh I love you. first hit on google.

Thank you, very useful !

Mario you boss! :-D

searchs commented Jul 31, 2014

Real thumbs up!

Shawful commented Sep 22, 2014

YES! Thank you!

hemedani commented Mar 6, 2015


Thanks, bro!

bdhoine commented Aug 4, 2015

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

minils commented Oct 27, 2015

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

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

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

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

indeed. just use that

Thanks you

You're awesome. Thanks.

This is excellent. Thanks!

Thank you !!

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 commented Oct 18, 2017

Thank you!

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.

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 commented Jan 19, 2018

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