2 .\" MAN PAGE COMMENTS to
5 .\" Information Network Services
6 .\" Case Western Reserve University
9 .\" Last Change: Thu Feb 19 10:26:47 EST 1998
11 .TH READLINE 3 "1998 Feb 19" GNU
13 .\" File Name macro. This used to be `.PN', for Path Name,
14 .\" but Sun doesn't seem to like that very much.
20 readline \- get a line from a user with editing
32 char *readline (prompt)
37 .if n Readline is Copyright (C) 1989, 1991, 1993, 1995, 1996 by the Free Software Foundation, Inc.
38 .if t Readline is Copyright \(co 1989, 1991, 1993, 1995, 1996 by the Free Software Foundation, Inc.
42 will read a line from the terminal
47 is null, no prompt is issued. The line returned is allocated with
49 so the caller must free it when finished. The line returned
50 has the final newline removed, so only the text of the line
54 offers editing capabilities while the user is entering the
56 By default, the line editing commands
57 are similar to those of emacs.
58 A vi\-style line editing interface is also available.
62 returns the text of the line read. A blank line
63 returns the empty string. If
65 is encountered while reading a line, and the line is empty,
69 is read with a non\-empty line, it is
73 An emacs-style notation is used to denote
74 keystrokes. Control keys are denoted by C\-\fIkey\fR, e.g., C\-n
75 means Control\-N. Similarly,
77 keys are denoted by M\-\fIkey\fR, so M\-x means Meta\-X. (On keyboards
80 key, M\-\fIx\fP means ESC \fIx\fP, i.e., press the Escape key
83 key. This makes ESC the \fImeta prefix\fP.
84 The combination M\-C\-\fIx\fP means ESC\-Control\-\fIx\fP,
85 or press the Escape key
86 then hold the Control key while pressing the
90 Readline commands may be given numeric
92 which normally act as a repeat count. Sometimes, however, it is the
93 sign of the argument that is significant. Passing a negative argument
94 to a command that acts in the forward direction (e.g., \fBkill\-line\fP)
95 causes that command to act in a backward direction. Commands whose
96 behavior with arguments deviates from this are noted.
98 When a command is described as \fIkilling\fP text, the text
99 deleted is saved for possible future retrieval
100 (\fIyanking\fP). The killed text is saved in a
101 \fIkill ring\fP. Consecutive kills cause the text to be
102 accumulated into one unit, which can be yanked all at once.
103 Commands which do not kill text separate the chunks of text
105 .SH INITIALIZATION FILE
107 Readline is customized by putting commands in an initialization
108 file (the \fIinputrc\fP file).
109 The name of this file is taken from the value of the
111 environment variable. If that variable is unset, the default is
113 When a program which uses the readline library starts up, the
114 init file is read, and the key bindings and variables are set.
115 There are only a few basic constructs allowed in the
116 readline init file. Blank lines are ignored.
117 Lines beginning with a \fB#\fP are comments.
118 Lines beginning with a \fB$\fP indicate conditional constructs.
119 Other lines denote key bindings and variable settings.
120 Each program using this library may add its own commands
126 M\-Control\-u: universal\-argument
130 C\-Meta\-u: universal\-argument
134 would make M\-C\-u execute the readline command
135 .IR universal\-argument .
137 The following symbolic character names are recognized while
138 processing key bindings:
150 In addition to command names, readline allows keys to be bound
151 to a string that is inserted when the key is pressed (a \fImacro\fP).
155 The syntax for controlling key bindings in the
157 file is simple. All that is required is the name of the
158 command or the text of a macro and a key sequence to which
159 it should be bound. The name may be specified in one of two ways:
160 as a symbolic key name, possibly with \fIMeta\-\fP or \fIControl\-\fP
161 prefixes, or as a key sequence.
162 When using the form \fBkeyname\fP:\^\fIfunction-name\fP or \fImacro\fP,
164 is the name of a key spelled out in English. For example:
167 Control\-u: universal\-argument
169 Meta\-Rubout: backward\-kill\-word
171 Control\-o: ">&output"
174 In the above example,
176 is bound to the function
177 .BR universal\-argument ,
179 is bound to the function
180 .BR backward\-kill\-word ,
183 is bound to run the macro
184 expressed on the right hand side (that is, to insert the text
188 In the second form, \fB"keyseq"\fP:\^\fIfunction\-name\fP or \fImacro\fP,
192 above in that strings denoting
193 an entire key sequence may be specified by placing the sequence
194 within double quotes. Some GNU Emacs style key escapes can be
195 used, as in the following example.
198 "\eC\-u": universal\-argument
200 "\eC\-x\eC\-r": re\-read\-init\-file
202 "\ee[11~": "Function Key 1"
207 is again bound to the function
208 .BR universal\-argument .
210 is bound to the function
211 .BR re\-read\-init\-file ,
214 is bound to insert the text
215 .BR "Function Key 1" .
216 The full set of GNU Emacs style escape sequences is
240 In addition to the GNU Emacs style escape sequences, a second
241 set of backslash escapes is available:
270 the character whose ASCII code is the octal value \fInnn\fP
271 (one to three digits)
274 the character whose ASCII code is the hexadecimal value \fInnn\fP
275 (one to three digits)
279 When entering the text of a macro, single or double quotes should
280 be used to indicate a macro definition. Unquoted text
281 is assumed to be a function name.
282 In the macro body, the backslash escapes described above are expanded.
283 Backslash will quote any other character in the macro text,
287 allows the current readline key bindings to be displayed or modified
290 builtin command. The editing mode may be switched during interactive
295 builtin command. Other programs using this library provide
296 similar mechanisms. The
298 file may be edited and re-read if a program does not provide
299 any other means to incorporate new bindings.
302 Readline has variables that can be used to further customize its
303 behavior. A variable may be set in the
305 file with a statement of the form
308 \fBset\fP \fIvariable\-name\fP \fIvalue\fP
311 Except where noted, readline variables can take the values
315 The variables and their default values are:
319 .B bell\-style (audible)
320 Controls what happens when readline wants to ring the terminal bell.
321 If set to \fBnone\fP, readline never rings the bell. If set to
322 \fBvisible\fP, readline uses a visible bell if one is available.
323 If set to \fBaudible\fP, readline attempts to ring the terminal's bell.
325 .B comment\-begin (``#'')
326 The string that is inserted in \fBvi\fP mode when the
329 This command is bound to
335 .B completion\-ignore\-case (Off)
336 If set to \fBOn\fP, readline performs filename matching and completion
337 in a case\-insensitive fashion.
339 .B completion\-query\-items (100)
340 This determines when the user is queried about viewing
341 the number of possible completions
342 generated by the \fBpossible\-completions\fP command.
343 It may be set to any integer value greater than or equal to
344 zero. If the number of possible completions is greater than
345 or equal to the value of this variable, the user is asked whether
346 or not he wishes to view them; otherwise they are simply listed
349 .B convert\-meta (On)
350 If set to \fBOn\fP, readline will convert characters with the
351 eighth bit set to an ASCII key sequence
352 by stripping the eighth bit and prepending an
353 escape character (in effect, using escape as the \fImeta prefix\fP).
355 .B disable\-completion (Off)
356 If set to \fBOn\fP, readline will inhibit word completion. Completion
357 characters will be inserted into the line as if they had been
358 mapped to \fBself-insert\fP.
360 .B editing\-mode (emacs)
361 Controls whether readline begins with a set of key bindings similar
362 to \fIemacs\fP or \fIvi\fP.
369 .B enable\-keypad (Off)
370 When set to \fBOn\fP, readline will try to enable the application
371 keypad when it is called. Some systems need this to enable the
374 .B expand\-tilde (Off)
375 If set to \fBon\fP, tilde expansion is performed when readline
376 attempts word completion.
378 .B horizontal\-scroll\-mode (Off)
379 When set to \fBOn\fP, makes readline use a single line for display,
380 scrolling the input horizontally on a single screen line when it
381 becomes longer than the screen width rather than wrapping to a new line.
384 Set the current readline keymap. The set of legal keymap names is
385 \fIemacs, emacs-standard, emacs-meta, emacs-ctlx, vi, vi-move,
388 \fIvi\fP is equivalent to \fIvi-command\fP; \fIemacs\fP is
389 equivalent to \fIemacs-standard\fP. The default value is
393 also affects the default keymap.
395 .B mark\-directories (On)
396 If set to \fBOn\fP, complete<d directory names have a slash
399 .B mark\-modified\-lines (Off)
400 If set to \fBOn\fP, history lines that have been modified are displayed
401 with a preceding asterisk (\fB*\fP).
404 If set to \fBOn\fP, readline will enable eight-bit input (that is,
405 it will not strip the high bit from the characters it reads),
406 regardless of what the terminal claims it can support.
408 .B output\-meta (Off)
409 If set to \fBOn\fP, readline will display characters with the
410 eighth bit set directly rather than as a meta-prefixed escape
413 .B print\-completions\-horizontally (Off)
414 If set to \fBOn\fP, readline will display completions with matches
415 sorted horizontally in alphabetical order, rather than down the screen.
417 .B show\-all\-if\-ambiguous (Off)
418 This alters the default behavior of the completion functions. If
421 words which have more than one possible completion cause the
422 matches to be listed immediately instead of ringing the bell.
424 .B visible\-stats (Off)
425 If set to \fBOn\fP, a character denoting a file's type as reported
426 by \fBstat\fP(2) is appended to the filename when listing possible
429 .SS Conditional Constructs
431 Readline implements a facility similar in spirit to the conditional
432 compilation features of the C preprocessor which allows key
433 bindings and variable settings to be performed as the result
434 of tests. There are four parser directives used.
438 construct allows bindings to be made based on the
439 editing mode, the terminal being used, or the application using
440 readline. The text of the test extends to the end of the line;
441 no characters are required to isolate it.
444 The \fBmode=\fP form of the \fB$if\fP directive is used to test
445 whether readline is in emacs or vi mode.
446 This may be used in conjunction
447 with the \fBset keymap\fP command, for instance, to set bindings in
448 the \fIemacs-standard\fP and \fIemacs-ctlx\fP keymaps only if
449 readline is starting out in emacs mode.
451 The \fBterm=\fP form may be used to include terminal-specific
452 key bindings, perhaps to bind the key sequences output by the
453 terminal's function keys. The word on the right side of the
455 is tested against the full name of the terminal and the portion
456 of the terminal name before the first \fB\-\fP. This allows
463 .IP \fBapplication\fP
464 The \fBapplication\fP construct is used to include
465 application-specific settings. Each program using the readline
466 library sets the \fIapplication name\fP, and an initialization
467 file can test for a particular value.
468 This could be used to bind key sequences to functions useful for
469 a specific program. For instance, the following command adds a
470 key sequence that quotes the current or previous word in Bash:
475 # Quote the current or previous word
476 "\eC-xq": "\eeb\e"\eef\e""
482 This command, as seen in the previous example, terminates an
485 Commands in this branch of the \fB$if\fP directive are executed if
488 This directive takes a single filename as an argument and reads commands
489 and bindings from that file. For example, the following directive
490 would read \fI/etc/inputrc\fP:
494 \fB$include\fP \^ \fI/etc/inputrc\fP
499 Readline provides commands for searching through the command history
500 for lines containing a specified string.
501 There are two search modes:
504 .IR non-incremental .
506 Incremental searches begin before the user has finished typing the
508 As each character of the search string is typed, readline displays
509 the next entry from the history matching the string typed so far.
510 An incremental search requires only as many characters as needed to
511 find the desired history entry.
512 The Escape character is used to terminate an incremental search.
513 Control-J will also terminate the search.
514 Control-G will abort an incremental search and restore the original
516 When the search is terminated, the history entry containing the
517 search string becomes the current line.
518 To find other matching entries in the history list, type Control-S or
519 Control-R as appropriate.
520 This will search backward or forward in the history for the next
521 line matching the search string typed so far.
522 Any other key sequence bound to a readline command will terminate
523 the search and execute that command.
524 For instance, a \fInewline\fP will terminate the search and accept
525 the line, thereby executing the command from the history list.
527 Non-incremental searches read the entire search string before starting
528 to search for matching history lines. The search string may be
529 typed by the user or be part of the contents of the current line.
532 The following is a list of the names of the commands and the default
533 key sequences to which they are bound.
534 Command names without an accompanying key sequence are unbound by default.
535 .SS Commands for Moving
539 .B beginning\-of\-line (C\-a)
540 Move to the start of the current line.
542 .B end\-of\-line (C\-e)
543 Move to the end of the line.
545 .B forward\-char (C\-f)
546 Move forward a character.
548 .B backward\-char (C\-b)
549 Move back a character.
551 .B forward\-word (M\-f)
552 Move forward to the end of the next word. Words are composed of
553 alphanumeric characters (letters and digits).
555 .B backward\-word (M\-b)
556 Move back to the start of this, or the previous, word. Words are
557 composed of alphanumeric characters (letters and digits).
559 .B clear\-screen (C\-l)
560 Clear the screen leaving the current line at the top of the screen.
561 With an argument, refresh the current line without clearing the
564 .B redraw\-current\-line
565 Refresh the current line.
567 .SS Commands for Manipulating the History
571 .B accept\-line (Newline, Return)
572 Accept the line regardless of where the cursor is. If this line is
573 non-empty, add it to the history list. If the line is a modified
574 history line, then restore the history line to its original state.
576 .B previous\-history (C\-p)
577 Fetch the previous command from the history list, moving back in
580 .B next\-history (C\-n)
581 Fetch the next command from the history list, moving forward in the
584 .B beginning\-of\-history (M\-<)
585 Move to the first line in the history.
587 .B end\-of\-history (M\->)
588 Move to the end of the input history, i.e., the line currently being
591 .B reverse\-search\-history (C\-r)
592 Search backward starting at the current line and moving `up' through
593 the history as necessary. This is an incremental search.
595 .B forward\-search\-history (C\-s)
596 Search forward starting at the current line and moving `down' through
597 the history as necessary. This is an incremental search.
599 .B non\-incremental\-reverse\-search\-history (M\-p)
600 Search backward through the history starting at the current line
601 using a non-incremental search for a string supplied by the user.
603 .B non\-incremental\-forward\-search\-history (M\-n)
604 Search forward through the history using a non-incremental search
605 for a string supplied by the user.
607 .B history\-search\-forward
608 Search forward through the history for the string of characters
609 between the start of the current line and the current cursor
610 position (the \fIpoint\fP).
611 This is a non-incremental search.
613 .B history\-search\-backward
614 Search backward through the history for the string of characters
615 between the start of the current line and the point.
616 This is a non-incremental search.
618 .B yank\-nth\-arg (M\-C\-y)
619 Insert the first argument to the previous command (usually
620 the second word on the previous line) at point (the current
621 cursor position). With an argument
623 insert the \fIn\fPth word from the previous command (the words
624 in the previous command begin with word 0). A negative argument
625 inserts the \fIn\fPth word from the end of the previous command.
628 yank\-last\-arg (M\-.\^, M\-_\^)
629 Insert the last argument to the previous command (the last word of
630 the previous history entry). With an argument,
631 behave exactly like \fByank\-nth\-arg\fP.
632 Successive calls to \fByank\-last\-arg\fP move back through the history
633 list, inserting the last argument of each line in turn.
635 .SS Commands for Changing Text
639 .B delete\-char (C\-d)
640 Delete the character under the cursor. If point is at the
641 beginning of the line, there are no characters in the line, and
642 the last character typed was not bound to \fBBdelete\-char\fP, then return
646 .B backward\-delete\-char (Rubout)
647 Delete the character behind the cursor. When given a numeric argument,
648 save the deleted text on the kill ring.
650 .B quoted\-insert (C\-q, C\-v)
651 Add the next character that you type to the line verbatim. This is
652 how to insert characters like \fBC\-q\fP, for example.
654 .B tab\-insert (M-TAB)
655 Insert a tab character.
657 .B self\-insert (a,\ b,\ A,\ 1,\ !,\ ...)
658 Insert the character typed.
660 .B transpose\-chars (C\-t)
661 Drag the character before point forward over the character at point.
662 Point moves forward as well. If point is at the end of the line, then
663 transpose the two characters before point. Negative arguments don't work.
665 .B transpose\-words (M\-t)
666 Drag the word behind the cursor past the word in front of the cursor
667 moving the cursor over that word as well.
669 .B upcase\-word (M\-u)
670 Uppercase the current (or following) word. With a negative argument,
671 uppercase the previous word, but do not move point.
673 .B downcase\-word (M\-l)
674 Lowercase the current (or following) word. With a negative argument,
675 lowercase the previous word, but do not move point.
677 .B capitalize\-word (M\-c)
678 Capitalize the current (or following) word. With a negative argument,
679 capitalize the previous word, but do not move point.
681 .SS Killing and Yanking
686 Kill the text from the current cursor position to the end of the line.
688 .B backward\-kill\-line (C\-x Rubout)
689 Kill backward to the beginning of the line.
691 .B unix\-line\-discard (C\-u)
692 Kill backward from point to the beginning of the line.
693 The killed text is saved on the kill-ring.
694 .\" There is no real difference between this and backward-kill-line
697 Kill all characters on the current line, no matter where the
701 Kill from the cursor to the end of the current word, or if between
702 words, to the end of the next word. Word boundaries are the same as
703 those used by \fBforward\-word\fP.
705 .B backward\-kill\-word (M\-Rubout)
706 Kill the word behind the cursor. Word boundaries are the same as
707 those used by \fBbackward\-word\fP.
709 .B unix\-word\-rubout (C\-w)
710 Kill the word behind the cursor, using white space as a word boundary.
711 The word boundaries are different from
712 .BR backward\-kill\-word .
714 .B delete\-horizontal\-space (M\-\e)
715 Delete all spaces and tabs around point.
718 Kill the text between the point and \fImark\fP (saved cursor position).
719 This text is referred to as the \fIregion\fP.
721 .B copy\-region\-as\-kill
722 Copy the text in the region to the kill buffer.
724 .B copy\-backward\-word
725 Copy the word before point to the kill buffer.
726 The word boundaries are the same as \fBbackward\-word\fP.
728 .B copy\-forward\-word
729 Copy the word following point to the kill buffer.
730 The word boundaries are the same as \fBforward\-word\fP.
733 Yank the top of the kill ring into the buffer at the cursor.
736 Rotate the kill ring, and yank the new top. Only works following
741 .SS Numeric Arguments
745 .B digit\-argument (M\-0, M\-1, ..., M\-\-)
746 Add this digit to the argument already accumulating, or start a new
747 argument. M\-\- starts a negative argument.
749 .B universal\-argument
750 This is another way to specify an argument.
751 If this command is followed by one or more digits, optionally with a
752 leading minus sign, those digits define the argument.
753 If the command is followed by digits, executing
754 .B universal\-argument
755 again ends the numeric argument, but is otherwise ignored.
756 As a special case, if this command is immediately followed by a
757 character that is neither a digit or minus sign, the argument count
758 for the next command is multiplied by four.
759 The argument count is initially one, so executing this function the
760 first time makes the argument count four, a second time makes the
761 argument count sixteen, and so on.
768 Attempt to perform completion on the text before point.
769 The actual completion performed is application-specific.
771 for instance, attempts completion treating the text as a variable
772 (if the text begins with \fB$\fP), username (if the text begins with
773 \fB~\fP), hostname (if the text begins with \fB@\fP), or
774 command (including aliases and functions) in turn. If none
775 of these produces a match, filename completion is attempted.
778 allows completion of program functions and variables, and
779 only attempts filename completion under certain circumstances.
781 .B possible\-completions (M\-?)
782 List the possible completions of the text before point.
784 .B insert\-completions (M\-*)
785 Insert all completions of the text before point
786 that would have been generated by
787 \fBpossible\-completions\fP.
790 Similar to \fBcomplete\fP, but replaces the word to be completed
791 with a single match from the list of possible completions.
792 Repeated execution of \fBmenu\-complete\fP steps through the list
793 of possible completions, inserting each match in turn.
794 At the end of the list of completions, the bell is rung and the
795 original text is restored.
796 An argument of \fIn\fP moves \fIn\fP positions forward in the list
797 of matches; a negative argument may be used to move backward
799 This command is intended to be bound to \fBTAB\fP, but is unbound
806 .B start\-kbd\-macro (C\-x (\^)
807 Begin saving the characters typed into the current keyboard macro.
809 .B end\-kbd\-macro (C\-x )\^)
810 Stop saving the characters typed into the current keyboard macro
811 and store the definition.
813 .B call\-last\-kbd\-macro (C\-x e)
814 Re-execute the last keyboard macro defined, by making the characters
815 in the macro appear as if typed at the keyboard.
821 .B re\-read\-init\-file (C\-x C\-r)
822 Read in the contents of the \fIinputrc\fP file, and incorporate
823 any bindings or variable assignments found there.
826 Abort the current editing command and
827 ring the terminal's bell (subject to the setting of
830 .B do\-uppercase\-version (M\-a, M\-b, M\-\fIx\fP, ...)
831 If the metafied character \fIx\fP is lowercase, run the command
832 that is bound to the corresponding uppercase character.
834 .B prefix\-meta (ESC)
835 Metafy the next character typed.
842 .B undo (C\-_, C\-x C\-u)
843 Incremental undo, separately remembered for each line.
845 .B revert\-line (M\-r)
846 Undo all changes made to this line. This is like executing the
848 command enough times to return the line to its initial state.
850 .B tilde\-expand (M\-~)
851 Perform tilde expansion on the current word.
853 .B set\-mark (C\-@, M-<space>)
854 Set the mark to the current point. If a
855 numeric argument is supplied, the mark is set to that position.
857 .B exchange\-point\-and\-mark (C\-x C\-x)
858 Swap the point with the mark. The current cursor position is set to
859 the saved position, and the old cursor position is saved as the mark.
861 .B character\-search (C\-])
862 A character is read and point is moved to the next occurrence of that
863 character. A negative count searches for previous occurrences.
865 .B character\-search\-backward (M\-C\-])
866 A character is read and point is moved to the previous occurrence of that
867 character. A negative count searches for subsequent occurrences.
869 .B insert\-comment (M\-#)
870 The value of the readline
872 variable is inserted at the beginning of the current line, and the line
873 is accepted as if a newline had been typed. This makes the current line
877 Print all of the functions and their key bindings to the
878 readline output stream. If a numeric argument is supplied,
879 the output is formatted in such a way that it can be made part
880 of an \fIinputrc\fP file.
883 Print all of the settable variables and their values to the
884 readline output stream. If a numeric argument is supplied,
885 the output is formatted in such a way that it can be made part
886 of an \fIinputrc\fP file.
889 Print all of the readline key sequences bound to macros and the
890 strings they ouput. If a numeric argument is supplied,
891 the output is formatted in such a way that it can be made part
892 of an \fIinputrc\fP file.
894 .B emacs\-editing\-mode (C\-e)
897 editing mode, this causes a switch to
901 .B vi\-editing\-mode (M\-C\-j)
904 editing mode, this causes a switch to
908 .SH DEFAULT KEY BINDINGS
910 The following is a list of the default emacs and vi bindings.
911 Characters with the 8th bit set are written as M\-<character>, and
915 The printable ASCII characters not mentioned in the list of emacs
916 standard bindings are bound to the
918 function, which just inserts the given character into the input line.
919 In vi insertion mode, all characters not specifically mentioned are
922 Characters assigned to signal generation by
924 or the terminal driver, such as C-Z or C-C,
925 retain that function.
928 characters are bound to the same function in the emacs mode
930 The remaining characters are unbound, which causes readline
931 to ring the bell (subject to the setting of the
939 Emacs Standard bindings
942 "C-A" beginning-of-line
948 "C-H" backward-delete-char
955 "C-P" previous-history
957 "C-R" reverse-search-history
958 "C-S" forward-search-history
959 "C-T" transpose-chars
960 "C-U" unix-line-discard
962 "C-W" unix-word-rubout
964 "C-]" character-search
966 "\^ " to "/" self-insert
967 "0" to "9" self-insert
968 ":" to "~" self-insert
969 "C-?" backward-delete-char
974 "M-C-H" backward-kill-word
976 "M-C-J" vi-editing-mode
977 "M-C-M" vi-editing-mode
981 "M-C-]" character-search-backward
985 "M-*" insert-completions
998 "M-<" beginning-of-history
999 "M-=" possible-completions
1000 "M->" end-of-history
1001 "M-?" possible-completions
1003 "M-C" capitalize-word
1007 "M-N" non-incremental-forward-search-history
1008 "M-P" non-incremental-reverse-search-history
1010 "M-T" transpose-words
1013 "M-\e" delete-horizontal-space
1015 "M-C-?" backward-delete-word
1018 Emacs Control-X bindings
1021 "C-XC-R" re-read-init-file
1023 "C-XC-X" exchange-point-and-mark
1024 "C-X(" start-kbd-macro
1025 "C-X)" end-kbd-macro
1026 "C-XE" call-last-kbd-macro
1027 "C-XC-?" backward-kill-line
1030 .SS VI Mode bindings
1036 VI Insert Mode functions
1039 "C-H" backward-delete-char
1043 "C-R" reverse-search-history
1044 "C-S" forward-search-history
1045 "C-T" transpose-chars
1046 "C-U" unix-line-discard
1048 "C-W" unix-word-rubout
1050 "C-[" vi-movement-mode
1052 "\^ " to "~" self-insert
1053 "C-?" backward-delete-char
1055 VI Command Mode functions
1058 "C-E" emacs-editing-mode
1066 "C-P" previous-history
1068 "C-R" reverse-search-history
1069 "C-S" forward-search-history
1070 "C-T" transpose-chars
1071 "C-U" unix-line-discard
1073 "C-W" unix-word-rubout
1083 "-" previous-history
1086 "0" beginning-of-line
1087 "1" to "9" vi-arg-digit
1097 "G" vi-fetch-history
1106 "X" backward-delete-char
1119 "i" vi-insertion-mode
1139 \fIThe Gnu Readline Library\fP, Brian Fox and Chet Ramey
1141 \fIThe Gnu History Library\fP, Brian Fox and Chet Ramey
1149 Individual \fBreadline\fP initialization file
1152 Brian Fox, Free Software Foundation (primary author)
1156 Chet Ramey, Case Western Reserve University
1160 If you find a bug in
1162 you should report it. But first, you should
1163 make sure that it really is a bug, and that it appears in the latest
1166 library that you have.
1168 Once you have determined that a bug actually exists, mail a
1169 bug report to \fIbug\-readline\fP@\fIgnu.org\fP.
1170 If you have a fix, you are welcome to mail that
1171 as well! Suggestions and `philosophical' bug reports may be mailed
1172 to \fPbug-readline\fP@\fIgnu.org\fP or posted to the Usenet
1176 Comments and bug reports concerning
1177 this manual page should be directed to
1178 .IR chet@ins.CWRU.Edu .
1181 It's too big and too slow.
projects / platform / upstream / bash.git / blob