diff options
Diffstat (limited to 'readline/doc/rluserman.info')
| -rw-r--r-- | readline/doc/rluserman.info | 756 |
1 files changed, 621 insertions, 135 deletions
diff --git a/readline/doc/rluserman.info b/readline/doc/rluserman.info index 3fccbd4e272..a58234e28e8 100644 --- a/readline/doc/rluserman.info +++ b/readline/doc/rluserman.info @@ -1,30 +1,33 @@ -This is rluserman.info, produced by makeinfo version 4.1 from -/usr/homes/chet/src/bash/readline-src/doc/rluserman.texinfo. +This is rluserman.info, produced by makeinfo version 4.7 from +/Users/chet/src/bash/readline-src/doc/rluserman.texi. -INFO-DIR-SECTION Libraries -START-INFO-DIR-ENTRY -* RLuserman: (rluserman). The GNU readline library User's Manual. -END-INFO-DIR-ENTRY + This manual describes the end user interface of the GNU Readline +Library (version 5.1-beta1, 11 November 2005), a library which aids in +the consistency of user interface across discrete programs which provide +a command line interface. - This document describes the end user interface of the GNU Readline -Library, a utility which aids in the consistency of user interface -across discrete programs that need to provide a command line interface. - - Copyright (C) 1988-2002 Free Software Foundation, Inc. + Copyright (C) 1988-2005 Free Software Foundation, Inc. Permission is granted to make and distribute verbatim copies of this -manual provided the copyright notice and this permission notice pare +manual provided the copyright notice and this permission notice are preserved on all copies. - Permission is granted to copy and distribute modified versions of -this manual under the conditions for verbatim copying, provided that -the entire resulting derived work is distributed under the terms of a -permission notice identical to this one. + Permission is granted to copy, distribute and/or modify this + document under the terms of the GNU Free Documentation License, + Version 1.1 or any later version published by the Free Software + Foundation; with no Invariant Sections, with the Front-Cover texts + being "A GNU Manual," and with the Back-Cover Texts as in (a) + below. A copy of the license is included in the section entitled + "GNU Free Documentation License." - Permission is granted to copy and distribute translations of this -manual into another language, under the above conditions for modified -versions, except that this permission notice may be stated in a -translation approved by the Free Software Foundation. + (a) The FSF's Back-Cover Text is: "You have freedom to copy and + modify this GNU Manual, like GNU software. Copies published by + the Free Software Foundation raise funds for GNU development." + +INFO-DIR-SECTION Libraries +START-INFO-DIR-ENTRY +* RLuserman: (rluserman). The GNU readline library User's Manual. +END-INFO-DIR-ENTRY File: rluserman.info, Node: Top, Next: Command Line Editing, Up: (dir) @@ -32,21 +35,22 @@ File: rluserman.info, Node: Top, Next: Command Line Editing, Up: (dir) GNU Readline Library ******************** - This document describes the end user interface of the GNU Readline +This document describes the end user interface of the GNU Readline Library, a utility which aids in the consistency of user interface -across discrete programs that need to provide a command line interface. +across discrete programs which provide a command line interface. * Menu: * Command Line Editing:: GNU Readline User's Manual. +* Copying This Manual:: Copying This Manual. -File: rluserman.info, Node: Command Line Editing, Prev: Top, Up: Top +File: rluserman.info, Node: Command Line Editing, Next: Copying This Manual, Prev: Top, Up: Top -Command Line Editing -******************** +1 Command Line Editing +********************** - This chapter describes the basic features of the GNU command line +This chapter describes the basic features of the GNU command line editing interface. * Menu: @@ -62,10 +66,10 @@ editing interface. File: rluserman.info, Node: Introduction and Notation, Next: Readline Interaction, Up: Command Line Editing -Introduction to Line Editing -============================ +1.1 Introduction to Line Editing +================================ - The following paragraphs describe the notation used to represent +The following paragraphs describe the notation used to represent keystrokes. The text `C-k' is read as `Control-K' and describes the character @@ -98,10 +102,10 @@ some keyboards. File: rluserman.info, Node: Readline Interaction, Next: Readline Init File, Prev: Introduction and Notation, Up: Command Line Editing -Readline Interaction -==================== +1.2 Readline Interaction +======================== - Often during an interactive session you type in a long line of text, +Often during an interactive session you type in a long line of text, only to notice that the first word on the line is misspelled. The Readline library gives you a set of commands for manipulating the text as you type it in, allowing you to just fix your typo, and not forcing @@ -123,13 +127,13 @@ location of the cursor within the line. File: rluserman.info, Node: Readline Bare Essentials, Next: Readline Movement Commands, Up: Readline Interaction -Readline Bare Essentials ------------------------- +1.2.1 Readline Bare Essentials +------------------------------ - In order to enter characters into the line, simply type them. The -typed character appears where the cursor was, and then the cursor moves -one space to the right. If you mistype a character, you can use your -erase character to back up and delete the mistyped character. +In order to enter characters into the line, simply type them. The typed +character appears where the cursor was, and then the cursor moves one +space to the right. If you mistype a character, you can use your erase +character to back up and delete the mistyped character. Sometimes you may mistype a character, and not notice the error until you have typed several other characters. In that case, you can @@ -171,10 +175,10 @@ character to the left of the cursor.) File: rluserman.info, Node: Readline Movement Commands, Next: Readline Killing Commands, Prev: Readline Bare Essentials, Up: Readline Interaction -Readline Movement Commands --------------------------- +1.2.2 Readline Movement Commands +-------------------------------- - The above table describes the most basic keystrokes that you need in +The above table describes the most basic keystrokes that you need in order to do editing of the input line. For your convenience, many other commands have been added in addition to `C-b', `C-f', `C-d', and <DEL>. Here are some commands for moving more rapidly about the line. @@ -202,11 +206,11 @@ operate on characters while meta keystrokes operate on words. File: rluserman.info, Node: Readline Killing Commands, Next: Readline Arguments, Prev: Readline Movement Commands, Up: Readline Interaction -Readline Killing Commands -------------------------- +1.2.3 Readline Killing Commands +------------------------------- - "Killing" text means to delete the text from the line, but to save -it away for later use, usually by "yanking" (re-inserting) it back into +"Killing" text means to delete the text from the line, but to save it +away for later use, usually by "yanking" (re-inserting) it back into the line. (`Cut' and `paste' are more recent jargon for `kill' and `yank'.) @@ -218,7 +222,7 @@ place later. Any number of consecutive kills save all of the killed text together, so that when you yank it back, you get it all. The kill ring is not line specific; the text that you killed on a previously typed line is -available to be yanked back later, when you are typing another line. +available to be yanked back later, when you are typing another line. Here is the list of commands for killing text. @@ -240,6 +244,7 @@ available to be yanked back later, when you are typing another line. Kill from the cursor to the previous whitespace. This is different than `M-<DEL>' because the word boundaries differ. + Here is how to "yank" the text back into the line. Yanking means to copy the most-recently-killed text from the kill buffer. @@ -254,10 +259,10 @@ copy the most-recently-killed text from the kill buffer. File: rluserman.info, Node: Readline Arguments, Next: Searching, Prev: Readline Killing Commands, Up: Readline Interaction -Readline Arguments ------------------- +1.2.4 Readline Arguments +------------------------ - You can pass numeric arguments to Readline commands. Sometimes the +You can pass numeric arguments to Readline commands. Sometimes the argument acts as a repeat count, other times it is the sign of the argument that is significant. If you pass a negative argument to a command which normally acts in a forward direction, that command will @@ -275,10 +280,10 @@ will delete the next ten characters on the input line. File: rluserman.info, Node: Searching, Prev: Readline Arguments, Up: Readline Interaction -Searching for Commands in the History -------------------------------------- +1.2.5 Searching for Commands in the History +------------------------------------------- - Readline provides commands for searching through the command history +Readline provides commands for searching through the command history for lines containing a specified string. There are two search modes: "incremental" and "non-incremental". @@ -316,10 +321,10 @@ typed by the user or be part of the contents of the current line. File: rluserman.info, Node: Readline Init File, Next: Bindable Readline Commands, Prev: Readline Interaction, Up: Command Line Editing -Readline Init File -================== +1.3 Readline Init File +====================== - Although the Readline library comes with a set of Emacs-like +Although the Readline library comes with a set of Emacs-like keybindings installed by default, it is possible to use a different set of keybindings. Any user can customize programs that use Readline by putting commands in an "inputrc" file, conventionally in his home @@ -344,10 +349,10 @@ incorporating any changes that you might have made to it. File: rluserman.info, Node: Readline Init File Syntax, Next: Conditional Init Constructs, Up: Readline Init File -Readline Init File Syntax -------------------------- +1.3.1 Readline Init File Syntax +------------------------------- - There are only a few basic constructs allowed in the Readline init +There are only a few basic constructs allowed in the Readline init file. Blank lines are ignored. Lines beginning with a `#' are comments. Lines beginning with a `$' indicate conditional constructs (*note Conditional Init Constructs::). Other lines denote variable @@ -366,7 +371,11 @@ Variable Settings set editing-mode vi Variable names and values, where appropriate, are recognized - without regard to case. + without regard to case. Unrecognized variable names are ignored. + + Boolean variables (those that can be set to on or off) are set to + on if the value is null or empty, ON (case-insensitive), or 1. + Any other value results in the variable being set to off. A great deal of run-time behavior is changeable with the following variables. @@ -378,6 +387,11 @@ Variable Settings one is available. If set to `audible' (the default), Readline attempts to ring the terminal's bell. + `bind-tty-special-chars' + If set to `on', Readline attempts to bind the control + characters treated specially by the kernel's terminal driver + to their Readline equivalents. + `comment-begin' The string to insert at the beginning of the line when the `insert-comment' command is executed. The default value is @@ -390,12 +404,13 @@ Variable Settings `completion-query-items' The number of possible completions that determines when the - user is asked whether he wants to see the list of - possibilities. If the number of possible completions is - greater than this value, Readline will ask the user whether - or not he wishes to view them; otherwise, they are simply - listed. This variable must be set to an integer value - greater than or equal to 0. The default limit is `100'. + user is asked whether the list of possibilities should be + displayed. If the number of possible completions is greater + than this value, Readline will ask the user whether or not he + wishes to view them; otherwise, they are simply listed. This + variable must be set to an integer value greater than or + equal to 0. A negative value means Readline should never ask. + The default limit is `100'. `convert-meta' If set to `on', Readline will convert characters with the @@ -423,9 +438,10 @@ Variable Settings If set to `on', tilde expansion is performed when Readline attempts word completion. The default is `off'. + `history-preserve-point' If set to `on', the history code attempts to place point at - the same location on each history line retrived with - `previous-history' or `next-history'. + the same location on each history line retrieved with + `previous-history' or `next-history'. The default is `off'. `horizontal-scroll-mode' This variable can be set to either `on' or `off'. Setting it @@ -499,11 +515,21 @@ Variable Settings completion cause the matches to be listed immediately instead of ringing the bell. The default value is `off'. + `show-all-if-unmodified' + This alters the default behavior of the completion functions + in a fashion similar to SHOW-ALL-IF-AMBIGUOUS. If set to + `on', words which have more than one possible completion + without any possible partial completion (the possible + completions don't share a common prefix) cause the matches to + be listed immediately instead of ringing the bell. The + default value is `off'. + `visible-stats' If set to `on', a character denoting a file's type is appended to the filename when listing possible completions. The default is `off'. + Key Bindings The syntax for controlling key bindings in the init file is simple. First you need to find the name of the command that you @@ -554,6 +580,7 @@ Key Bindings `<ESC> <[> <1> <1> <~>' is bound to insert the text `Function Key 1'. + The following GNU Emacs style escape sequences are available when specifying key sequences: @@ -619,13 +646,14 @@ Key Bindings the line: "\C-x\\": "\\" + File: rluserman.info, Node: Conditional Init Constructs, Next: Sample Init File, Prev: Readline Init File Syntax, Up: Readline Init File -Conditional Init Constructs ---------------------------- +1.3.2 Conditional Init Constructs +--------------------------------- - Readline implements a facility similar in spirit to the conditional +Readline implements a facility similar in spirit to the conditional compilation features of the C preprocessor which allows key bindings and variable settings to be performed as the result of tests. There are four parser directives used. @@ -682,11 +710,11 @@ are four parser directives used. File: rluserman.info, Node: Sample Init File, Prev: Conditional Init Constructs, Up: Readline Init File -Sample Init File ----------------- +1.3.3 Sample Init File +---------------------- - Here is an example of an INPUTRC file. This illustrates key -binding, variable assignment, and conditional syntax. +Here is an example of an INPUTRC file. This illustrates key binding, +variable assignment, and conditional syntax. # This file controls the behaviour of line input editing for @@ -699,16 +727,16 @@ binding, variable assignment, and conditional syntax. # First, include any systemwide bindings and variable # assignments from /etc/Inputrc $include /etc/Inputrc - + # # Set various bindings for emacs mode. - + set editing-mode emacs - + $if mode=emacs - + Meta-Control-h: backward-kill-word Text after the function name is ignored - + # # Arrow keys in keypad mode # @@ -737,14 +765,14 @@ binding, variable assignment, and conditional syntax. #"\M-\C-[C": forward-char #"\M-\C-[A": previous-history #"\M-\C-[B": next-history - + C-q: quoted-insert - + $endif - + # An old-style binding. This happens to be the default. TAB: complete - + # Macros that are convenient for shell interaction $if Bash # edit the path @@ -763,25 +791,25 @@ binding, variable assignment, and conditional syntax. # Edit variable on current line. "\M-\C-v": "\C-a\C-k$\C-y\M-\C-e\C-a\C-y=" $endif - + # use a visible bell if one is available set bell-style visible - + # don't strip characters to 7 bits when reading set input-meta on - + # allow iso-latin1 characters to be inserted rather # than converted to prefix-meta sequences set convert-meta off - + # display characters with the eighth bit set directly # rather than as meta-prefixed characters set output-meta on - + # if there are more than 150 possible completions for # a word, ask the user if he wants to see all of them set completion-query-items 150 - + # For FTP $if Ftp "\C-xg": "get \M-?" @@ -792,8 +820,8 @@ binding, variable assignment, and conditional syntax. File: rluserman.info, Node: Bindable Readline Commands, Next: Readline vi Mode, Prev: Readline Init File, Up: Command Line Editing -Bindable Readline Commands -========================== +1.4 Bindable Readline Commands +============================== * Menu: @@ -818,8 +846,8 @@ as the "region". File: rluserman.info, Node: Commands For Moving, Next: Commands For History, Up: Bindable Readline Commands -Commands For Moving -------------------- +1.4.1 Commands For Moving +------------------------- `beginning-of-line (C-a)' Move to the start of the current line. @@ -848,11 +876,12 @@ Commands For Moving `redraw-current-line ()' Refresh the current line. By default, this is unbound. + File: rluserman.info, Node: Commands For History, Next: Commands For Text, Prev: Commands For Moving, Up: Bindable Readline Commands -Commands For Manipulating The History -------------------------------------- +1.4.2 Commands For Manipulating The History +------------------------------------------- `accept-line (Newline or Return)' Accept the line regardless of where the cursor is. If this line is @@ -908,20 +937,24 @@ Commands For Manipulating The History second word on the previous line) at point. With an argument N, insert the Nth word from the previous command (the words in the previous command begin with word 0). A negative argument inserts - the Nth word from the end of the previous command. + the Nth word from the end of the previous command. Once the + argument N is computed, the argument is extracted as if the `!N' + history expansion had been specified. `yank-last-arg (M-. or M-_)' Insert last argument to the previous command (the last word of the previous history entry). With an argument, behave exactly like `yank-nth-arg'. Successive calls to `yank-last-arg' move back through the history list, inserting the last argument of each line - in turn. + in turn. The history expansion facilities are used to extract the + last argument, as if the `!$' history expansion had been specified. + File: rluserman.info, Node: Commands For Text, Next: Commands For Killing, Prev: Commands For History, Up: Bindable Readline Commands -Commands For Changing Text --------------------------- +1.4.3 Commands For Changing Text +-------------------------------- `delete-char (C-d)' Delete the character at point. If point is at the beginning of @@ -984,11 +1017,12 @@ Commands For Changing Text By default, this command is unbound. + File: rluserman.info, Node: Commands For Killing, Next: Numeric Arguments, Prev: Commands For Text, Up: Bindable Readline Commands -Killing And Yanking -------------------- +1.4.4 Killing And Yanking +------------------------- `kill-line (C-k)' Kill the text from point to the end of the line. @@ -1016,6 +1050,11 @@ Killing And Yanking Kill the word behind point, using white space as a word boundary. The killed text is saved on the kill-ring. +`unix-filename-rubout ()' + Kill the word behind point, using white space and the slash + character as the word boundaries. The killed text is saved on the + kill-ring. + `delete-horizontal-space ()' Delete all spaces and tabs around point. By default, this is unbound. @@ -1048,8 +1087,8 @@ Killing And Yanking File: rluserman.info, Node: Numeric Arguments, Next: Commands For Completion, Prev: Commands For Killing, Up: Bindable Readline Commands -Specifying Numeric Arguments ----------------------------- +1.4.5 Specifying Numeric Arguments +---------------------------------- `digit-argument (M-0, M-1, ... M--)' Add this digit to the argument already accumulating, or start a new @@ -1071,8 +1110,8 @@ Specifying Numeric Arguments File: rluserman.info, Node: Commands For Completion, Next: Keyboard Macros, Prev: Numeric Arguments, Up: Bindable Readline Commands -Letting Readline Type For You ------------------------------ +1.4.6 Letting Readline Type For You +----------------------------------- `complete (<TAB>)' Attempt to perform completion on the text before point. The @@ -1104,11 +1143,12 @@ Letting Readline Type For You behaves identically to `possible-completions'. This command is unbound by default. + File: rluserman.info, Node: Keyboard Macros, Next: Miscellaneous Commands, Prev: Commands For Completion, Up: Bindable Readline Commands -Keyboard Macros ---------------- +1.4.7 Keyboard Macros +--------------------- `start-kbd-macro (C-x ()' Begin saving the characters typed into the current keyboard macro. @@ -1121,11 +1161,12 @@ Keyboard Macros Re-execute the last keyboard macro defined, by making the characters in the macro appear as if typed at the keyboard. + File: rluserman.info, Node: Miscellaneous Commands, Prev: Keyboard Macros, Up: Bindable Readline Commands -Some Miscellaneous Commands ---------------------------- +1.4.8 Some Miscellaneous Commands +--------------------------------- `re-read-init-file (C-x C-r)' Read in the contents of the INPUTRC file, and incorporate any @@ -1208,13 +1249,14 @@ Some Miscellaneous Commands When in `emacs' editing mode, this causes a switch to `vi' editing mode. + File: rluserman.info, Node: Readline vi Mode, Prev: Bindable Readline Commands, Up: Command Line Editing -Readline vi Mode -================ +1.5 Readline vi Mode +==================== - While the Readline library does not have a full set of `vi' editing +While the Readline library does not have a full set of `vi' editing functions, it does contain enough to allow simple editing of the line. The Readline `vi' mode behaves as specified in the POSIX 1003.2 standard. @@ -1230,31 +1272,475 @@ you into `command' mode, where you can edit the text of the line with the standard `vi' movement keys, move to previous history lines with `k' and subsequent lines with `j', and so forth. + +File: rluserman.info, Node: Copying This Manual, Prev: Command Line Editing, Up: Top + +Appendix A Copying This Manual +****************************** + +* Menu: + +* GNU Free Documentation License:: License for copying this manual. + + +File: rluserman.info, Node: GNU Free Documentation License, Up: Copying This Manual + +A.1 GNU Free Documentation License +================================== + + Version 1.2, November 2002 + + Copyright (C) 2000,2001,2002 Free Software Foundation, Inc. + 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA + + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + 0. PREAMBLE + + The purpose of this License is to make a manual, textbook, or other + functional and useful document "free" in the sense of freedom: to + assure everyone the effective freedom to copy and redistribute it, + with or without modifying it, either commercially or + noncommercially. Secondarily, this License preserves for the + author and publisher a way to get credit for their work, while not + being considered responsible for modifications made by others. + + This License is a kind of "copyleft", which means that derivative + works of the document must themselves be free in the same sense. + It complements the GNU General Public License, which is a copyleft + license designed for free software. + + We have designed this License in order to use it for manuals for + free software, because free software needs free documentation: a + free program should come with manuals providing the same freedoms + that the software does. But this License is not limited to + software manuals; it can be used for any textual work, regardless + of subject matter or whether it is published as a printed book. + We recommend this License principally for works whose purpose is + instruction or reference. + + 1. APPLICABILITY AND DEFINITIONS + + This License applies to any manual or other work, in any medium, + that contains a notice placed by the copyright holder saying it + can be distributed under the terms of this License. Such a notice + grants a world-wide, royalty-free license, unlimited in duration, + to use that work under the conditions stated herein. The + "Document", below, refers to any such manual or work. Any member + of the public is a licensee, and is addressed as "you". You + accept the license if you copy, modify or distribute the work in a + way requiring permission under copyright law. + + A "Modified Version" of the Document means any work containing the + Document or a portion of it, either copied verbatim, or with + modifications and/or translated into another language. + + A "Secondary Section" is a named appendix or a front-matter section + of the Document that deals exclusively with the relationship of the + publishers or authors of the Document to the Document's overall + subject (or to related matters) and contains nothing that could + fall directly within that overall subject. (Thus, if the Document + is in part a textbook of mathematics, a Secondary Section may not + explain any mathematics.) The relationship could be a matter of + historical connection with the subject or with related matters, or + of legal, commercial, philosophical, ethical or political position + regarding them. + + The "Invariant Sections" are certain Secondary Sections whose + titles are designated, as being those of Invariant Sections, in + the notice that says that the Document is released under this + License. If a section does not fit the above definition of + Secondary then it is not allowed to be designated as Invariant. + The Document may contain zero Invariant Sections. If the Document + does not identify any Invariant Sections then there are none. + + The "Cover Texts" are certain short passages of text that are + listed, as Front-Cover Texts or Back-Cover Texts, in the notice + that says that the Document is released under this License. A + Front-Cover Text may be at most 5 words, and a Back-Cover Text may + be at most 25 words. + + A "Transparent" copy of the Document means a machine-readable copy, + represented in a format whose specification is available to the + general public, that is suitable for revising the document + straightforwardly with generic text editors or (for images + composed of pixels) generic paint programs or (for drawings) some + widely available drawing editor, and that is suitable for input to + text formatters or for automatic translation to a variety of + formats suitable for input to text formatters. A copy made in an + otherwise Transparent file format whose markup, or absence of + markup, has been arranged to thwart or discourage subsequent + modification by readers is not Transparent. An image format is + not Transparent if used for any substantial amount of text. A + copy that is not "Transparent" is called "Opaque". + + Examples of suitable formats for Transparent copies include plain + ASCII without markup, Texinfo input format, LaTeX input format, + SGML or XML using a publicly available DTD, and + standard-conforming simple HTML, PostScript or PDF designed for + human modification. Examples of transparent image formats include + PNG, XCF and JPG. Opaque formats include proprietary formats that + can be read and edited only by proprietary word processors, SGML or + XML for which the DTD and/or processing tools are not generally + available, and the machine-generated HTML, PostScript or PDF + produced by some word processors for output purposes only. + + The "Title Page" means, for a printed book, the title page itself, + plus such following pages as are needed to hold, legibly, the + material this License requires to appear in the title page. For + works in formats which do not have any title page as such, "Title + Page" means the text near the most prominent appearance of the + work's title, preceding the beginning of the body of the text. + + A section "Entitled XYZ" means a named subunit of the Document + whose title either is precisely XYZ or contains XYZ in parentheses + following text that translates XYZ in another language. (Here XYZ + stands for a specific section name mentioned below, such as + "Acknowledgements", "Dedications", "Endorsements", or "History".) + To "Preserve the Title" of such a section when you modify the + Document means that it remains a section "Entitled XYZ" according + to this definition. + + The Document may include Warranty Disclaimers next to the notice + which states that this License applies to the Document. These + Warranty Disclaimers are considered to be included by reference in + this License, but only as regards disclaiming warranties: any other + implication that these Warranty Disclaimers may have is void and + has no effect on the meaning of this License. + + 2. VERBATIM COPYING + + You may copy and distribute the Document in any medium, either + commercially or noncommercially, provided that this License, the + copyright notices, and the license notice saying this License + applies to the Document are reproduced in all copies, and that you + add no other conditions whatsoever to those of this License. You + may not use technical measures to obstruct or control the reading + or further copying of the copies you make or distribute. However, + you may accept compensation in exchange for copies. If you + distribute a large enough number of copies you must also follow + the conditions in section 3. + + You may also lend copies, under the same conditions stated above, + and you may publicly display copies. + + 3. COPYING IN QUANTITY + + If you publish printed copies (or copies in media that commonly + have printed covers) of the Document, numbering more than 100, and + the Document's license notice requires Cover Texts, you must + enclose the copies in covers that carry, clearly and legibly, all + these Cover Texts: Front-Cover Texts on the front cover, and + Back-Cover Texts on the back cover. Both covers must also clearly + and legibly identify you as the publisher of these copies. The + front cover must present the full title with all words of the + title equally prominent and visible. You may add other material + on the covers in addition. Copying with changes limited to the + covers, as long as they preserve the title of the Document and + satisfy these conditions, can be treated as verbatim copying in + other respects. + + If the required texts for either cover are too voluminous to fit + legibly, you should put the first ones listed (as many as fit + reasonably) on the actual cover, and continue the rest onto + adjacent pages. + + If you publish or distribute Opaque copies of the Document + numbering more than 100, you must either include a + machine-readable Transparent copy along with each Opaque copy, or + state in or with each Opaque copy a computer-network location from + which the general network-using public has access to download + using public-standard network protocols a complete Transparent + copy of the Document, free of added material. If you use the + latter option, you must take reasonably prudent steps, when you + begin distribution of Opaque copies in quantity, to ensure that + this Transparent copy will remain thus accessible at the stated + location until at least one year after the last time you + distribute an Opaque copy (directly or through your agents or + retailers) of that edition to the public. + + It is requested, but not required, that you contact the authors of + the Document well before redistributing any large number of + copies, to give them a chance to provide you with an updated + version of the Document. + + 4. MODIFICATIONS + + You may copy and distribute a Modified Version of the Document + under the conditions of sections 2 and 3 above, provided that you + release the Modified Version under precisely this License, with + the Modified Version filling the role of the Document, thus + licensing distribution and modification of the Modified Version to + whoever possesses a copy of it. In addition, you must do these + things in the Modified Version: + + A. Use in the Title Page (and on the covers, if any) a title + distinct from that of the Document, and from those of + previous versions (which should, if there were any, be listed + in the History section of the Document). You may use the + same title as a previous version if the original publisher of + that version gives permission. + + B. List on the Title Page, as authors, one or more persons or + entities responsible for authorship of the modifications in + the Modified Version, together with at least five of the + principal authors of the Document (all of its principal + authors, if it has fewer than five), unless they release you + from this requirement. + + C. State on the Title page the name of the publisher of the + Modified Version, as the publisher. + + D. Preserve all the copyright notices of the Document. + + E. Add an appropriate copyright notice for your modifications + adjacent to the other copyright notices. + + F. Include, immediately after the copyright notices, a license + notice giving the public permission to use the Modified + Version under the terms of this License, in the form shown in + the Addendum below. + + G. Preserve in that license notice the full lists of Invariant + Sections and required Cover Texts given in the Document's + license notice. + + H. Include an unaltered copy of this License. + + I. Preserve the section Entitled "History", Preserve its Title, + and add to it an item stating at least the title, year, new + authors, and publisher of the Modified Version as given on + the Title Page. If there is no section Entitled "History" in + the Document, create one stating the title, year, authors, + and publisher of the Document as given on its Title Page, + then add an item describing the Modified Version as stated in + the previous sentence. + + J. Preserve the network location, if any, given in the Document + for public access to a Transparent copy of the Document, and + likewise the network locations given in the Document for + previous versions it was based on. These may be placed in + the "History" section. You may omit a network location for a + work that was published at least four years before the + Document itself, or if the original publisher of the version + it refers to gives permission. + + K. For any section Entitled "Acknowledgements" or "Dedications", + Preserve the Title of the section, and preserve in the + section all the substance and tone of each of the contributor + acknowledgements and/or dedications given therein. + + L. Preserve all the Invariant Sections of the Document, + unaltered in their text and in their titles. Section numbers + or the equivalent are not considered part of the section + titles. + + M. Delete any section Entitled "Endorsements". Such a section + may not be included in the Modified Version. + + N. Do not retitle any existing section to be Entitled + "Endorsements" or to conflict in title with any Invariant + Section. + + O. Preserve any Warranty Disclaimers. + + If the Modified Version includes new front-matter sections or + appendices that qualify as Secondary Sections and contain no + material copied from the Document, you may at your option + designate some or all of these sections as invariant. To do this, + add their titles to the list of Invariant Sections in the Modified + Version's license notice. These titles must be distinct from any + other section titles. + + You may add a section Entitled "Endorsements", provided it contains + nothing but endorsements of your Modified Version by various + parties--for example, statements of peer review or that the text + has been approved by an organization as the authoritative + definition of a standard. + + You may add a passage of up to five words as a Front-Cover Text, + and a passage of up to 25 words as a Back-Cover Text, to the end + of the list of Cover Texts in the Modified Version. Only one + passage of Front-Cover Text and one of Back-Cover Text may be + added by (or through arrangements made by) any one entity. If the + Document already includes a cover text for the same cover, + previously added by you or by arrangement made by the same entity + you are acting on behalf of, you may not add another; but you may + replace the old one, on explicit permission from the previous + publisher that added the old one. + + The author(s) and publisher(s) of the Document do not by this + License give permission to use their names for publicity for or to + assert or imply endorsement of any Modified Version. + + 5. COMBINING DOCUMENTS + + You may combine the Document with other documents released under + this License, under the terms defined in section 4 above for + modified versions, provided that you include in the combination + all of the Invariant Sections of all of the original documents, + unmodified, and list them all as Invariant Sections of your + combined work in its license notice, and that you preserve all + their Warranty Disclaimers. + + The combined work need only contain one copy of this License, and + multiple identical Invariant Sections may be replaced with a single + copy. If there are multiple Invariant Sections with the same name + but different contents, make the title of each such section unique + by adding at the end of it, in parentheses, the name of the + original author or publisher of that section if known, or else a + unique number. Make the same adjustment to the section titles in + the list of Invariant Sections in the license notice of the + combined work. + + In the combination, you must combine any sections Entitled + "History" in the various original documents, forming one section + Entitled "History"; likewise combine any sections Entitled + "Acknowledgements", and any sections Entitled "Dedications". You + must delete all sections Entitled "Endorsements." + + 6. COLLECTIONS OF DOCUMENTS + + You may make a collection consisting of the Document and other + documents released under this License, and replace the individual + copies of this License in the various documents with a single copy + that is included in the collection, provided that you follow the + rules of this License for verbatim copying of each of the + documents in all other respects. + + You may extract a single document from such a collection, and + distribute it individually under this License, provided you insert + a copy of this License into the extracted document, and follow + this License in all other respects regarding verbatim copying of + that document. + + 7. AGGREGATION WITH INDEPENDENT WORKS + + A compilation of the Document or its derivatives with other + separate and independent documents or works, in or on a volume of + a storage or distribution medium, is called an "aggregate" if the + copyright resulting from the compilation is not used to limit the + legal rights of the compilation's users beyond what the individual + works permit. When the Document is included an aggregate, this + License does not apply to the other works in the aggregate which + are not themselves derivative works of the Document. + + If the Cover Text requirement of section 3 is applicable to these + copies of the Document, then if the Document is less than one half + of the entire aggregate, the Document's Cover Texts may be placed + on covers that bracket the Document within the aggregate, or the + electronic equivalent of covers if the Document is in electronic + form. Otherwise they must appear on printed covers that bracket + the whole aggregate. + + 8. TRANSLATION + + Translation is considered a kind of modification, so you may + distribute translations of the Document under the terms of section + 4. Replacing Invariant Sections with translations requires special + permission from their copyright holders, but you may include + translations of some or all Invariant Sections in addition to the + original versions of these Invariant Sections. You may include a + translation of this License, and all the license notices in the + Document, and any Warranty Disclaimers, provided that you also + include the original English version of this License and the + original versions of those notices and disclaimers. In case of a + disagreement between the translation and the original version of + this License or a notice or disclaimer, the original version will + prevail. + + If a section in the Document is Entitled "Acknowledgements", + "Dedications", or "History", the requirement (section 4) to + Preserve its Title (section 1) will typically require changing the + actual title. + + 9. TERMINATION + + You may not copy, modify, sublicense, or distribute the Document + except as expressly provided for under this License. Any other + attempt to copy, modify, sublicense or distribute the Document is + void, and will automatically terminate your rights under this + License. However, parties who have received copies, or rights, + from you under this License will not have their licenses + terminated so long as such parties remain in full compliance. + + 10. FUTURE REVISIONS OF THIS LICENSE + + The Free Software Foundation may publish new, revised versions of + the GNU Free Documentation License from time to time. Such new + versions will be similar in spirit to the present version, but may + differ in detail to address new problems or concerns. See + `http://www.gnu.org/copyleft/'. + + Each version of the License is given a distinguishing version + number. If the Document specifies that a particular numbered + version of this License "or any later version" applies to it, you + have the option of following the terms and conditions either of + that specified version or of any later version that has been + published (not as a draft) by the Free Software Foundation. If + the Document does not specify a version number of this License, + you may choose any version ever published (not as a draft) by the + Free Software Foundation. + +A.1.1 ADDENDUM: How to use this License for your documents +---------------------------------------------------------- + +To use this License in a document you have written, include a copy of +the License in the document and put the following copyright and license +notices just after the title page: + + Copyright (C) YEAR YOUR NAME. + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.2 + or any later version published by the Free Software Foundation; + with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. + A copy of the license is included in the section entitled ``GNU + Free Documentation License''. + + If you have Invariant Sections, Front-Cover Texts and Back-Cover +Texts, replace the "with...Texts." line with this: + + with the Invariant Sections being LIST THEIR TITLES, with + the Front-Cover Texts being LIST, and with the Back-Cover Texts + being LIST. + + If you have Invariant Sections without Cover Texts, or some other +combination of the three, merge those two alternatives to suit the +situation. + + If your document contains nontrivial examples of program code, we +recommend releasing these examples in parallel under your choice of +free software license, such as the GNU General Public License, to +permit their use in free software. + Tag Table: -Node: Top1208 -Node: Command Line Editing1604 -Node: Introduction and Notation2218 -Node: Readline Interaction3837 -Node: Readline Bare Essentials5025 -Node: Readline Movement Commands6807 -Node: Readline Killing Commands7765 -Node: Readline Arguments9675 -Node: Searching10712 -Node: Readline Init File12856 -Node: Readline Init File Syntax13918 -Node: Conditional Init Constructs24802 -Node: Sample Init File27328 -Node: Bindable Readline Commands30513 -Node: Commands For Moving31564 -Node: Commands For History32414 -Node: Commands For Text35273 -Node: Commands For Killing37988 -Node: Numeric Arguments39940 -Node: Commands For Completion41069 -Node: Keyboard Macros42602 -Node: Miscellaneous Commands43162 -Node: Readline vi Mode46512 +Node: Top1382 +Node: Command Line Editing1814 +Node: Introduction and Notation2457 +Node: Readline Interaction4081 +Node: Readline Bare Essentials5274 +Node: Readline Movement Commands7065 +Node: Readline Killing Commands8032 +Node: Readline Arguments9954 +Node: Searching11000 +Node: Readline Init File13153 +Node: Readline Init File Syntax14220 +Node: Conditional Init Constructs26156 +Node: Sample Init File28691 +Node: Bindable Readline Commands31810 +Node: Commands For Moving32869 +Node: Commands For History33732 +Node: Commands For Text36858 +Node: Commands For Killing39586 +Node: Numeric Arguments41730 +Node: Commands For Completion42871 +Node: Keyboard Macros44417 +Node: Miscellaneous Commands44990 +Node: Readline vi Mode48353 +Node: Copying This Manual49274 +Node: GNU Free Documentation License49506 End Tag Table |