]> git.ipfire.org Git - thirdparty/bash.git/blame - lib/readline/doc/rluser.texi
commit bash-20041230 snapshot
[thirdparty/bash.git] / lib / readline / doc / rluser.texi
CommitLineData
d3a24ed2
CR
1@comment %**start of header (This is for running Texinfo on a region.)
2@setfilename rluser.info
3@comment %**end of header (This is for running Texinfo on a region.)
4@setchapternewpage odd
5
6@ignore
7This file documents the end user interface to the GNU command line
8editing features. It is to be an appendix to manuals for programs which
9use these features. There is a document entitled "readline.texinfo"
10which contains both end-user and programmer documentation for the
11GNU Readline Library.
12
113d85a4 13Copyright (C) 1988-2004 Free Software Foundation, Inc.
d3a24ed2
CR
14
15Authored by Brian Fox and Chet Ramey.
16
17Permission is granted to process this file through Tex and print the
18results, provided the printed document carries copying permission notice
19identical to this one except for the removal of this paragraph (this
20paragraph not being relevant to the printed manual).
21
22Permission is granted to make and distribute verbatim copies of this manual
23provided the copyright notice and this permission notice are preserved on
24all copies.
25
26Permission is granted to copy and distribute modified versions of this
27manual under the conditions for verbatim copying, provided also that the
28GNU Copyright statement is available to the distributee, and provided that
29the entire resulting derived work is distributed under the terms of a
30permission notice identical to this one.
31
32Permission is granted to copy and distribute translations of this manual
33into another language, under the above conditions for modified versions.
34@end ignore
35
36@comment If you are including this manual as an appendix, then set the
37@comment variable readline-appendix.
38
39@ifclear BashFeatures
40@defcodeindex bt
41@end ifclear
42
43@node Command Line Editing
44@chapter Command Line Editing
45
46This chapter describes the basic features of the @sc{gnu}
47command line editing interface.
48@ifset BashFeatures
49Command line editing is provided by the Readline library, which is
50used by several different programs, including Bash.
51@end ifset
52
53@menu
54* Introduction and Notation:: Notation used in this text.
55* Readline Interaction:: The minimum set of commands for editing a line.
56* Readline Init File:: Customizing Readline from a user's view.
57* Bindable Readline Commands:: A description of most of the Readline commands
58 available for binding
59* Readline vi Mode:: A short description of how to make Readline
60 behave like the vi editor.
61@ifset BashFeatures
62* Programmable Completion:: How to specify the possible completions for
63 a specific command.
64* Programmable Completion Builtins:: Builtin commands to specify how to
65 complete arguments for a particular command.
66@end ifset
67@end menu
68
69@node Introduction and Notation
70@section Introduction to Line Editing
71
72The following paragraphs describe the notation used to represent
73keystrokes.
74
75The text @kbd{C-k} is read as `Control-K' and describes the character
76produced when the @key{k} key is pressed while the Control key
77is depressed.
78
79The text @kbd{M-k} is read as `Meta-K' and describes the character
80produced when the Meta key (if you have one) is depressed, and the @key{k}
81key is pressed.
82The Meta key is labeled @key{ALT} on many keyboards.
83On keyboards with two keys labeled @key{ALT} (usually to either side of
84the space bar), the @key{ALT} on the left side is generally set to
85work as a Meta key.
86The @key{ALT} key on the right may also be configured to work as a
87Meta key or may be configured as some other modifier, such as a
88Compose key for typing accented characters.
89
90If you do not have a Meta or @key{ALT} key, or another key working as
91a Meta key, the identical keystroke can be generated by typing @key{ESC}
92@emph{first}, and then typing @key{k}.
93Either process is known as @dfn{metafying} the @key{k} key.
94
95The text @kbd{M-C-k} is read as `Meta-Control-k' and describes the
96character produced by @dfn{metafying} @kbd{C-k}.
97
98In addition, several keys have their own names. Specifically,
99@key{DEL}, @key{ESC}, @key{LFD}, @key{SPC}, @key{RET}, and @key{TAB} all
100stand for themselves when seen in this text, or in an init file
101(@pxref{Readline Init File}).
102If your keyboard lacks a @key{LFD} key, typing @key{C-j} will
103produce the desired character.
104The @key{RET} key may be labeled @key{Return} or @key{Enter} on
105some keyboards.
106
107@node Readline Interaction
108@section Readline Interaction
109@cindex interaction, readline
110
111Often during an interactive session you type in a long line of text,
112only to notice that the first word on the line is misspelled. The
113Readline library gives you a set of commands for manipulating the text
114as you type it in, allowing you to just fix your typo, and not forcing
115you to retype the majority of the line. Using these editing commands,
116you move the cursor to the place that needs correction, and delete or
117insert the text of the corrections. Then, when you are satisfied with
118the line, you simply press @key{RET}. You do not have to be at the
119end of the line to press @key{RET}; the entire line is accepted
120regardless of the location of the cursor within the line.
121
122@menu
123* Readline Bare Essentials:: The least you need to know about Readline.
124* Readline Movement Commands:: Moving about the input line.
125* Readline Killing Commands:: How to delete text, and how to get it back!
126* Readline Arguments:: Giving numeric arguments to commands.
127* Searching:: Searching through previous lines.
128@end menu
129
130@node Readline Bare Essentials
131@subsection Readline Bare Essentials
132@cindex notation, readline
133@cindex command editing
134@cindex editing command lines
135
136In order to enter characters into the line, simply type them. The typed
137character appears where the cursor was, and then the cursor moves one
138space to the right. If you mistype a character, you can use your
139erase character to back up and delete the mistyped character.
140
141Sometimes you may mistype a character, and
142not notice the error until you have typed several other characters. In
143that case, you can type @kbd{C-b} to move the cursor to the left, and then
144correct your mistake. Afterwards, you can move the cursor to the right
145with @kbd{C-f}.
146
147When you add text in the middle of a line, you will notice that characters
148to the right of the cursor are `pushed over' to make room for the text
149that you have inserted. Likewise, when you delete text behind the cursor,
150characters to the right of the cursor are `pulled back' to fill in the
151blank space created by the removal of the text. A list of the bare
152essentials for editing the text of an input line follows.
153
154@table @asis
155@item @kbd{C-b}
156Move back one character.
157@item @kbd{C-f}
158Move forward one character.
159@item @key{DEL} or @key{Backspace}
160Delete the character to the left of the cursor.
161@item @kbd{C-d}
162Delete the character underneath the cursor.
163@item @w{Printing characters}
164Insert the character into the line at the cursor.
165@item @kbd{C-_} or @kbd{C-x C-u}
166Undo the last editing command. You can undo all the way back to an
167empty line.
168@end table
169
170@noindent
171(Depending on your configuration, the @key{Backspace} key be set to
172delete the character to the left of the cursor and the @key{DEL} key set
173to delete the character underneath the cursor, like @kbd{C-d}, rather
174than the character to the left of the cursor.)
175
176@node Readline Movement Commands
177@subsection Readline Movement Commands
178
179
180The above table describes the most basic keystrokes that you need
181in order to do editing of the input line. For your convenience, many
182other commands have been added in addition to @kbd{C-b}, @kbd{C-f},
183@kbd{C-d}, and @key{DEL}. Here are some commands for moving more rapidly
184about the line.
185
186@table @kbd
187@item C-a
188Move to the start of the line.
189@item C-e
190Move to the end of the line.
191@item M-f
192Move forward a word, where a word is composed of letters and digits.
193@item M-b
194Move backward a word.
195@item C-l
196Clear the screen, reprinting the current line at the top.
197@end table
198
199Notice how @kbd{C-f} moves forward a character, while @kbd{M-f} moves
200forward a word. It is a loose convention that control keystrokes
201operate on characters while meta keystrokes operate on words.
202
203@node Readline Killing Commands
204@subsection Readline Killing Commands
205
206@cindex killing text
207@cindex yanking text
208
209@dfn{Killing} text means to delete the text from the line, but to save
210it away for later use, usually by @dfn{yanking} (re-inserting)
211it back into the line.
212(`Cut' and `paste' are more recent jargon for `kill' and `yank'.)
213
214If the description for a command says that it `kills' text, then you can
215be sure that you can get the text back in a different (or the same)
216place later.
217
218When you use a kill command, the text is saved in a @dfn{kill-ring}.
219Any number of consecutive kills save all of the killed text together, so
220that when you yank it back, you get it all. The kill
221ring is not line specific; the text that you killed on a previously
222typed line is available to be yanked back later, when you are typing
223another line.
224@cindex kill ring
225
226Here is the list of commands for killing text.
227
228@table @kbd
229@item C-k
230Kill the text from the current cursor position to the end of the line.
231
232@item M-d
233Kill from the cursor to the end of the current word, or, if between
234words, to the end of the next word.
235Word boundaries are the same as those used by @kbd{M-f}.
236
237@item M-@key{DEL}
238Kill from the cursor the start of the current word, or, if between
239words, to the start of the previous word.
240Word boundaries are the same as those used by @kbd{M-b}.
241
242@item C-w
243Kill from the cursor to the previous whitespace. This is different than
244@kbd{M-@key{DEL}} because the word boundaries differ.
245
246@end table
247
248Here is how to @dfn{yank} the text back into the line. Yanking
249means to copy the most-recently-killed text from the kill buffer.
250
251@table @kbd
252@item C-y
253Yank the most recently killed text back into the buffer at the cursor.
254
255@item M-y
256Rotate the kill-ring, and yank the new top. You can only do this if
257the prior command is @kbd{C-y} or @kbd{M-y}.
258@end table
259
260@node Readline Arguments
261@subsection Readline Arguments
262
263You can pass numeric arguments to Readline commands. Sometimes the
264argument acts as a repeat count, other times it is the @i{sign} of the
265argument that is significant. If you pass a negative argument to a
266command which normally acts in a forward direction, that command will
267act in a backward direction. For example, to kill text back to the
268start of the line, you might type @samp{M-- C-k}.
269
270The general way to pass numeric arguments to a command is to type meta
271digits before the command. If the first `digit' typed is a minus
272sign (@samp{-}), then the sign of the argument will be negative. Once
273you have typed one meta digit to get the argument started, you can type
274the remainder of the digits, and then the command. For example, to give
275the @kbd{C-d} command an argument of 10, you could type @samp{M-1 0 C-d},
276which will delete the next ten characters on the input line.
277
278@node Searching
279@subsection Searching for Commands in the History
280
281Readline provides commands for searching through the command history
282@ifset BashFeatures
283(@pxref{Bash History Facilities})
284@end ifset
285for lines containing a specified string.
286There are two search modes: @dfn{incremental} and @dfn{non-incremental}.
287
288Incremental searches begin before the user has finished typing the
289search string.
290As each character of the search string is typed, Readline displays
291the next entry from the history matching the string typed so far.
292An incremental search requires only as many characters as needed to
293find the desired history entry.
294To search backward in the history for a particular string, type
295@kbd{C-r}. Typing @kbd{C-s} searches forward through the history.
296The characters present in the value of the @code{isearch-terminators} variable
297are used to terminate an incremental search.
298If that variable has not been assigned a value, the @key{ESC} and
299@kbd{C-J} characters will terminate an incremental search.
300@kbd{C-g} will abort an incremental search and restore the original line.
301When the search is terminated, the history entry containing the
302search string becomes the current line.
303
304To find other matching entries in the history list, type @kbd{C-r} or
305@kbd{C-s} as appropriate.
306This will search backward or forward in the history for the next
307entry matching the search string typed so far.
308Any other key sequence bound to a Readline command will terminate
309the search and execute that command.
310For instance, a @key{RET} will terminate the search and accept
311the line, thereby executing the command from the history list.
312A movement command will terminate the search, make the last line found
313the current line, and begin editing.
314
315Readline remembers the last incremental search string. If two
316@kbd{C-r}s are typed without any intervening characters defining a new
317search string, any remembered search string is used.
318
319Non-incremental searches read the entire search string before starting
320to search for matching history lines. The search string may be
321typed by the user or be part of the contents of the current line.
322
323@node Readline Init File
324@section Readline Init File
325@cindex initialization file, readline
326
327Although the Readline library comes with a set of Emacs-like
328keybindings installed by default, it is possible to use a different set
329of keybindings.
330Any user can customize programs that use Readline by putting
331commands in an @dfn{inputrc} file, conventionally in his home directory.
332The name of this
333@ifset BashFeatures
334file is taken from the value of the shell variable @env{INPUTRC}. If
335@end ifset
336@ifclear BashFeatures
337file is taken from the value of the environment variable @env{INPUTRC}. If
338@end ifclear
339that variable is unset, the default is @file{~/.inputrc}.
340
341When a program which uses the Readline library starts up, the
342init file is read, and the key bindings are set.
343
344In addition, the @code{C-x C-r} command re-reads this init file, thus
345incorporating any changes that you might have made to it.
346
347@menu
348* Readline Init File Syntax:: Syntax for the commands in the inputrc file.
349
350* Conditional Init Constructs:: Conditional key bindings in the inputrc file.
351
352* Sample Init File:: An example inputrc file.
353@end menu
354
355@node Readline Init File Syntax
356@subsection Readline Init File Syntax
357
358There are only a few basic constructs allowed in the
359Readline init file. Blank lines are ignored.
360Lines beginning with a @samp{#} are comments.
361Lines beginning with a @samp{$} indicate conditional
362constructs (@pxref{Conditional Init Constructs}). Other lines
363denote variable settings and key bindings.
364
365@table @asis
366@item Variable Settings
367You can modify the run-time behavior of Readline by
368altering the values of variables in Readline
369using the @code{set} command within the init file.
370The syntax is simple:
371
372@example
373set @var{variable} @var{value}
374@end example
375
376@noindent
377Here, for example, is how to
378change from the default Emacs-like key binding to use
379@code{vi} line editing commands:
380
381@example
382set editing-mode vi
383@end example
384
385Variable names and values, where appropriate, are recognized without regard
386to case.
387
388@ifset BashFeatures
389The @w{@code{bind -V}} command lists the current Readline variable names
390and values. @xref{Bash Builtins}.
391@end ifset
392
393A great deal of run-time behavior is changeable with the following
394variables.
395
396@cindex variables, readline
397@table @code
398
399@item bell-style
400@vindex bell-style
401Controls what happens when Readline wants to ring the terminal bell.
402If set to @samp{none}, Readline never rings the bell. If set to
403@samp{visible}, Readline uses a visible bell if one is available.
404If set to @samp{audible} (the default), Readline attempts to ring
405the terminal's bell.
406
453f278a 407@item bind-tty-special-chars
eb2bb562 408@vindex bind-tty-special-chars
453f278a
CR
409If set to @samp{on}, Readline attempts to bind the control characters
410treated specially by the kernel's terminal driver to their Readline
411equivalents.
412
d3a24ed2
CR
413@item comment-begin
414@vindex comment-begin
415The string to insert at the beginning of the line when the
416@code{insert-comment} command is executed. The default value
417is @code{"#"}.
418
419@item completion-ignore-case
420If set to @samp{on}, Readline performs filename matching and completion
421in a case-insensitive fashion.
422The default value is @samp{off}.
423
424@item completion-query-items
425@vindex completion-query-items
426The number of possible completions that determines when the user is
427asked whether the list of possibilities should be displayed.
428If the number of possible completions is greater than this value,
429Readline will ask the user whether or not he wishes to view
430them; otherwise, they are simply listed.
431This variable must be set to an integer value greater than or equal to 0.
432The default limit is @code{100}.
433
434@item convert-meta
435@vindex convert-meta
436If set to @samp{on}, Readline will convert characters with the
437eighth bit set to an @sc{ascii} key sequence by stripping the eighth
438bit and prefixing an @key{ESC} character, converting them to a
439meta-prefixed key sequence. The default value is @samp{on}.
440
441@item disable-completion
442@vindex disable-completion
443If set to @samp{On}, Readline will inhibit word completion.
444Completion characters will be inserted into the line as if they had
445been mapped to @code{self-insert}. The default is @samp{off}.
446
447@item editing-mode
448@vindex editing-mode
449The @code{editing-mode} variable controls which default set of
450key bindings is used. By default, Readline starts up in Emacs editing
451mode, where the keystrokes are most similar to Emacs. This variable can be
452set to either @samp{emacs} or @samp{vi}.
453
454@item enable-keypad
455@vindex enable-keypad
456When set to @samp{on}, Readline will try to enable the application
457keypad when it is called. Some systems need this to enable the
458arrow keys. The default is @samp{off}.
459
460@item expand-tilde
461@vindex expand-tilde
462If set to @samp{on}, tilde expansion is performed when Readline
463attempts word completion. The default is @samp{off}.
464
465@vindex history-preserve-point
466If set to @samp{on}, the history code attempts to place point at the
467same location on each history line retrieved with @code{previous-history}
468or @code{next-history}.
469
470@item horizontal-scroll-mode
471@vindex horizontal-scroll-mode
472This variable can be set to either @samp{on} or @samp{off}. Setting it
473to @samp{on} means that the text of the lines being edited will scroll
474horizontally on a single screen line when they are longer than the width
475of the screen, instead of wrapping onto a new screen line. By default,
476this variable is set to @samp{off}.
477
478@item input-meta
479@vindex input-meta
480@vindex meta-flag
481If set to @samp{on}, Readline will enable eight-bit input (it
482will not clear the eighth bit in the characters it reads),
483regardless of what the terminal claims it can support. The
484default value is @samp{off}. The name @code{meta-flag} is a
485synonym for this variable.
486
487@item isearch-terminators
488@vindex isearch-terminators
489The string of characters that should terminate an incremental search without
490subsequently executing the character as a command (@pxref{Searching}).
491If this variable has not been given a value, the characters @key{ESC} and
492@kbd{C-J} will terminate an incremental search.
493
494@item keymap
495@vindex keymap
496Sets Readline's idea of the current keymap for key binding commands.
497Acceptable @code{keymap} names are
498@code{emacs},
499@code{emacs-standard},
500@code{emacs-meta},
501@code{emacs-ctlx},
502@code{vi},
503@code{vi-move},
504@code{vi-command}, and
505@code{vi-insert}.
506@code{vi} is equivalent to @code{vi-command}; @code{emacs} is
507equivalent to @code{emacs-standard}. The default value is @code{emacs}.
508The value of the @code{editing-mode} variable also affects the
509default keymap.
510
511@item mark-directories
512If set to @samp{on}, completed directory names have a slash
513appended. The default is @samp{on}.
514
515@item mark-modified-lines
516@vindex mark-modified-lines
517This variable, when set to @samp{on}, causes Readline to display an
518asterisk (@samp{*}) at the start of history lines which have been modified.
519This variable is @samp{off} by default.
520
521@item mark-symlinked-directories
522@vindex mark-symlinked-directories
523If set to @samp{on}, completed names which are symbolic links
524to directories have a slash appended (subject to the value of
525@code{mark-directories}).
526The default is @samp{off}.
527
528@item match-hidden-files
529@vindex match-hidden-files
530This variable, when set to @samp{on}, causes Readline to match files whose
531names begin with a @samp{.} (hidden files) when performing filename
532completion, unless the leading @samp{.} is
533supplied by the user in the filename to be completed.
534This variable is @samp{on} by default.
535
536@item output-meta
537@vindex output-meta
538If set to @samp{on}, Readline will display characters with the
539eighth bit set directly rather than as a meta-prefixed escape
540sequence. The default is @samp{off}.
541
542@item page-completions
543@vindex page-completions
544If set to @samp{on}, Readline uses an internal @code{more}-like pager
545to display a screenful of possible completions at a time.
546This variable is @samp{on} by default.
547
548@item print-completions-horizontally
549If set to @samp{on}, Readline will display completions with matches
550sorted horizontally in alphabetical order, rather than down the screen.
551The default is @samp{off}.
552
553@item show-all-if-ambiguous
554@vindex show-all-if-ambiguous
555This alters the default behavior of the completion functions. If
556set to @samp{on},
557words which have more than one possible completion cause the
558matches to be listed immediately instead of ringing the bell.
559The default value is @samp{off}.
560
561@item show-all-if-unmodified
562@vindex show-all-if-unmodified
563This alters the default behavior of the completion functions in
564a fashion similar to @var{show-all-if-ambiguous}.
565If set to @samp{on},
566words which have more than one possible completion without any
567possible partial completion (the possible completions don't share
568a common prefix) cause the matches to be listed immediately instead
569of ringing the bell.
570The default value is @samp{off}.
571
572@item visible-stats
573@vindex visible-stats
574If set to @samp{on}, a character denoting a file's type
575is appended to the filename when listing possible
576completions. The default is @samp{off}.
577
578@end table
579
580@item Key Bindings
581The syntax for controlling key bindings in the init file is
582simple. First you need to find the name of the command that you
583want to change. The following sections contain tables of the command
584name, the default keybinding, if any, and a short description of what
585the command does.
586
587Once you know the name of the command, simply place on a line
588in the init file the name of the key
589you wish to bind the command to, a colon, and then the name of the
590command. The name of the key
591can be expressed in different ways, depending on what you find most
592comfortable.
593
594In addition to command names, readline allows keys to be bound
595to a string that is inserted when the key is pressed (a @var{macro}).
596
597@ifset BashFeatures
598The @w{@code{bind -p}} command displays Readline function names and
599bindings in a format that can put directly into an initialization file.
600@xref{Bash Builtins}.
601@end ifset
602
603@table @asis
604@item @w{@var{keyname}: @var{function-name} or @var{macro}}
605@var{keyname} is the name of a key spelled out in English. For example:
606@example
607Control-u: universal-argument
608Meta-Rubout: backward-kill-word
609Control-o: "> output"
610@end example
611
612In the above example, @kbd{C-u} is bound to the function
613@code{universal-argument},
614@kbd{M-DEL} is bound to the function @code{backward-kill-word}, and
615@kbd{C-o} is bound to run the macro
616expressed on the right hand side (that is, to insert the text
617@samp{> output} into the line).
618
619A number of symbolic character names are recognized while
620processing this key binding syntax:
621@var{DEL},
622@var{ESC},
623@var{ESCAPE},
624@var{LFD},
625@var{NEWLINE},
626@var{RET},
627@var{RETURN},
628@var{RUBOUT},
629@var{SPACE},
630@var{SPC},
631and
632@var{TAB}.
633
634@item @w{"@var{keyseq}": @var{function-name} or @var{macro}}
635@var{keyseq} differs from @var{keyname} above in that strings
636denoting an entire key sequence can be specified, by placing
637the key sequence in double quotes. Some @sc{gnu} Emacs style key
638escapes can be used, as in the following example, but the
639special character names are not recognized.
640
641@example
642"\C-u": universal-argument
643"\C-x\C-r": re-read-init-file
644"\e[11~": "Function Key 1"
645@end example
646
647In the above example, @kbd{C-u} is again bound to the function
648@code{universal-argument} (just as it was in the first example),
649@samp{@kbd{C-x} @kbd{C-r}} is bound to the function @code{re-read-init-file},
650and @samp{@key{ESC} @key{[} @key{1} @key{1} @key{~}} is bound to insert
651the text @samp{Function Key 1}.
652
653@end table
654
655The following @sc{gnu} Emacs style escape sequences are available when
656specifying key sequences:
657
658@table @code
659@item @kbd{\C-}
660control prefix
661@item @kbd{\M-}
662meta prefix
663@item @kbd{\e}
664an escape character
665@item @kbd{\\}
666backslash
667@item @kbd{\"}
668@key{"}, a double quotation mark
669@item @kbd{\'}
670@key{'}, a single quote or apostrophe
671@end table
672
673In addition to the @sc{gnu} Emacs style escape sequences, a second
674set of backslash escapes is available:
675
676@table @code
677@item \a
678alert (bell)
679@item \b
680backspace
681@item \d
682delete
683@item \f
684form feed
685@item \n
686newline
687@item \r
688carriage return
689@item \t
690horizontal tab
691@item \v
692vertical tab
693@item \@var{nnn}
694the eight-bit character whose value is the octal value @var{nnn}
695(one to three digits)
696@item \x@var{HH}
697the eight-bit character whose value is the hexadecimal value @var{HH}
698(one or two hex digits)
699@end table
700
701When entering the text of a macro, single or double quotes must
702be used to indicate a macro definition.
703Unquoted text is assumed to be a function name.
704In the macro body, the backslash escapes described above are expanded.
705Backslash will quote any other character in the macro text,
706including @samp{"} and @samp{'}.
707For example, the following binding will make @samp{@kbd{C-x} \}
708insert a single @samp{\} into the line:
709@example
710"\C-x\\": "\\"
711@end example
712
713@end table
714
715@node Conditional Init Constructs
716@subsection Conditional Init Constructs
717
718Readline implements a facility similar in spirit to the conditional
719compilation features of the C preprocessor which allows key
720bindings and variable settings to be performed as the result
721of tests. There are four parser directives used.
722
723@table @code
724@item $if
725The @code{$if} construct allows bindings to be made based on the
726editing mode, the terminal being used, or the application using
727Readline. The text of the test extends to the end of the line;
728no characters are required to isolate it.
729
730@table @code
731@item mode
732The @code{mode=} form of the @code{$if} directive is used to test
733whether Readline is in @code{emacs} or @code{vi} mode.
734This may be used in conjunction
735with the @samp{set keymap} command, for instance, to set bindings in
736the @code{emacs-standard} and @code{emacs-ctlx} keymaps only if
737Readline is starting out in @code{emacs} mode.
738
739@item term
740The @code{term=} form may be used to include terminal-specific
741key bindings, perhaps to bind the key sequences output by the
742terminal's function keys. The word on the right side of the
743@samp{=} is tested against both the full name of the terminal and
744the portion of the terminal name before the first @samp{-}. This
745allows @code{sun} to match both @code{sun} and @code{sun-cmd},
746for instance.
747
748@item application
749The @var{application} construct is used to include
750application-specific settings. Each program using the Readline
751library sets the @var{application name}, and you can test for
752a particular value.
753This could be used to bind key sequences to functions useful for
754a specific program. For instance, the following command adds a
755key sequence that quotes the current or previous word in Bash:
756@example
757$if Bash
758# Quote the current or previous word
759"\C-xq": "\eb\"\ef\""
760$endif
761@end example
762@end table
763
764@item $endif
765This command, as seen in the previous example, terminates an
766@code{$if} command.
767
768@item $else
769Commands in this branch of the @code{$if} directive are executed if
770the test fails.
771
772@item $include
773This directive takes a single filename as an argument and reads commands
774and bindings from that file.
775For example, the following directive reads from @file{/etc/inputrc}:
776@example
777$include /etc/inputrc
778@end example
779@end table
780
781@node Sample Init File
782@subsection Sample Init File
783
784Here is an example of an @var{inputrc} file. This illustrates key
785binding, variable assignment, and conditional syntax.
786
787@example
788@page
789# This file controls the behaviour of line input editing for
790# programs that use the GNU Readline library. Existing
791# programs include FTP, Bash, and GDB.
792#
793# You can re-read the inputrc file with C-x C-r.
794# Lines beginning with '#' are comments.
795#
796# First, include any systemwide bindings and variable
797# assignments from /etc/Inputrc
798$include /etc/Inputrc
799
800#
801# Set various bindings for emacs mode.
802
803set editing-mode emacs
804
805$if mode=emacs
806
807Meta-Control-h: backward-kill-word Text after the function name is ignored
808
809#
810# Arrow keys in keypad mode
811#
812#"\M-OD": backward-char
813#"\M-OC": forward-char
814#"\M-OA": previous-history
815#"\M-OB": next-history
816#
817# Arrow keys in ANSI mode
818#
819"\M-[D": backward-char
820"\M-[C": forward-char
821"\M-[A": previous-history
822"\M-[B": next-history
823#
824# Arrow keys in 8 bit keypad mode
825#
826#"\M-\C-OD": backward-char
827#"\M-\C-OC": forward-char
828#"\M-\C-OA": previous-history
829#"\M-\C-OB": next-history
830#
831# Arrow keys in 8 bit ANSI mode
832#
833#"\M-\C-[D": backward-char
834#"\M-\C-[C": forward-char
835#"\M-\C-[A": previous-history
836#"\M-\C-[B": next-history
837
838C-q: quoted-insert
839
840$endif
841
842# An old-style binding. This happens to be the default.
843TAB: complete
844
845# Macros that are convenient for shell interaction
846$if Bash
847# edit the path
848"\C-xp": "PATH=$@{PATH@}\e\C-e\C-a\ef\C-f"
849# prepare to type a quoted word --
850# insert open and close double quotes
851# and move to just after the open quote
852"\C-x\"": "\"\"\C-b"
853# insert a backslash (testing backslash escapes
854# in sequences and macros)
855"\C-x\\": "\\"
856# Quote the current or previous word
857"\C-xq": "\eb\"\ef\""
858# Add a binding to refresh the line, which is unbound
859"\C-xr": redraw-current-line
860# Edit variable on current line.
861"\M-\C-v": "\C-a\C-k$\C-y\M-\C-e\C-a\C-y="
862$endif
863
864# use a visible bell if one is available
865set bell-style visible
866
867# don't strip characters to 7 bits when reading
868set input-meta on
869
870# allow iso-latin1 characters to be inserted rather
871# than converted to prefix-meta sequences
872set convert-meta off
873
874# display characters with the eighth bit set directly
875# rather than as meta-prefixed characters
876set output-meta on
877
878# if there are more than 150 possible completions for
879# a word, ask the user if he wants to see all of them
880set completion-query-items 150
881
882# For FTP
883$if Ftp
884"\C-xg": "get \M-?"
885"\C-xt": "put \M-?"
886"\M-.": yank-last-arg
887$endif
888@end example
889
890@node Bindable Readline Commands
891@section Bindable Readline Commands
892
893@menu
894* Commands For Moving:: Moving about the line.
895* Commands For History:: Getting at previous lines.
896* Commands For Text:: Commands for changing text.
897* Commands For Killing:: Commands for killing and yanking.
898* Numeric Arguments:: Specifying numeric arguments, repeat counts.
899* Commands For Completion:: Getting Readline to do the typing for you.
900* Keyboard Macros:: Saving and re-executing typed characters
901* Miscellaneous Commands:: Other miscellaneous commands.
902@end menu
903
904This section describes Readline commands that may be bound to key
905sequences.
906@ifset BashFeatures
907You can list your key bindings by executing
908@w{@code{bind -P}} or, for a more terse format, suitable for an
909@var{inputrc} file, @w{@code{bind -p}}. (@xref{Bash Builtins}.)
910@end ifset
911Command names without an accompanying key sequence are unbound by default.
912
913In the following descriptions, @dfn{point} refers to the current cursor
914position, and @dfn{mark} refers to a cursor position saved by the
915@code{set-mark} command.
916The text between the point and mark is referred to as the @dfn{region}.
917
918@node Commands For Moving
919@subsection Commands For Moving
920@ftable @code
921@item beginning-of-line (C-a)
922Move to the start of the current line.
923
924@item end-of-line (C-e)
925Move to the end of the line.
926
927@item forward-char (C-f)
928Move forward a character.
929
930@item backward-char (C-b)
931Move back a character.
932
933@item forward-word (M-f)
934Move forward to the end of the next word. Words are composed of
935letters and digits.
936
937@item backward-word (M-b)
938Move back to the start of the current or previous word. Words are
939composed of letters and digits.
940
941@item clear-screen (C-l)
942Clear the screen and redraw the current line,
943leaving the current line at the top of the screen.
944
945@item redraw-current-line ()
946Refresh the current line. By default, this is unbound.
947
948@end ftable
949
950@node Commands For History
951@subsection Commands For Manipulating The History
952
953@ftable @code
954@item accept-line (Newline or Return)
955@ifset BashFeatures
956Accept the line regardless of where the cursor is.
957If this line is
958non-empty, add it to the history list according to the setting of
959the @env{HISTCONTROL} and @env{HISTIGNORE} variables.
960If this line is a modified history line, then restore the history line
961to its original state.
962@end ifset
963@ifclear BashFeatures
964Accept the line regardless of where the cursor is.
965If this line is
966non-empty, it may be added to the history list for future recall with
967@code{add_history()}.
968If this line is a modified history line, the history line is restored
969to its original state.
970@end ifclear
971
972@item previous-history (C-p)
973Move `back' through the history list, fetching the previous command.
974
975@item next-history (C-n)
976Move `forward' through the history list, fetching the next command.
977
978@item beginning-of-history (M-<)
979Move to the first line in the history.
980
981@item end-of-history (M->)
982Move to the end of the input history, i.e., the line currently
983being entered.
984
985@item reverse-search-history (C-r)
986Search backward starting at the current line and moving `up' through
987the history as necessary. This is an incremental search.
988
989@item forward-search-history (C-s)
990Search forward starting at the current line and moving `down' through
991the the history as necessary. This is an incremental search.
992
993@item non-incremental-reverse-search-history (M-p)
994Search backward starting at the current line and moving `up'
995through the history as necessary using a non-incremental search
996for a string supplied by the user.
997
998@item non-incremental-forward-search-history (M-n)
999Search forward starting at the current line and moving `down'
1000through the the history as necessary using a non-incremental search
1001for a string supplied by the user.
1002
1003@item history-search-forward ()
1004Search forward through the history for the string of characters
1005between the start of the current line and the point.
1006This is a non-incremental search.
1007By default, this command is unbound.
1008
1009@item history-search-backward ()
1010Search backward through the history for the string of characters
1011between the start of the current line and the point. This
1012is a non-incremental search. By default, this command is unbound.
1013
1014@item yank-nth-arg (M-C-y)
1015Insert the first argument to the previous command (usually
1016the second word on the previous line) at point.
1017With an argument @var{n},
1018insert the @var{n}th word from the previous command (the words
1019in the previous command begin with word 0). A negative argument
1020inserts the @var{n}th word from the end of the previous command.
eb2bb562
CR
1021Once the argument @var{n} is computed, the argument is extracted
1022as if the @samp{!@var{n}} history expansion had been specified.
d3a24ed2
CR
1023
1024@item yank-last-arg (M-. or M-_)
1025Insert last argument to the previous command (the last word of the
1026previous history entry). With an
1027argument, behave exactly like @code{yank-nth-arg}.
1028Successive calls to @code{yank-last-arg} move back through the history
1029list, inserting the last argument of each line in turn.
eb2bb562
CR
1030The history expansion facilities are used to extract the last argument,
1031as if the @samp{!$} history expansion had been specified.
d3a24ed2
CR
1032
1033@end ftable
1034
1035@node Commands For Text
1036@subsection Commands For Changing Text
1037
1038@ftable @code
1039@item delete-char (C-d)
1040Delete the character at point. If point is at the
1041beginning of the line, there are no characters in the line, and
1042the last character typed was not bound to @code{delete-char}, then
1043return @sc{eof}.
1044
1045@item backward-delete-char (Rubout)
1046Delete the character behind the cursor. A numeric argument means
1047to kill the characters instead of deleting them.
1048
1049@item forward-backward-delete-char ()
1050Delete the character under the cursor, unless the cursor is at the
1051end of the line, in which case the character behind the cursor is
1052deleted. By default, this is not bound to a key.
1053
1054@item quoted-insert (C-q or C-v)
1055Add the next character typed to the line verbatim. This is
1056how to insert key sequences like @kbd{C-q}, for example.
1057
1058@ifclear BashFeatures
1059@item tab-insert (M-@key{TAB})
1060Insert a tab character.
1061@end ifclear
1062
1063@item self-insert (a, b, A, 1, !, @dots{})
1064Insert yourself.
1065
1066@item transpose-chars (C-t)
1067Drag the character before the cursor forward over
1068the character at the cursor, moving the
1069cursor forward as well. If the insertion point
1070is at the end of the line, then this
1071transposes the last two characters of the line.
1072Negative arguments have no effect.
1073
1074@item transpose-words (M-t)
1075Drag the word before point past the word after point,
1076moving point past that word as well.
1077If the insertion point is at the end of the line, this transposes
1078the last two words on the line.
1079
1080@item upcase-word (M-u)
1081Uppercase the current (or following) word. With a negative argument,
1082uppercase the previous word, but do not move the cursor.
1083
1084@item downcase-word (M-l)
1085Lowercase the current (or following) word. With a negative argument,
1086lowercase the previous word, but do not move the cursor.
1087
1088@item capitalize-word (M-c)
1089Capitalize the current (or following) word. With a negative argument,
1090capitalize the previous word, but do not move the cursor.
1091
1092@item overwrite-mode ()
1093Toggle overwrite mode. With an explicit positive numeric argument,
1094switches to overwrite mode. With an explicit non-positive numeric
1095argument, switches to insert mode. This command affects only
1096@code{emacs} mode; @code{vi} mode does overwrite differently.
1097Each call to @code{readline()} starts in insert mode.
1098
1099In overwrite mode, characters bound to @code{self-insert} replace
1100the text at point rather than pushing the text to the right.
1101Characters bound to @code{backward-delete-char} replace the character
1102before point with a space.
1103
1104By default, this command is unbound.
1105
1106@end ftable
1107
1108@node Commands For Killing
1109@subsection Killing And Yanking
1110
1111@ftable @code
1112
1113@item kill-line (C-k)
1114Kill the text from point to the end of the line.
1115
1116@item backward-kill-line (C-x Rubout)
1117Kill backward to the beginning of the line.
1118
1119@item unix-line-discard (C-u)
1120Kill backward from the cursor to the beginning of the current line.
1121
1122@item kill-whole-line ()
1123Kill all characters on the current line, no matter where point is.
1124By default, this is unbound.
1125
1126@item kill-word (M-d)
1127Kill from point to the end of the current word, or if between
1128words, to the end of the next word.
1129Word boundaries are the same as @code{forward-word}.
1130
1131@item backward-kill-word (M-@key{DEL})
1132Kill the word behind point.
1133Word boundaries are the same as @code{backward-word}.
1134
1135@item unix-word-rubout (C-w)
1136Kill the word behind point, using white space as a word boundary.
1137The killed text is saved on the kill-ring.
1138
113d85a4
CR
1139@item unix-filename-rubout ()
1140Kill the word behind point, using white space and the slash character
1141as the word boundaries.
1142The killed text is saved on the kill-ring.
1143
d3a24ed2
CR
1144@item delete-horizontal-space ()
1145Delete all spaces and tabs around point. By default, this is unbound.
1146
1147@item kill-region ()
1148Kill the text in the current region.
1149By default, this command is unbound.
1150
1151@item copy-region-as-kill ()
1152Copy the text in the region to the kill buffer, so it can be yanked
1153right away. By default, this command is unbound.
1154
1155@item copy-backward-word ()
1156Copy the word before point to the kill buffer.
1157The word boundaries are the same as @code{backward-word}.
1158By default, this command is unbound.
1159
1160@item copy-forward-word ()
1161Copy the word following point to the kill buffer.
1162The word boundaries are the same as @code{forward-word}.
1163By default, this command is unbound.
1164
1165@item yank (C-y)
1166Yank the top of the kill ring into the buffer at point.
1167
1168@item yank-pop (M-y)
1169Rotate the kill-ring, and yank the new top. You can only do this if
1170the prior command is @code{yank} or @code{yank-pop}.
1171@end ftable
1172
1173@node Numeric Arguments
1174@subsection Specifying Numeric Arguments
1175@ftable @code
1176
1177@item digit-argument (@kbd{M-0}, @kbd{M-1}, @dots{} @kbd{M--})
1178Add this digit to the argument already accumulating, or start a new
1179argument. @kbd{M--} starts a negative argument.
1180
1181@item universal-argument ()
1182This is another way to specify an argument.
1183If this command is followed by one or more digits, optionally with a
1184leading minus sign, those digits define the argument.
1185If the command is followed by digits, executing @code{universal-argument}
1186again ends the numeric argument, but is otherwise ignored.
1187As a special case, if this command is immediately followed by a
1188character that is neither a digit or minus sign, the argument count
1189for the next command is multiplied by four.
1190The argument count is initially one, so executing this function the
1191first time makes the argument count four, a second time makes the
1192argument count sixteen, and so on.
1193By default, this is not bound to a key.
1194@end ftable
1195
1196@node Commands For Completion
1197@subsection Letting Readline Type For You
1198
1199@ftable @code
1200@item complete (@key{TAB})
1201Attempt to perform completion on the text before point.
1202The actual completion performed is application-specific.
1203@ifset BashFeatures
1204Bash attempts completion treating the text as a variable (if the
1205text begins with @samp{$}), username (if the text begins with
1206@samp{~}), hostname (if the text begins with @samp{@@}), or
1207command (including aliases and functions) in turn. If none
1208of these produces a match, filename completion is attempted.
1209@end ifset
1210@ifclear BashFeatures
1211The default is filename completion.
1212@end ifclear
1213
1214@item possible-completions (M-?)
1215List the possible completions of the text before point.
1216
1217@item insert-completions (M-*)
1218Insert all completions of the text before point that would have
1219been generated by @code{possible-completions}.
1220
1221@item menu-complete ()
1222Similar to @code{complete}, but replaces the word to be completed
1223with a single match from the list of possible completions.
1224Repeated execution of @code{menu-complete} steps through the list
1225of possible completions, inserting each match in turn.
1226At the end of the list of completions, the bell is rung
1227(subject to the setting of @code{bell-style})
1228and the original text is restored.
1229An argument of @var{n} moves @var{n} positions forward in the list
1230of matches; a negative argument may be used to move backward
1231through the list.
1232This command is intended to be bound to @key{TAB}, but is unbound
1233by default.
1234
1235@item delete-char-or-list ()
1236Deletes the character under the cursor if not at the beginning or
1237end of the line (like @code{delete-char}).
1238If at the end of the line, behaves identically to
1239@code{possible-completions}.
1240This command is unbound by default.
1241
1242@ifset BashFeatures
1243@item complete-filename (M-/)
1244Attempt filename completion on the text before point.
1245
1246@item possible-filename-completions (C-x /)
1247List the possible completions of the text before point,
1248treating it as a filename.
1249
1250@item complete-username (M-~)
1251Attempt completion on the text before point, treating
1252it as a username.
1253
1254@item possible-username-completions (C-x ~)
1255List the possible completions of the text before point,
1256treating it as a username.
1257
1258@item complete-variable (M-$)
1259Attempt completion on the text before point, treating
1260it as a shell variable.
1261
1262@item possible-variable-completions (C-x $)
1263List the possible completions of the text before point,
1264treating it as a shell variable.
1265
1266@item complete-hostname (M-@@)
1267Attempt completion on the text before point, treating
1268it as a hostname.
1269
1270@item possible-hostname-completions (C-x @@)
1271List the possible completions of the text before point,
1272treating it as a hostname.
1273
1274@item complete-command (M-!)
1275Attempt completion on the text before point, treating
1276it as a command name. Command completion attempts to
1277match the text against aliases, reserved words, shell
1278functions, shell builtins, and finally executable filenames,
1279in that order.
1280
1281@item possible-command-completions (C-x !)
1282List the possible completions of the text before point,
1283treating it as a command name.
1284
1285@item dynamic-complete-history (M-@key{TAB})
1286Attempt completion on the text before point, comparing
1287the text against lines from the history list for possible
1288completion matches.
1289
1290@item complete-into-braces (M-@{)
1291Perform filename completion and insert the list of possible completions
1292enclosed within braces so the list is available to the shell
1293(@pxref{Brace Expansion}).
1294
1295@end ifset
1296@end ftable
1297
1298@node Keyboard Macros
1299@subsection Keyboard Macros
1300@ftable @code
1301
1302@item start-kbd-macro (C-x ()
1303Begin saving the characters typed into the current keyboard macro.
1304
1305@item end-kbd-macro (C-x ))
1306Stop saving the characters typed into the current keyboard macro
1307and save the definition.
1308
1309@item call-last-kbd-macro (C-x e)
1310Re-execute the last keyboard macro defined, by making the characters
1311in the macro appear as if typed at the keyboard.
1312
1313@end ftable
1314
1315@node Miscellaneous Commands
1316@subsection Some Miscellaneous Commands
1317@ftable @code
1318
1319@item re-read-init-file (C-x C-r)
1320Read in the contents of the @var{inputrc} file, and incorporate
1321any bindings or variable assignments found there.
1322
1323@item abort (C-g)
1324Abort the current editing command and
1325ring the terminal's bell (subject to the setting of
1326@code{bell-style}).
1327
1328@item do-uppercase-version (M-a, M-b, M-@var{x}, @dots{})
1329If the metafied character @var{x} is lowercase, run the command
1330that is bound to the corresponding uppercase character.
1331
1332@item prefix-meta (@key{ESC})
1333Metafy the next character typed. This is for keyboards
1334without a meta key. Typing @samp{@key{ESC} f} is equivalent to typing
1335@kbd{M-f}.
1336
1337@item undo (C-_ or C-x C-u)
1338Incremental undo, separately remembered for each line.
1339
1340@item revert-line (M-r)
1341Undo all changes made to this line. This is like executing the @code{undo}
1342command enough times to get back to the beginning.
1343
1344@ifset BashFeatures
1345@item tilde-expand (M-&)
1346@end ifset
1347@ifclear BashFeatures
1348@item tilde-expand (M-~)
1349@end ifclear
1350Perform tilde expansion on the current word.
1351
1352@item set-mark (C-@@)
1353Set the mark to the point. If a
1354numeric argument is supplied, the mark is set to that position.
1355
1356@item exchange-point-and-mark (C-x C-x)
1357Swap the point with the mark. The current cursor position is set to
1358the saved position, and the old cursor position is saved as the mark.
1359
1360@item character-search (C-])
1361A character is read and point is moved to the next occurrence of that
1362character. A negative count searches for previous occurrences.
1363
1364@item character-search-backward (M-C-])
1365A character is read and point is moved to the previous occurrence
1366of that character. A negative count searches for subsequent
1367occurrences.
1368
1369@item insert-comment (M-#)
1370Without a numeric argument, the value of the @code{comment-begin}
1371variable is inserted at the beginning of the current line.
1372If a numeric argument is supplied, this command acts as a toggle: if
1373the characters at the beginning of the line do not match the value
1374of @code{comment-begin}, the value is inserted, otherwise
1375the characters in @code{comment-begin} are deleted from the beginning of
1376the line.
1377In either case, the line is accepted as if a newline had been typed.
1378@ifset BashFeatures
1379The default value of @code{comment-begin} causes this command
1380to make the current line a shell comment.
1381If a numeric argument causes the comment character to be removed, the line
1382will be executed by the shell.
1383@end ifset
1384
1385@item dump-functions ()
1386Print all of the functions and their key bindings to the
1387Readline output stream. If a numeric argument is supplied,
1388the output is formatted in such a way that it can be made part
1389of an @var{inputrc} file. This command is unbound by default.
1390
1391@item dump-variables ()
1392Print all of the settable variables and their values to the
1393Readline output stream. If a numeric argument is supplied,
1394the output is formatted in such a way that it can be made part
1395of an @var{inputrc} file. This command is unbound by default.
1396
1397@item dump-macros ()
1398Print all of the Readline key sequences bound to macros and the
1399strings they output. If a numeric argument is supplied,
1400the output is formatted in such a way that it can be made part
1401of an @var{inputrc} file. This command is unbound by default.
1402
1403@ifset BashFeatures
1404@item glob-complete-word (M-g)
1405The word before point is treated as a pattern for pathname expansion,
1406with an asterisk implicitly appended. This pattern is used to
1407generate a list of matching file names for possible completions.
1408
1409@item glob-expand-word (C-x *)
1410The word before point is treated as a pattern for pathname expansion,
1411and the list of matching file names is inserted, replacing the word.
1412If a numeric argument is supplied, a @samp{*} is appended before
1413pathname expansion.
1414
1415@item glob-list-expansions (C-x g)
1416The list of expansions that would have been generated by
1417@code{glob-expand-word} is displayed, and the line is redrawn.
1418If a numeric argument is supplied, a @samp{*} is appended before
1419pathname expansion.
1420
1421@item display-shell-version (C-x C-v)
1422Display version information about the current instance of Bash.
1423
1424@item shell-expand-line (M-C-e)
1425Expand the line as the shell does.
1426This performs alias and history expansion as well as all of the shell
1427word expansions (@pxref{Shell Expansions}).
1428
1429@item history-expand-line (M-^)
1430Perform history expansion on the current line.
1431
1432@item magic-space ()
1433Perform history expansion on the current line and insert a space
1434(@pxref{History Interaction}).
1435
1436@item alias-expand-line ()
1437Perform alias expansion on the current line (@pxref{Aliases}).
1438
1439@item history-and-alias-expand-line ()
1440Perform history and alias expansion on the current line.
1441
1442@item insert-last-argument (M-. or M-_)
1443A synonym for @code{yank-last-arg}.
1444
1445@item operate-and-get-next (C-o)
1446Accept the current line for execution and fetch the next line
1447relative to the current line from the history for editing. Any
1448argument is ignored.
1449
1450@item edit-and-execute-command (C-xC-e)
1451Invoke an editor on the current command line, and execute the result as shell
1452commands.
1453Bash attempts to invoke
de8913bd 1454@code{$VISUAL}, @code{$EDITOR}, and @code{emacs}
d3a24ed2
CR
1455as the editor, in that order.
1456
1457@end ifset
1458
1459@ifclear BashFeatures
1460@item emacs-editing-mode (C-e)
1461When in @code{vi} command mode, this causes a switch to @code{emacs}
1462editing mode.
1463
1464@item vi-editing-mode (M-C-j)
1465When in @code{emacs} editing mode, this causes a switch to @code{vi}
1466editing mode.
1467
1468@end ifclear
1469
1470@end ftable
1471
1472@node Readline vi Mode
1473@section Readline vi Mode
1474
1475While the Readline library does not have a full set of @code{vi}
1476editing functions, it does contain enough to allow simple editing
1477of the line. The Readline @code{vi} mode behaves as specified in
1478the @sc{posix} 1003.2 standard.
1479
1480@ifset BashFeatures
1481In order to switch interactively between @code{emacs} and @code{vi}
1482editing modes, use the @samp{set -o emacs} and @samp{set -o vi}
1483commands (@pxref{The Set Builtin}).
1484@end ifset
1485@ifclear BashFeatures
1486In order to switch interactively between @code{emacs} and @code{vi}
1487editing modes, use the command @kbd{M-C-j} (bound to emacs-editing-mode
1488when in @code{vi} mode and to vi-editing-mode in @code{emacs} mode).
1489@end ifclear
1490The Readline default is @code{emacs} mode.
1491
1492When you enter a line in @code{vi} mode, you are already placed in
1493`insertion' mode, as if you had typed an @samp{i}. Pressing @key{ESC}
1494switches you into `command' mode, where you can edit the text of the
1495line with the standard @code{vi} movement keys, move to previous
1496history lines with @samp{k} and subsequent lines with @samp{j}, and
1497so forth.
1498
1499@ifset BashFeatures
1500@node Programmable Completion
1501@section Programmable Completion
1502@cindex programmable completion
1503
1504When word completion is attempted for an argument to a command for
1505which a completion specification (a @var{compspec}) has been defined
1506using the @code{complete} builtin (@pxref{Programmable Completion Builtins}),
1507the programmable completion facilities are invoked.
1508
1509First, the command name is identified.
1510If a compspec has been defined for that command, the
1511compspec is used to generate the list of possible completions for the word.
1512If the command word is a full pathname, a compspec for the full
1513pathname is searched for first.
1514If no compspec is found for the full pathname, an attempt is made to
1515find a compspec for the portion following the final slash.
1516
1517Once a compspec has been found, it is used to generate the list of
1518matching words.
1519If a compspec is not found, the default Bash completion
1520described above (@pxref{Commands For Completion}) is performed.
1521
1522First, the actions specified by the compspec are used.
1523Only matches which are prefixed by the word being completed are
1524returned.
1525When the @option{-f} or @option{-d} option is used for filename or
1526directory name completion, the shell variable @env{FIGNORE} is
1527used to filter the matches.
1528@xref{Bash Variables}, for a description of @env{FIGNORE}.
1529
1530Any completions specified by a filename expansion pattern to the
1531@option{-G} option are generated next.
1532The words generated by the pattern need not match the word being completed.
1533The @env{GLOBIGNORE} shell variable is not used to filter the matches,
1534but the @env{FIGNORE} shell variable is used.
1535
1536Next, the string specified as the argument to the @option{-W} option
1537is considered.
1538The string is first split using the characters in the @env{IFS}
1539special variable as delimiters.
1540Shell quoting is honored.
1541Each word is then expanded using
1542brace expansion, tilde expansion, parameter and variable expansion,
1543command substitution, arithmetic expansion, and pathname expansion,
1544as described above (@pxref{Shell Expansions}).
1545The results are split using the rules described above
1546(@pxref{Word Splitting}).
1547The results of the expansion are prefix-matched against the word being
1548completed, and the matching words become the possible completions.
1549
1550After these matches have been generated, any shell function or command
1551specified with the @option{-F} and @option{-C} options is invoked.
1552When the command or function is invoked, the @env{COMP_LINE} and
1553@env{COMP_POINT} variables are assigned values as described above
1554(@pxref{Bash Variables}).
1555If a shell function is being invoked, the @env{COMP_WORDS} and
1556@env{COMP_CWORD} variables are also set.
1557When the function or command is invoked, the first argument is the
1558name of the command whose arguments are being completed, the
1559second argument is the word being completed, and the third argument
1560is the word preceding the word being completed on the current command line.
1561No filtering of the generated completions against the word being completed
1562is performed; the function or command has complete freedom in generating
1563the matches.
1564
1565Any function specified with @option{-F} is invoked first.
1566The function may use any of the shell facilities, including the
1567@code{compgen} builtin described below
1568(@pxref{Programmable Completion Builtins}), to generate the matches.
1569It must put the possible completions in the @env{COMPREPLY} array
1570variable.
1571
1572Next, any command specified with the @option{-C} option is invoked
1573in an environment equivalent to command substitution.
1574It should print a list of completions, one per line, to
1575the standard output.
1576Backslash may be used to escape a newline, if necessary.
1577
1578After all of the possible completions are generated, any filter
1579specified with the @option{-X} option is applied to the list.
1580The filter is a pattern as used for pathname expansion; a @samp{&}
1581in the pattern is replaced with the text of the word being completed.
1582A literal @samp{&} may be escaped with a backslash; the backslash
1583is removed before attempting a match.
1584Any completion that matches the pattern will be removed from the list.
1585A leading @samp{!} negates the pattern; in this case any completion
1586not matching the pattern will be removed.
1587
1588Finally, any prefix and suffix specified with the @option{-P} and @option{-S}
1589options are added to each member of the completion list, and the result is
1590returned to the Readline completion code as the list of possible
1591completions.
1592
1593If the previously-applied actions do not generate any matches, and the
1594@option{-o dirnames} option was supplied to @code{complete} when the
1595compspec was defined, directory name completion is attempted.
1596
1597If the @option{-o plusdirs} option was supplied to @code{complete} when
1598the compspec was defined, directory name completion is attempted and any
1599matches are added to the results of the other actions.
1600
1601By default, if a compspec is found, whatever it generates is returned to
1602the completion code as the full set of possible completions.
1603The default Bash completions are not attempted, and the Readline default
1604of filename completion is disabled.
1605If the @option{-o bashdefault} option was supplied to @code{complete} when
1606the compspec was defined, the default Bash completions are attempted
1607if the compspec generates no matches.
1608If the @option{-o default} option was supplied to @code{complete} when the
1609compspec was defined, Readline's default completion will be performed
1610if the compspec (and, if attempted, the default Bash completions)
1611generate no matches.
1612
1613When a compspec indicates that directory name completion is desired,
1614the programmable completion functions force Readline to append a slash
1615to completed names which are symbolic links to directories, subject to
1616the value of the @var{mark-directories} Readline variable, regardless
1617of the setting of the @var{mark-symlinked-directories} Readline variable.
1618
1619@node Programmable Completion Builtins
1620@section Programmable Completion Builtins
1621@cindex completion builtins
1622
1623Two builtin commands are available to manipulate the programmable completion
1624facilities.
1625
1626@table @code
1627@item compgen
1628@btindex compgen
1629@example
1630@code{compgen [@var{option}] [@var{word}]}
1631@end example
1632
1633Generate possible completion matches for @var{word} according to
1634the @var{option}s, which may be any option accepted by the
1635@code{complete}
1636builtin with the exception of @option{-p} and @option{-r}, and write
1637the matches to the standard output.
1638When using the @option{-F} or @option{-C} options, the various shell variables
1639set by the programmable completion facilities, while available, will not
1640have useful values.
1641
1642The matches will be generated in the same way as if the programmable
1643completion code had generated them directly from a completion specification
1644with the same flags.
1645If @var{word} is specified, only those completions matching @var{word}
1646will be displayed.
1647
1648The return value is true unless an invalid option is supplied, or no
1649matches were generated.
1650
1651@item complete
1652@btindex complete
1653@example
1654@code{complete [-abcdefgjksuv] [-o @var{comp-option}] [-A @var{action}] [-G @var{globpat}] [-W @var{wordlist}]
1655[-P @var{prefix}] [-S @var{suffix}] [-X @var{filterpat}] [-F @var{function}]
1656[-C @var{command}] @var{name} [@var{name} @dots{}]}
1657@code{complete -pr [@var{name} @dots{}]}
1658@end example
1659
1660Specify how arguments to each @var{name} should be completed.
1661If the @option{-p} option is supplied, or if no options are supplied, existing
1662completion specifications are printed in a way that allows them to be
1663reused as input.
1664The @option{-r} option removes a completion specification for
1665each @var{name}, or, if no @var{name}s are supplied, all
1666completion specifications.
1667
1668The process of applying these completion specifications when word completion
1669is attempted is described above (@pxref{Programmable Completion}).
1670
1671Other options, if specified, have the following meanings.
1672The arguments to the @option{-G}, @option{-W}, and @option{-X} options
1673(and, if necessary, the @option{-P} and @option{-S} options)
1674should be quoted to protect them from expansion before the
1675@code{complete} builtin is invoked.
1676
1677
1678@table @code
1679@item -o @var{comp-option}
1680The @var{comp-option} controls several aspects of the compspec's behavior
1681beyond the simple generation of completions.
1682@var{comp-option} may be one of:
1683
1684@table @code
1685
1686@item bashdefault
1687Perform the rest of the default Bash completions if the compspec
1688generates no matches.
1689
1690@item default
1691Use Readline's default filename completion if the compspec generates
1692no matches.
1693
1694@item dirnames
1695Perform directory name completion if the compspec generates no matches.
1696
1697@item filenames
1698Tell Readline that the compspec generates filenames, so it can perform any
1699filename-specific processing (like adding a slash to directory names or
1700suppressing trailing spaces). This option is intended to be used with
1701shell functions specified with @option{-F}.
1702
1703@item nospace
1704Tell Readline not to append a space (the default) to words completed at
1705the end of the line.
301e2142
CR
1706
1707@item plusdirs
1708After any matches defined by the compspec are generated,
1709directory name completion is attempted and any
1710matches are added to the results of the other actions.
1711
d3a24ed2
CR
1712@end table
1713
1714@item -A @var{action}
1715The @var{action} may be one of the following to generate a list of possible
1716completions:
1717
1718@table @code
1719@item alias
1720Alias names. May also be specified as @option{-a}.
1721
1722@item arrayvar
1723Array variable names.
1724
1725@item binding
1726Readline key binding names (@pxref{Bindable Readline Commands}).
1727
1728@item builtin
1729Names of shell builtin commands. May also be specified as @option{-b}.
1730
1731@item command
1732Command names. May also be specified as @option{-c}.
1733
1734@item directory
1735Directory names. May also be specified as @option{-d}.
1736
1737@item disabled
1738Names of disabled shell builtins.
1739
1740@item enabled
1741Names of enabled shell builtins.
1742
1743@item export
1744Names of exported shell variables. May also be specified as @option{-e}.
1745
1746@item file
1747File names. May also be specified as @option{-f}.
1748
1749@item function
1750Names of shell functions.
1751
1752@item group
1753Group names. May also be specified as @option{-g}.
1754
1755@item helptopic
1756Help topics as accepted by the @code{help} builtin (@pxref{Bash Builtins}).
1757
1758@item hostname
1759Hostnames, as taken from the file specified by the
1760@env{HOSTFILE} shell variable (@pxref{Bash Variables}).
1761
1762@item job
1763Job names, if job control is active. May also be specified as @option{-j}.
1764
1765@item keyword
1766Shell reserved words. May also be specified as @option{-k}.
1767
1768@item running
1769Names of running jobs, if job control is active.
1770
1771@item service
1772Service names. May also be specified as @option{-s}.
1773
1774@item setopt
1775Valid arguments for the @option{-o} option to the @code{set} builtin
1776(@pxref{The Set Builtin}).
1777
1778@item shopt
1779Shell option names as accepted by the @code{shopt} builtin
1780(@pxref{Bash Builtins}).
1781
1782@item signal
1783Signal names.
1784
1785@item stopped
1786Names of stopped jobs, if job control is active.
1787
1788@item user
1789User names. May also be specified as @option{-u}.
1790
1791@item variable
1792Names of all shell variables. May also be specified as @option{-v}.
1793@end table
1794
1795@item -G @var{globpat}
1796The filename expansion pattern @var{globpat} is expanded to generate
1797the possible completions.
1798
1799@item -W @var{wordlist}
1800The @var{wordlist} is split using the characters in the
1801@env{IFS} special variable as delimiters, and each resultant word
1802is expanded.
1803The possible completions are the members of the resultant list which
1804match the word being completed.
1805
1806@item -C @var{command}
1807@var{command} is executed in a subshell environment, and its output is
1808used as the possible completions.
1809
1810@item -F @var{function}
1811The shell function @var{function} is executed in the current shell
1812environment.
1813When it finishes, the possible completions are retrieved from the value
1814of the @env{COMPREPLY} array variable.
1815
1816@item -X @var{filterpat}
1817@var{filterpat} is a pattern as used for filename expansion.
1818It is applied to the list of possible completions generated by the
1819preceding options and arguments, and each completion matching
1820@var{filterpat} is removed from the list.
1821A leading @samp{!} in @var{filterpat} negates the pattern; in this
1822case, any completion not matching @var{filterpat} is removed.
1823
1824@item -P @var{prefix}
1825@var{prefix} is added at the beginning of each possible completion
1826after all other options have been applied.
1827
1828@item -S @var{suffix}
1829@var{suffix} is appended to each possible completion
1830after all other options have been applied.
1831@end table
1832
1833The return value is true unless an invalid option is supplied, an option
1834other than @option{-p} or @option{-r} is supplied without a @var{name}
1835argument, an attempt is made to remove a completion specification for
1836a @var{name} for which no specification exists, or
1837an error occurs adding a completion specification.
1838
1839@end table
1840@end ifset