On Monday 21 November 2005 06:07 pm, Adam Hardy wrote:
> Roberto C. Sanchez on 21/11/05 22:30, wrote:
> > On Mon, Nov 21, 2005 at 10:00:33PM +0000, Adam Hardy wrote:
> >>thanks for the tips about C-r Is there some sort of documentation on
> >> this? I'd like to see how much history it keeps. It's a seperate program
> >> from history, right?
> > HISTSIZE
> > The number of commands to remember in the command history
> > (see HISTORY below). The default value is 500.
> > [...]
> > To find other matching entries in the history list, type
> > Control-S or Control-R as appropriate.
ctrl-s will suspend your term in some cases. ctrl-q is your friend.
> > This will search backward or
> > forward in the history for the next entry matching the search string
> > typed so far. Any other key sequence bound to a readline command will
> > terminate the search and execute that command. For instance, a
> > newline will termi- nate the search and accept the line, thereby
> > executing the command from the history list.
> OK thanks.
by default the keybindings are from emacs -- helpful if you use emacs. can be
changed to work like the keystrokes in vi. read the section 'READLINE' in
> I assume that my .bash_history gets converted to binary at some point by
> bash. I can see that bash is using .bash_history now, but it's not clear
> why the file should become binary on my system.