]> git.ipfire.org Git - thirdparty/bash.git/blob - lib/readline/doc/hsuser.texi
Bash-4.2 distribution sources and documentation
[thirdparty/bash.git] / lib / readline / doc / hsuser.texi
1 @ignore
2 This file documents the user interface to the GNU History library.
3
4 Copyright (C) 1988--2011 Free Software Foundation, Inc.
5 Authored by Brian Fox and Chet Ramey.
6
7 Permission is granted to make and distribute verbatim copies of this manual
8 provided the copyright notice and this permission notice are preserved on
9 all copies.
10
11 Permission is granted to process this file through Tex and print the
12 results, provided the printed document carries copying permission notice
13 identical to this one except for the removal of this paragraph (this
14 paragraph not being relevant to the printed manual).
15
16 Permission is granted to copy and distribute modified versions of this
17 manual under the conditions for verbatim copying, provided also that the
18 GNU Copyright statement is available to the distributee, and provided that
19 the entire resulting derived work is distributed under the terms of a
20 permission notice identical to this one.
21
22 Permission is granted to copy and distribute translations of this manual
23 into another language, under the above conditions for modified versions.
24 @end ignore
25
26 @node Using History Interactively
27 @chapter Using History Interactively
28
29 @ifclear BashFeatures
30 @defcodeindex bt
31 @end ifclear
32
33 @ifset BashFeatures
34 This chapter describes how to use the @sc{gnu} History Library
35 interactively, from a user's standpoint.
36 It should be considered a user's guide.
37 For information on using the @sc{gnu} History Library in other programs,
38 see the @sc{gnu} Readline Library Manual.
39 @end ifset
40 @ifclear BashFeatures
41 This chapter describes how to use the @sc{gnu} History Library interactively,
42 from a user's standpoint. It should be considered a user's guide. For
43 information on using the @sc{gnu} History Library in your own programs,
44 @pxref{Programming with GNU History}.
45 @end ifclear
46
47 @ifset BashFeatures
48 @menu
49 * Bash History Facilities:: How Bash lets you manipulate your command
50 history.
51 * Bash History Builtins:: The Bash builtin commands that manipulate
52 the command history.
53 * History Interaction:: What it feels like using History as a user.
54 @end menu
55 @end ifset
56 @ifclear BashFeatures
57 @menu
58 * History Interaction:: What it feels like using History as a user.
59 @end menu
60 @end ifclear
61
62 @ifset BashFeatures
63 @node Bash History Facilities
64 @section Bash History Facilities
65 @cindex command history
66 @cindex history list
67
68 When the @option{-o history} option to the @code{set} builtin
69 is enabled (@pxref{The Set Builtin}),
70 the shell provides access to the @dfn{command history},
71 the list of commands previously typed.
72 The value of the @env{HISTSIZE} shell variable is used as the
73 number of commands to save in a history list.
74 The text of the last @env{$HISTSIZE}
75 commands (default 500) is saved.
76 The shell stores each command in the history list prior to
77 parameter and variable expansion
78 but after history expansion is performed, subject to the
79 values of the shell variables
80 @env{HISTIGNORE} and @env{HISTCONTROL}.
81
82 When the shell starts up, the history is initialized from the
83 file named by the @env{HISTFILE} variable (default @file{~/.bash_history}).
84 The file named by the value of @env{HISTFILE} is truncated, if
85 necessary, to contain no more than the number of lines specified by
86 the value of the @env{HISTFILESIZE} variable.
87 When an interactive shell exits, the last
88 @env{$HISTSIZE} lines are copied from the history list to the file
89 named by @env{$HISTFILE}.
90 If the @code{histappend} shell option is set (@pxref{Bash Builtins}),
91 the lines are appended to the history file,
92 otherwise the history file is overwritten.
93 If @env{HISTFILE}
94 is unset, or if the history file is unwritable, the history is
95 not saved. After saving the history, the history file is truncated
96 to contain no more than @env{$HISTFILESIZE}
97 lines. If @env{HISTFILESIZE} is not set, no truncation is performed.
98
99 If the @env{HISTTIMEFORMAT} is set, the time stamp information
100 associated with each history entry is written to the history file,
101 marked with the history comment character.
102 When the history file is read, lines beginning with the history
103 comment character followed immediately by a digit are interpreted
104 as timestamps for the previous history line.
105
106 The builtin command @code{fc} may be used to list or edit and re-execute
107 a portion of the history list.
108 The @code{history} builtin may be used to display or modify the history
109 list and manipulate the history file.
110 When using command-line editing, search commands
111 are available in each editing mode that provide access to the
112 history list (@pxref{Commands For History}).
113
114 The shell allows control over which commands are saved on the history
115 list. The @env{HISTCONTROL} and @env{HISTIGNORE}
116 variables may be set to cause the shell to save only a subset of the
117 commands entered.
118 The @code{cmdhist}
119 shell option, if enabled, causes the shell to attempt to save each
120 line of a multi-line command in the same history entry, adding
121 semicolons where necessary to preserve syntactic correctness.
122 The @code{lithist}
123 shell option causes the shell to save the command with embedded newlines
124 instead of semicolons.
125 The @code{shopt} builtin is used to set these options.
126 @xref{Bash Builtins}, for a description of @code{shopt}.
127
128 @node Bash History Builtins
129 @section Bash History Builtins
130 @cindex history builtins
131
132 Bash provides two builtin commands which manipulate the
133 history list and history file.
134
135 @table @code
136
137 @item fc
138 @btindex fc
139 @example
140 @code{fc [-e @var{ename}] [-lnr] [@var{first}] [@var{last}]}
141 @code{fc -s [@var{pat}=@var{rep}] [@var{command}]}
142 @end example
143
144 Fix Command. In the first form, a range of commands from @var{first} to
145 @var{last} is selected from the history list. Both @var{first} and
146 @var{last} may be specified as a string (to locate the most recent
147 command beginning with that string) or as a number (an index into the
148 history list, where a negative number is used as an offset from the
149 current command number). If @var{last} is not specified it is set to
150 @var{first}. If @var{first} is not specified it is set to the previous
151 command for editing and @minus{}16 for listing. If the @option{-l} flag is
152 given, the commands are listed on standard output. The @option{-n} flag
153 suppresses the command numbers when listing. The @option{-r} flag
154 reverses the order of the listing. Otherwise, the editor given by
155 @var{ename} is invoked on a file containing those commands. If
156 @var{ename} is not given, the value of the following variable expansion
157 is used: @code{$@{FCEDIT:-$@{EDITOR:-vi@}@}}. This says to use the
158 value of the @env{FCEDIT} variable if set, or the value of the
159 @env{EDITOR} variable if that is set, or @code{vi} if neither is set.
160 When editing is complete, the edited commands are echoed and executed.
161
162 In the second form, @var{command} is re-executed after each instance
163 of @var{pat} in the selected command is replaced by @var{rep}.
164
165 A useful alias to use with the @code{fc} command is @code{r='fc -s'}, so
166 that typing @samp{r cc} runs the last command beginning with @code{cc}
167 and typing @samp{r} re-executes the last command (@pxref{Aliases}).
168
169 @item history
170 @btindex history
171 @example
172 history [@var{n}]
173 history -c
174 history -d @var{offset}
175 history [-anrw] [@var{filename}]
176 history -ps @var{arg}
177 @end example
178
179 With no options, display the history list with line numbers.
180 Lines prefixed with a @samp{*} have been modified.
181 An argument of @var{n} lists only the last @var{n} lines.
182 If the shell variable @env{HISTTIMEFORMAT} is set and not null,
183 it is used as a format string for @var{strftime} to display
184 the time stamp associated with each displayed history entry.
185 No intervening blank is printed between the formatted time stamp
186 and the history line.
187
188 Options, if supplied, have the following meanings:
189
190 @table @code
191 @item -c
192 Clear the history list. This may be combined
193 with the other options to replace the history list completely.
194
195 @item -d @var{offset}
196 Delete the history entry at position @var{offset}.
197 @var{offset} should be specified as it appears when the history is
198 displayed.
199
200 @item -a
201 Append the new
202 history lines (history lines entered since the beginning of the
203 current Bash session) to the history file.
204
205 @item -n
206 Append the history lines not already read from the history file
207 to the current history list. These are lines appended to the history
208 file since the beginning of the current Bash session.
209
210 @item -r
211 Read the current history file and append its contents to
212 the history list.
213
214 @item -w
215 Write out the current history to the history file.
216
217 @item -p
218 Perform history substitution on the @var{arg}s and display the result
219 on the standard output, without storing the results in the history list.
220
221 @item -s
222 The @var{arg}s are added to the end of
223 the history list as a single entry.
224
225 @end table
226
227 When any of the @option{-w}, @option{-r}, @option{-a}, or @option{-n} options is
228 used, if @var{filename}
229 is given, then it is used as the history file. If not, then
230 the value of the @env{HISTFILE} variable is used.
231
232 @end table
233 @end ifset
234
235 @node History Interaction
236 @section History Expansion
237 @cindex history expansion
238
239 The History library provides a history expansion feature that is similar
240 to the history expansion provided by @code{csh}. This section
241 describes the syntax used to manipulate the history information.
242
243 History expansions introduce words from the history list into
244 the input stream, making it easy to repeat commands, insert the
245 arguments to a previous command into the current input line, or
246 fix errors in previous commands quickly.
247
248 History expansion takes place in two parts. The first is to determine
249 which line from the history list should be used during substitution.
250 The second is to select portions of that line for inclusion into the
251 current one. The line selected from the history is called the
252 @dfn{event}, and the portions of that line that are acted upon are
253 called @dfn{words}. Various @dfn{modifiers} are available to manipulate
254 the selected words. The line is broken into words in the same fashion
255 that Bash does, so that several words
256 surrounded by quotes are considered one word.
257 History expansions are introduced by the appearance of the
258 history expansion character, which is @samp{!} by default.
259 @ifset BashFeatures
260 Only @samp{\} and @samp{'} may be used to escape the history expansion
261 character.
262 @end ifset
263
264 @ifset BashFeatures
265 Several shell options settable with the @code{shopt}
266 builtin (@pxref{Bash Builtins}) may be used to tailor
267 the behavior of history expansion. If the
268 @code{histverify} shell option is enabled, and Readline
269 is being used, history substitutions are not immediately passed to
270 the shell parser.
271 Instead, the expanded line is reloaded into the Readline
272 editing buffer for further modification.
273 If Readline is being used, and the @code{histreedit}
274 shell option is enabled, a failed history expansion will be
275 reloaded into the Readline editing buffer for correction.
276 The @option{-p} option to the @code{history} builtin command
277 may be used to see what a history expansion will do before using it.
278 The @option{-s} option to the @code{history} builtin may be used to
279 add commands to the end of the history list without actually executing
280 them, so that they are available for subsequent recall.
281 This is most useful in conjunction with Readline.
282
283 The shell allows control of the various characters used by the
284 history expansion mechanism with the @code{histchars} variable,
285 as explained above (@pxref{Bash Variables}). The shell uses
286 the history comment character to mark history timestamps when
287 writing the history file.
288 @end ifset
289
290 @menu
291 * Event Designators:: How to specify which history line to use.
292 * Word Designators:: Specifying which words are of interest.
293 * Modifiers:: Modifying the results of substitution.
294 @end menu
295
296 @node Event Designators
297 @subsection Event Designators
298 @cindex event designators
299
300 An event designator is a reference to a command line entry in the
301 history list.
302 Unless the reference is absolute, events are relative to the current
303 position in the history list.
304 @cindex history events
305
306 @table @asis
307
308 @item @code{!}
309 @ifset BashFeatures
310 Start a history substitution, except when followed by a space, tab,
311 the end of the line, @samp{=} or @samp{(} (when the
312 @code{extglob} shell option is enabled using the @code{shopt} builtin).
313 @end ifset
314 @ifclear BashFeatures
315 Start a history substitution, except when followed by a space, tab,
316 the end of the line, or @samp{=}.
317 @end ifclear
318
319 @item @code{!@var{n}}
320 Refer to command line @var{n}.
321
322 @item @code{!-@var{n}}
323 Refer to the command @var{n} lines back.
324
325 @item @code{!!}
326 Refer to the previous command. This is a synonym for @samp{!-1}.
327
328 @item @code{!@var{string}}
329 Refer to the most recent command
330 preceding the current position in the history list
331 starting with @var{string}.
332
333 @item @code{!?@var{string}[?]}
334 Refer to the most recent command
335 preceding the current position in the history list
336 containing @var{string}.
337 The trailing
338 @samp{?} may be omitted if the @var{string} is followed immediately by
339 a newline.
340
341 @item @code{^@var{string1}^@var{string2}^}
342 Quick Substitution. Repeat the last command, replacing @var{string1}
343 with @var{string2}. Equivalent to
344 @code{!!:s/@var{string1}/@var{string2}/}.
345
346 @item @code{!#}
347 The entire command line typed so far.
348
349 @end table
350
351 @node Word Designators
352 @subsection Word Designators
353
354 Word designators are used to select desired words from the event.
355 A @samp{:} separates the event specification from the word designator. It
356 may be omitted if the word designator begins with a @samp{^}, @samp{$},
357 @samp{*}, @samp{-}, or @samp{%}. Words are numbered from the beginning
358 of the line, with the first word being denoted by 0 (zero). Words are
359 inserted into the current line separated by single spaces.
360
361 @need 0.75
362 For example,
363
364 @table @code
365 @item !!
366 designates the preceding command. When you type this, the preceding
367 command is repeated in toto.
368
369 @item !!:$
370 designates the last argument of the preceding command. This may be
371 shortened to @code{!$}.
372
373 @item !fi:2
374 designates the second argument of the most recent command starting with
375 the letters @code{fi}.
376 @end table
377
378 @need 0.75
379 Here are the word designators:
380
381 @table @code
382
383 @item 0 (zero)
384 The @code{0}th word. For many applications, this is the command word.
385
386 @item @var{n}
387 The @var{n}th word.
388
389 @item ^
390 The first argument; that is, word 1.
391
392 @item $
393 The last argument.
394
395 @item %
396 The word matched by the most recent @samp{?@var{string}?} search.
397
398 @item @var{x}-@var{y}
399 A range of words; @samp{-@var{y}} abbreviates @samp{0-@var{y}}.
400
401 @item *
402 All of the words, except the @code{0}th. This is a synonym for @samp{1-$}.
403 It is not an error to use @samp{*} if there is just one word in the event;
404 the empty string is returned in that case.
405
406 @item @var{x}*
407 Abbreviates @samp{@var{x}-$}
408
409 @item @var{x}-
410 Abbreviates @samp{@var{x}-$} like @samp{@var{x}*}, but omits the last word.
411
412 @end table
413
414 If a word designator is supplied without an event specification, the
415 previous command is used as the event.
416
417 @node Modifiers
418 @subsection Modifiers
419
420 After the optional word designator, you can add a sequence of one or more
421 of the following modifiers, each preceded by a @samp{:}.
422
423 @table @code
424
425 @item h
426 Remove a trailing pathname component, leaving only the head.
427
428 @item t
429 Remove all leading pathname components, leaving the tail.
430
431 @item r
432 Remove a trailing suffix of the form @samp{.@var{suffix}}, leaving
433 the basename.
434
435 @item e
436 Remove all but the trailing suffix.
437
438 @item p
439 Print the new command but do not execute it.
440
441 @ifset BashFeatures
442 @item q
443 Quote the substituted words, escaping further substitutions.
444
445 @item x
446 Quote the substituted words as with @samp{q},
447 but break into words at spaces, tabs, and newlines.
448 @end ifset
449
450 @item s/@var{old}/@var{new}/
451 Substitute @var{new} for the first occurrence of @var{old} in the
452 event line. Any delimiter may be used in place of @samp{/}.
453 The delimiter may be quoted in @var{old} and @var{new}
454 with a single backslash. If @samp{&} appears in @var{new},
455 it is replaced by @var{old}. A single backslash will quote
456 the @samp{&}. The final delimiter is optional if it is the last
457 character on the input line.
458
459 @item &
460 Repeat the previous substitution.
461
462 @item g
463 @itemx a
464 Cause changes to be applied over the entire event line. Used in
465 conjunction with @samp{s}, as in @code{gs/@var{old}/@var{new}/},
466 or with @samp{&}.
467
468 @item G
469 Apply the following @samp{s} modifier once to each word in the event.
470
471 @end table