[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: command not put into history if it starts with space

From: DennisW
Subject: Re: command not put into history if it starts with space
Date: Fri, 5 Feb 2010 23:03:26 -0800 (PST)
User-agent: G2/1.0

On Feb 5, 4:07 am, Paul Stansell <address@hidden> wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i386
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i386'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-redhat-linux-gnu'
> -DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale'
> -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H   -I.  -I. -I./include
> -D_FILE_OFFSET_BITS=64 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
> -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32
> -march=i686 -mtune=atom -fasynchronous-unwind-tables
> uname output: Linux ram.opd.local #1 SMP
> Mon Jan 18 20:22:46 UTC 2010 i686 athlon i386 GNU/Linux
> Machine Type: i386-redhat-linux-gnu
> Bash Version: 4.0
> Patch Level: 35
> Release Status: release
> Description:
> When using the bash shell in an xterm or rxvt terminals at least,
> commands executed which start with a space, eg " ls" are not added to
> the command line history and so are not accessible by ctrl-p.
> Repeat-By:
> Type any command prefixed by one or more spaces.  Press return.  Press
> Ctrl-p or type "history | tail".  Observe that last command starting
> with space is not in present in the command history.
> Thanks,
> Paul Stansell

>From the Bash man page:


        A colon-separated list of values controlling  how  commands
        saved  on  the  history  list.   If  the list of values
        ignorespace, lines which begin with a space  character  are
        saved  in  the history list.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]