[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This Appendix describes the GNU History library, a programming tool that provides a consistent user interface for recalling lines of previously typed input.
A.1 Introduction to History | What is the GNU History library for? | |
A.2 History Interaction | What it feels like using History as a user. |
[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Many programs read input from the user a line at a time. The GNU history library is able to keep track of those lines, associate arbitrary data with each line, and utilize information from previous lines in making up new ones.
The programmer using the History library has available to him functions for remembering lines on a history stack, associating arbitrary data with a line, removing lines from the stack, searching through the stack for a line containing an arbitrary text string, and referencing any line on the stack directly. In addition, a history expansion function is available which provides for a consistent user interface across many different programs.
When you use programs written with the History library, you have the benefit of a consistent user interface, with a set of well-known commands for manipulating the text of previous lines and using that text in new commands. The basic history manipulation commands are similar to the history substitution used by Csh.
GNU programs often also use the Readline library, which includes history manipulation by default, and has the added advantage of Emacs style command line editing.
[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The History library provides a history expansion feature that is similar to the history expansion in Csh. The following text describes what syntax features are available.
History expansion takes place in two parts. The first is to determine which line from the previous history should be used during substitution. The second is to select portions of that line for inclusion into the current one. The line selected from the previous history is called the event, and the portions of that line that are acted upon are called words. The line is broken into words in the same fashion used by the Bash shell, so that several words surrounded by quotes are treated as if they were a single word.
A.2.1 Event Designators | How to specify which history line to use. * Word Designators:: Specifying which words are of interest. * Modifiers:: Modifying the results of susbstitution. |
[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
An event designator is a reference to a command line entry in the history list.
!
Start a history subsititution, except when followed by a space, tab, or the end of the line; or by ‘=’ or ‘(’.
!!
Refer to the previous command. This is a synonym for !-1
.
!n
Refer to command line n.
!-n
Refer to the command line n lines back.
!string
Refer to the most recent command starting with string.
!?string
[?
]Refer to the most recent command containing string.
[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
A ‘:’ separates the event specification from the word designator. It can be omitted if the word designator begins with a ‘^’, ‘$’, ‘*’ or ‘%’. Words are numbered from the beginning of the line, with the first word being denoted by a 0 (zero).
0 (zero)
The zero’th word. For many applications, this is the command word.
n
The n’th word.
^
The first argument. that is, word 1.
$
The last argument.
%
The word matched by the most recent ?string?
search.
x-y
A range of words; -y
abbreviates 0-y
.
*
All of the words, excepting the zero’th. This is a synonym for ‘1-$’. It is not an error to use ‘*’ if there is just one word in the event. The empty string is returned in that case.
[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
After the optional word designator, you can add a sequence of one or more of the following modifiers, each preceded by a ‘:’.
#
The entire command line typed so far. This means the current command, not the previous command, so it really isn’t a word designator, and doesn’t belong in this section.
h
Remove a trailing pathname component, leaving only the head.
r
Remove a trailing suffix of the form ‘.suffix’, leaving the basename.
e
Remove all but the suffix.
t
Remove all leading pathname components, leaving the tail.
p
Print the new command but do not execute it. This takes effect immediately, so it should be the last specifier on the line.
[Top] | [Contents] | [Index] | [ ? ] |
This document was generated on March 29, 2022 using texi2html 5.0.
The buttons in the navigation panels have the following meaning:
Button | Name | Go to | From 1.2.3 go to |
---|---|---|---|
[ << ] | FastBack | Beginning of this chapter or previous chapter | 1 |
[ < ] | Back | Previous section in reading order | 1.2.2 |
[ Up ] | Up | Up section | 1.2 |
[ > ] | Forward | Next section in reading order | 1.2.4 |
[ >> ] | FastForward | Next chapter | 2 |
[Top] | Top | Cover (top) of document | |
[Contents] | Contents | Table of contents | |
[Index] | Index | Index | |
[ ? ] | About | About (help) |
where the Example assumes that the current position is at Subsubsection One-Two-Three of a document of the following structure:
This document was generated on March 29, 2022 using texi2html 5.0.