LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This 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


Reply
  Search this Thread
Old 04-03-2011, 07:29 PM   #16
mansour
Member
 
Registered: Nov 2010
Location: Toronto, Canada
Distribution: Ubuntu 10.04 Lucid Lynx - Ubuntu 10.10 notebook - Debian 5.08 - Win XP
Posts: 172

Original Poster
Rep: Reputation: 2

Quote:
Originally Posted by Tinkster View Post
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:~$






mansour

Last edited by mansour; 04-03-2011 at 07:32 PM.
 
Old 04-03-2011, 08:59 PM   #17
Tinkster
Moderator
 
Registered: Apr 2002
Location: in a fallen world
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
Blog Entries: 11

Rep: Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910
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'
 
Old 04-03-2011, 10:08 PM   #18
mansour
Member
 
Registered: Nov 2010
Location: Toronto, Canada
Distribution: Ubuntu 10.04 Lucid Lynx - Ubuntu 10.10 notebook - Debian 5.08 - Win XP
Posts: 172

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by Tinkster View Post
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.


mansour
 
Old 04-04-2011, 01:22 AM   #19
Tinkster
Moderator
 
Registered: Apr 2002
Location: in a fallen world
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
Blog Entries: 11

Rep: Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910
If you do
Code:
env | grep -i hist
now, what do you see?


Cheers,
Tink
 
Old 04-04-2011, 10:47 AM   #20
mansour
Member
 
Registered: Nov 2010
Location: Toronto, Canada
Distribution: Ubuntu 10.04 Lucid Lynx - Ubuntu 10.10 notebook - Debian 5.08 - Win XP
Posts: 172

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by Tinkster View Post
If you do
Code:
env | grep -i hist
now, what do you see?


Cheers,
Tink

Good Morning:

This is the result:

mansour@ubuntu-notebook:~$ env | grep -i hist
PROMPT_COMMAND=history -a
mansour@ubuntu-notebook:~$

hist is red colour though.


mansour
 
Old 04-04-2011, 02:45 PM   #21
Tinkster
Moderator
 
Registered: Apr 2002
Location: in a fallen world
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
Blog Entries: 11

Rep: Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910
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
 
Old 04-04-2011, 03:22 PM   #22
mansour
Member
 
Registered: Nov 2010
Location: Toronto, Canada
Distribution: Ubuntu 10.04 Lucid Lynx - Ubuntu 10.10 notebook - Debian 5.08 - Win XP
Posts: 172

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by Tinkster View Post
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
 
Old 04-04-2011, 03:24 PM   #23
Tinkster
Moderator
 
Registered: Apr 2002
Location: in a fallen world
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
Blog Entries: 11

Rep: Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910
Why are you trying to use sudo? This is the first time you
mention/use sudo in the thread.

Is the whole problem you experience about root's history?



Cheers,
Tink
 
Old 04-04-2011, 03:26 PM   #24
mansour
Member
 
Registered: Nov 2010
Location: Toronto, Canada
Distribution: Ubuntu 10.04 Lucid Lynx - Ubuntu 10.10 notebook - Debian 5.08 - Win XP
Posts: 172

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by mansour View Post
mansour@ubuntu-notebook:~$ sudo . ~/.bashrc
sudo: .: command not found
mansour@ubuntu-notebook:~$ sudo ./.bashrc
sudo: ./.bashrc: command not found
mansour@ubuntu-notebook:~$

mansour

mansour@ubuntu-notebook:~$ . ~/.bashrc
mansour@ubuntu-notebook:~$ env | grep -i hist
PROMPT_COMMAND=history -a
mansour@ubuntu-notebook:~$
 
Old 04-04-2011, 03:27 PM   #25
mansour
Member
 
Registered: Nov 2010
Location: Toronto, Canada
Distribution: Ubuntu 10.04 Lucid Lynx - Ubuntu 10.10 notebook - Debian 5.08 - Win XP
Posts: 172

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by Tinkster View Post
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:~$ . ~/.bashrc
mansour@ubuntu-notebook:~$ env | grep -i hist
PROMPT_COMMAND=history -a
mansour@ubuntu-notebook:~$
 
Old 04-04-2011, 03:29 PM   #26
mansour
Member
 
Registered: Nov 2010
Location: Toronto, Canada
Distribution: Ubuntu 10.04 Lucid Lynx - Ubuntu 10.10 notebook - Debian 5.08 - Win XP
Posts: 172

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by Tinkster View Post
Why are you trying to use sudo? This is the first time you
mention/use sudo in the thread.

Is the whole problem you experience about root's history?



Cheers,
Tink
No it is not only about root's history? No actually with user mansour too. I thought I should.


mansour

Last edited by mansour; 04-04-2011 at 06:31 PM.
 
Old 04-04-2011, 04:49 PM   #27
Tinkster
Moderator
 
Registered: Apr 2002
Location: in a fallen world
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
Blog Entries: 11

Rep: Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910
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
 
Old 04-04-2011, 07:05 PM   #28
mansour
Member
 
Registered: Nov 2010
Location: Toronto, Canada
Distribution: Ubuntu 10.04 Lucid Lynx - Ubuntu 10.10 notebook - Debian 5.08 - Win XP
Posts: 172

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by Tinkster View Post
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
.
.
.
.
.
Of course this not the whole file.


mansour

Last edited by mansour; 04-04-2011 at 07:06 PM.
 
Old 04-04-2011, 07:27 PM   #29
Tinkster
Moderator
 
Registered: Apr 2002
Location: in a fallen world
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
Blog Entries: 11

Rep: Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910Reputation: 910
Quote:
Originally Posted by mansour View Post
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
.
.
.
.
.
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?


Cheers,
Tink
 
Old 04-04-2011, 08:15 PM   #30
mansour
Member
 
Registered: Nov 2010
Location: Toronto, Canada
Distribution: Ubuntu 10.04 Lucid Lynx - Ubuntu 10.10 notebook - Debian 5.08 - Win XP
Posts: 172

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by Tinkster View 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'



mansour
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Lupu511 pupsave feature apparently is shutting down my notebook to often Benny7440 Linux - Newbie 2 10-16-2010 02:10 PM
Working at the command line with Ubuntu Server edition. David_R Linux - Server 1 06-30-2010 08:02 AM
LXer: A Brief History of Brown: Ubuntu Feature Timeline LXer Syndicated Linux News 0 03-18-2010 01:00 AM
Implement a Unix Shell with History Feature vipin_jss Linux - Newbie 2 05-07-2009 08:38 PM
soundblaster live 24bit edition not working in ubuntu wormraper Ubuntu 2 08-10-2005 07:01 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 06:41 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration