History feature not working on ubuntu 10.10 notebook edition terminal
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
No worries; I sometimes find myself using shell semantics w/o making
sure people know what I'm talking about.
You shouldn't have to. You will, however, most likely have
to log out and back in to make the change take.
Cheers,
Tink
OK, so I did log out and then logged back in. Is there anything else I should do.
If not then, how would I know if it worked?
When I logged back in, the up and down arrows still didn't produce any commands, and I still get this result for history:
mansour@ubuntu-notebook:~$ history
1 history
mansour@ubuntu-notebook:~$
That's because w/o the login-shell sourcing .bashrc the relevant lines
Code:
HISTSIZE=1000
HISTFILESIZE=2000
won't have been in effect. If you now run commands in bash, close the
window by typing 'exit' or 'Ctrl-D', and then open a new one you should
see the previous entries using cursor up/down.
On a side-note: you can make the saving of history more efficient (less
prone to errors) by adding this to ~/.bashrc
That's because w/o the login-shell sourcing .bashrc the relevant lines
Code:
HISTSIZE=1000
HISTFILESIZE=2000
won't have been in effect. If you now run commands in bash, close the
window by typing 'exit' or 'Ctrl-D', and then open a new one you should
see the previous entries using cursor up/down.
On a side-note: you can make the saving of history more efficient (less
prone to errors) by adding this to ~/.bashrc
Code:
export PROMPT_COMMAND='history -a'
I just did as you said. Also added the line to the end of my ~./bashrc but still no effects. up and down arrows won't do anything.
This is quite confusing ... the options for HISTSIZE
and HISTFILESIZE are missing, even though they're part
of your .bashrc ...
If you try a
Code:
. ~/.bashrc
and then repeat the env|grep ... what do you see?
Cheers,
Tink
mansour@ubuntu-notebook:~$ sudo . ~/.bashrc
sudo: .: command not found
mansour@ubuntu-notebook:~$ sudo ./.bashrc
sudo: ./.bashrc: command not found
mansour@ubuntu-notebook:~$
mansour@ubuntu-notebook:~$ sudo . ~/.bashrc
sudo: .: command not found
mansour@ubuntu-notebook:~$ sudo ./.bashrc
sudo: ./.bashrc: command not found
mansour@ubuntu-notebook:~$
This makes no sense at all ... can you once more confirm that
Code:
HISTSIZE=1000
HISTFILESIZE=2000
is still in ~mansour/.bashrc and not commented out?
Cheers,
Tink
Yes it is, and no is not commented out.
Code:
GNU nano 2.2.4 File: /home/mansour/.bashrc
# ~/.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
.
.
.
.
.
GNU nano 2.2.4 File: /home/mansour/.bashrc
# ~/.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
.
.
.
.
.
Of course this not the whole file.
mansour
For completeness sake, can you attach both the ~/.bashrc and ~/.bash_login
here to your next post?
For completeness sake, can you attach both the ~/.bashrc and ~/.bash_login
here to your next post?
Cheers,
Tink
Here we go:
~/.bash_login
Code:
if [ -f ~/.bashsrc ]; then
~/.bahsrc
fi
and ~/.bashrc
Code:
GNU nano 2.2.4 File: /home/mansour/.bashrc Modified
if [ -f ~/.bashsrc ]; then
~/.bahsrc
fi
# ~/.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$
# 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
export PROMPT_COMMAND='history -a'
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.