-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.8 from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
translation approved by the author instead of in the original English.
\1f
-File: xemacs.info, Node: Completion, Next: Minibuffer History, Prev: Minibuffer Edit, Up: Minibuffer
-
-Completion
-==========
-
- For certain kinds of arguments, you can use "completion" to enter
-the argument value. Completion means that you type part of the
-argument, then XEmacs visibly fills in the rest, or as much as can be
-determined from the part you have typed.
-
- When completion is available, certain keys--<TAB>, <RET>, and
-<SPC>--are rebound to complete the text present in the minibuffer into
-a longer string that it stands for, by matching it against a set of
-"completion alternatives" provided by the command reading the argument.
-`?' is defined to display a list of possible completions of what you
-have inserted.
-
- For example, when `M-x' uses the minibuffer to read the name of a
-command, it provides a list of all available XEmacs command names to
-complete against. The completion keys match the text in the minibuffer
-against all the command names, find any additional name characters
-implied by the ones already present in the minibuffer, and add those
-characters to the ones you have given. This is what makes it possible
-to type `M-x inse <SPC> b <RET>' instead of `M-x insert-buffer <RET>'
-(for example).
-
- Case is normally significant in completion because it is significant
-in most of the names that you can complete (buffer names, file names and
-command names). Thus, `fo' does not complete to `Foo'. When you are
-completing a name in which case does not matter, case may be ignored
-for completion's sake if specified by program.
-
- When a completion list is displayed, the completions will highlight
-as you move the mouse over them. Clicking the middle mouse button on
-any highlighted completion will "select" it just as if you had typed it
-in and hit <RET>.
-
-* Menu:
-
-* Example: Completion Example.
-* Commands: Completion Commands.
-* Strict Completion::
-* Options: Completion Options.
+File: xemacs.info, Node: Bugs, Prev: Lossage, Up: Top
+
+27.13 Reporting Bugs
+====================
+
+Sometimes you will encounter a bug in Emacs. Although we cannot promise
+we can or will fix the bug, and we might not even agree that it is a
+bug, we want to hear about bugs you encounter in case we do want to fix
+them.
+
+ To make it possible for us to fix a bug, you must report it. In
+order to do so effectively, you must know when and how to do it.
+
+27.13.1 When Is There a Bug
+---------------------------
+
+If Emacs executes an illegal instruction, or dies with an operating
+system error message that indicates a problem in the program (as
+opposed to something like "disk full"), then it is certainly a bug.
+
+ If Emacs updates the display in a way that does not correspond to
+what is in the buffer, then it is certainly a bug. If a command seems
+to do the wrong thing but the problem corrects itself if you type
+`C-l', it is a case of incorrect display updating.
+
+ Taking forever to complete a command can be a bug, but you must make
+certain that it was really Emacs's fault. Some commands simply take a
+long time. Type `C-g' and then `C-h l' to see whether the input Emacs
+received was what you intended to type; if the input was such that you
+KNOW it should have been processed quickly, report a bug. If you don't
+know whether the command should take a long time, find out by looking
+in the manual or by asking for assistance.
+
+ If a command you are familiar with causes an Emacs error message in a
+case where its usual definition ought to be reasonable, it is probably a
+bug.
+
+ If a command does the wrong thing, that is a bug. But be sure you
+know for certain what it ought to have done. If you aren't familiar
+with the command, or don't know for certain how the command is supposed
+to work, then it might actually be working right. Rather than jumping
+to conclusions, show the problem to someone who knows for certain.
+
+ Finally, a command's intended definition may not be best for editing
+with. This is a very important sort of problem, but it is also a
+matter of judgment. Also, it is easy to come to such a conclusion out
+of ignorance of some of the existing features. It is probably best not
+to complain about such a problem until you have checked the
+documentation in the usual ways, feel confident that you understand it,
+and know for certain that what you want is not available. If you are
+not sure what the command is supposed to do after a careful reading of
+the manual, check the index and glossary for any terms that may be
+unclear. If you still do not understand, this indicates a bug in the
+manual. The manual's job is to make everything clear. It is just as
+important to report documentation bugs as program bugs.
+
+ If the online documentation string of a function or variable
+disagrees with the manual, one of them must be wrong, so report the bug.
+
+27.13.2 How to Report a Bug
+---------------------------
+
+When you decide that there is a bug, it is important to report it and to
+report it in a way which is useful. What is most useful is an exact
+description of what commands you type, starting with the shell command
+to run Emacs, until the problem happens. Always include the version
+number of Emacs that you are using; type `M-x emacs-version' to print
+this.
+
+ The most important principle in reporting a bug is to report FACTS,
+not hypotheses or categorizations. It is always easier to report the
+facts, but people seem to prefer to strain to posit explanations and
+report them instead. If the explanations are based on guesses about
+how Emacs is implemented, they will be useless; we will have to try to
+figure out what the facts must have been to lead to such speculations.
+Sometimes this is impossible. But in any case, it is unnecessary work
+for us.
+
+ For example, suppose that you type `C-x C-f /glorp/baz.ugh <RET>',
+visiting a file which (you know) happens to be rather large, and Emacs
+prints out `I feel pretty today'. The best way to report the bug is
+with a sentence like the preceding one, because it gives all the facts
+and nothing but the facts.
+
+ Do not assume that the problem is due to the size of the file and
+say, "When I visit a large file, Emacs prints out `I feel pretty
+today'." This is what we mean by "guessing explanations". The problem
+is just as likely to be due to the fact that there is a `z' in the file
+name. If this is so, then when we got your report, we would try out
+the problem with some "large file", probably with no `z' in its name,
+and not find anything wrong. There is no way in the world that we
+could guess that we should try visiting a file with a `z' in its name.
+
+ Alternatively, the problem might be due to the fact that the file
+starts with exactly 25 spaces. For this reason, you should make sure
+that you inform us of the exact contents of any file that is needed to
+reproduce the bug. What if the problem only occurs when you have typed
+the `C-x a l' command previously? This is why we ask you to give the
+exact sequence of characters you typed since starting to use Emacs.
+
+ You should not even say "visit a file" instead of `C-x C-f' unless
+you know that it makes no difference which visiting command is used.
+Similarly, rather than saying "if I have three characters on the line,"
+say "after I type `<RET> A B C <RET> C-p'," if that is the way you
+entered the text.
+
+ If you are not in Fundamental mode when the problem occurs, you
+should say what mode you are in.
+
+ If the manifestation of the bug is an Emacs error message, it is
+important to report not just the text of the error message but a
+backtrace showing how the Lisp program in Emacs arrived at the error.
+To make the backtrace, you must execute the Lisp expression `(setq
+debug-on-error t)' before the error happens (that is to say, you must
+execute that expression and then make the bug happen). This causes the
+Lisp debugger to run (*note Lisp Debug::). The debugger's backtrace
+can be copied as text into the bug report. This use of the debugger is
+possible only if you know how to make the bug happen again. Do note
+the error message the first time the bug happens, so if you can't make
+it happen again, you can report at least that.
+
+ Check whether any programs you have loaded into the Lisp world,
+including your init file, set any variables that may affect the
+functioning of Emacs. *Note Init File::. Also, see whether the
+problem happens in a freshly started Emacs without loading your init
+file (start Emacs with the `-q' switch to prevent loading the init
+file). If the problem does NOT occur then, it is essential that we
+know the contents of any programs that you must load into the Lisp
+world in order to cause the problem to occur.
+
+ If the problem does depend on an init file or other Lisp programs
+that are not part of the standard Emacs system, then you should make
+sure it is not a bug in those programs by complaining to their
+maintainers first. After they verify that they are using Emacs in a
+way that is supposed to work, they should report the bug.
+
+ If you can tell us a way to cause the problem without visiting any
+files, please do so. This makes it much easier to debug. If you do
+need files, make sure you arrange for us to see their exact contents.
+For example, it can often matter whether there are spaces at the ends
+of lines, or a newline after the last line in the buffer (nothing ought
+to care whether the last line is terminated, but tell that to the bugs).
+
+ The easy way to record the input to Emacs precisely is to write a
+dribble file; execute the Lisp expression:
+
+ (open-dribble-file "~/dribble")
+
+using `Meta-<ESC>' or from the `*scratch*' buffer just after starting
+Emacs. From then on, all Emacs input will be written in the specified
+dribble file until the Emacs process is killed.
+
+ For possible display bugs, it is important to report the terminal
+type (the value of environment variable `TERM'), the complete termcap
+entry for the terminal from `/etc/termcap' (since that file is not
+identical on all machines), and the output that Emacs actually sent to
+the terminal. The way to collect this output is to execute the Lisp
+expression:
+
+ (open-termscript "~/termscript")
+
+using `Meta-<ESC>' or from the `*scratch*' buffer just after starting
+Emacs. From then on, all output from Emacs to the terminal will be
+written in the specified termscript file as well, until the Emacs
+process is killed. If the problem happens when Emacs starts up, put
+this expression into your init file so that the termscript file will be
+open when Emacs displays the screen for the first time. *Note Init
+File::. Be warned: it is often difficult, and sometimes impossible, to
+fix a terminal-dependent bug without access to a terminal of the type
+that stimulates the bug.
+
+ The newsgroup `comp.emacs.xemacs' may be used for bug reports, other
+discussions and requests for assistance.
+
+ If you don't have access to this newgroup, you can subscribe to the
+mailing list version: the newsgroup is bidirectionally gatewayed into
+the mailing list `xemacs@xemacs.org'.
+
+ To be added or removed from this mailing list, send mail to
+`xemacs-request@xemacs.org'. Do not send requests for addition to the
+mailing list itself.
+
+ The mailing lists and newsgroups are archived on our anonymous FTP
+server, `ftp.xemacs.org', and at various other archive sites around the
+net. You should also check the `FAQ' in `/pub/xemacs' on our anonymous
+FTP server. It provides some introductory information and help for
+initial configuration problems.
\1f
-File: xemacs.info, Node: Completion Example, Next: Completion Commands, Prev: Completion, Up: Completion
+File: xemacs.info, Node: Glossary, Next: Manifesto, Prev: Intro, Up: Top
+
+Glossary
+********
+
+Abbrev
+ An abbrev is a text string which expands into a different text
+ string when present in the buffer. For example, you might define
+ a short word as an abbrev for a long phrase that you want to insert
+ frequently. *Note Abbrevs::.
+
+Aborting
+ Aborting means getting out of a recursive edit (q.v.). You can use
+ the commands `C-]' and `M-x top-level' for this. *Note Quitting::.
+
+Auto Fill mode
+ Auto Fill mode is a minor mode in which text you insert is
+ automatically broken into lines of fixed width. *Note Filling::.
+
+Auto Saving
+ Auto saving means that Emacs automatically stores the contents of
+ an Emacs buffer in a specially-named file so the information will
+ not be lost if the buffer is lost due to a system error or user
+ error. *Note Auto Save::.
+
+Backup File
+ A backup file records the contents that a file had before the
+ current editing session. Emacs creates backup files automatically
+ to help you track down or cancel changes you later regret. *Note
+ Backup::.
+
+Balance Parentheses
+ Emacs can balance parentheses manually or automatically. Manual
+ balancing is done by the commands to move over balanced expressions
+ (*note Lists::). Automatic balancing is done by blinking the
+ parenthesis that matches one just inserted (*note Matching Parens:
+ Matching.).
+
+Bind
+ To bind a key is to change its binding (q.v.). *Note Rebinding::.
+
+Binding
+ A key gets its meaning in Emacs by having a binding which is a
+ command (q.v.), a Lisp function that is run when the key is typed.
+ *Note Binding: Commands. Customization often involves rebinding a
+ character to a different command function. The bindings of all
+ keys are recorded in the keymaps (q.v.). *Note Keymaps::.
+
+Blank Lines
+ Blank lines are lines that contain only whitespace. Emacs has
+ several commands for operating on the blank lines in a buffer.
+
+Buffer
+ The buffer is the basic editing unit; one buffer corresponds to one
+ piece of text being edited. You can have several buffers, but at
+ any time you are editing only one, the `selected' buffer, though
+ several buffers can be visible when you are using multiple
+ windows. *Note Buffers::.
+
+Buffer Selection History
+ Emacs keeps a buffer selection history which records how recently
+ each Emacs buffer was selected. Emacs uses this list when
+ choosing a buffer to select. *Note Buffers::.
+
+C-
+ `C' in the name of a character is an abbreviation for Control.
+ *Note C-: Keystrokes.
+
+C-M-
+ `C-M-' in the name of a character is an abbreviation for
+ Control-Meta. *Note C-M-: Keystrokes.
+
+Case Conversion
+ Case conversion means changing text from upper case to lower case
+ or vice versa. *Note Case::, for the commands for case conversion.
+
+Characters
+ Characters form the contents of an Emacs buffer; also, Emacs
+ commands are invoked by keys (q.v.), which are sequences of one or
+ more characters. *Note Keystrokes::.
+
+Command
+ A command is a Lisp function specially defined to be able to serve
+ as a key binding in Emacs. When you type a key (q.v.), Emacs
+ looks up its binding (q.v.) in the relevant keymaps (q.v.) to find
+ the command to run. *Note Commands::.
+
+Command Name
+ A command name is the name of a Lisp symbol which is a command
+ (*note Commands::). You can invoke any command by its name using
+ `M-x' (*note M-x::).
+
+Comments
+ A comment is text in a program which is intended only for the
+ people reading the program, and is marked specially so that it
+ will be ignored when the program is loaded or compiled. Emacs
+ offers special commands for creating, aligning, and killing
+ comments. *Note Comments::.
+
+Compilation
+ Compilation is the process of creating an executable program from
+ source code. Emacs has commands for compiling files of Emacs Lisp
+ code (*note Lisp Libraries::) and programs in C and other languages
+ (*note Compilation::).
+
+Complete Key
+ A complete key is a character or sequence of characters which,
+ when typed by the user, fully specifies one action to be performed
+ by Emacs. For example, `X' and `Control-f' and `Control-x m' are
+ keys. Keys derive their meanings from being bound (q.v.) to
+ commands (q.v.). Thus, `X' is conventionally bound to a command
+ to insert `X' in the buffer; `C-x m' is conventionally bound to a
+ command to begin composing a mail message. *Note Keystrokes::.
-Completion Example
-------------------
-
- A concrete example may help here. If you type `M-x au <TAB>', the
-<TAB> looks for alternatives (in this case, command names) that start
-with `au'. There are several, including `auto-fill-mode' and
-`auto-save-mode'--but they are all the same as far as `auto', so the
-`au' in the minibuffer changes to `auto'.
-
- If you type <TAB> again immediately, there are multiple
-possibilities for the very next character--it could be any of `c-'--so
-no more characters are added; instead, <TAB> displays a list of all
-possible completions in another window.
-
- If you go on to type `f <TAB>', this <TAB> sees `auto-f'. The only
-command name starting this way is `auto-fill-mode', so completion fills
-in the rest of that. You now have `auto-fill-mode' in the minibuffer
-after typing just `au <TAB> f <TAB>'. Note that <TAB> has this effect
-because in the minibuffer it is bound to the command
-`minibuffer-complete' when completion is available.
-
-\1f
-File: xemacs.info, Node: Completion Commands, Next: Strict Completion, Prev: Completion Example, Up: Completion
-
-Completion Commands
--------------------
-
- Here is a list of the completion commands defined in the minibuffer
-when completion is available.
-
-`<TAB>'
- Complete the text in the minibuffer as much as possible
- (`minibuffer-complete').
-
-`<SPC>'
- Complete the minibuffer text, but don't go beyond one word
- (`minibuffer-complete-word').
-
-`<RET>'
- Submit the text in the minibuffer as the argument, possibly
- completing first as described below
- (`minibuffer-complete-and-exit').
-
-`?'
- Print a list of all possible completions of the text in the
- minibuffer (`minibuffer-list-completions').
-
-`<button2>'
- Select the highlighted text under the mouse as a minibuffer
- response. When the minibuffer is being used to prompt the user
- for a completion, any valid completions which are visible on the
- screen will be highlighted when the mouse moves over them.
- Clicking <button2> will select the highlighted completion and exit
- the minibuffer. (`minibuf-select-highlighted-completion').
-
- <SPC> completes much like <TAB>, but never goes beyond the next
-hyphen or space. If you have `auto-f' in the minibuffer and type
-<SPC>, it finds that the completion is `auto-fill-mode', but it stops
-completing after `fill-'. This gives `auto-fill-'. Another <SPC> at
-this point completes all the way to `auto-fill-mode'. <SPC> in the
-minibuffer when completion is available runs the command
-`minibuffer-complete-word'.
-
- Here are some commands you can use to choose a completion from a
-window that displays a list of completions:
-
-`button2up'
- Clicking mouse button 2 on a completion in the list of possible
- completions chooses that completion (`mouse-choose-completion').
- You normally use this command while point is in the minibuffer;
- but you must click in the list of completions, not in the
- minibuffer itself.
-
-`<RET>'
- Typing <RET> _in the completion list buffer_ chooses the
- completion that point is in or next to (`choose-completion'). To
- use this command, you must first switch windows to the window that
- shows the list of completions.
-
-`<RIGHT>'
-`<TAB>'
-`C-f'
- Typing the right-arrow key <RIGHT>, <TAB> or `C-f' _in the
- completion list buffer_ moves point to the following completion
- (`next-list-mode-item').
-
-`<LEFT>'
-`C-b'
- Typing the left-arrow key <LEFT> or `C-b' _in the completion list
- buffer_ moves point toward the beginning of the buffer, to the
- previous completion (`previous-list-mode-item').
+Completion
+ When Emacs automatically fills an abbreviation for a name into the
+ entire name, that process is called completion. Completion is
+ done for minibuffer (q.v.) arguments when the set of possible
+ valid inputs is known; for example, on command names, buffer
+ names, and file names. Completion occurs when you type <TAB>,
+ <SPC>, or <RET>. *Note Completion::.
+
+Continuation Line
+ When a line of text is longer than the width of the frame, it
+ takes up more than one screen line when displayed. We say that the
+ text line is continued, and all screen lines used for it after the
+ first are called continuation lines. *Note Continuation: Basic.
+
+Control-Character
+ ASCII characters with octal codes 0 through 037, and also code
+ 0177, do not have graphic images assigned to them. These are the
+ control characters. Any control character can be typed by holding
+ down the <CTRL> key and typing some other character; some have
+ special keys on the keyboard. <RET>, <TAB>, <ESC>, <LFD>, and
+ <DEL> are all control characters. *Note Keystrokes::.
+
+Copyleft
+ A copyleft is a notice giving the public legal permission to
+ redistribute a program or other work of art. Copylefts are used
+ by leftists to enrich the public just as copyrights are used by
+ rightists to gain power over the public.
+
+Current Buffer
+ The current buffer in Emacs is the Emacs buffer on which most
+ editing commands operate. You can select any Emacs buffer as the
+ current one. *Note Buffers::.
+
+Current Line
+ The line point is on (*note Point::).
+
+Current Paragraph
+ The paragraph that point is in. If point is between paragraphs,
+ the current paragraph is the one that follows point. *Note
+ Paragraphs::.
+
+Current Defun
+ The defun (q.v.) that point is in. If point is between defuns, the
+ current defun is the one that follows point. *Note Defuns::.
+
+Cursor
+ The cursor is the rectangle on the screen which indicates the
+ position called point (q.v.) at which insertion and deletion takes
+ place. The cursor is on or under the character that follows
+ point. Often people speak of `the cursor' when, strictly
+ speaking, they mean `point'. *Note Cursor: Basic.
+
+Customization
+ Customization is making minor changes in the way Emacs works. It
+ is often done by setting variables (*note Variables::) or by
+ rebinding keys (*note Keymaps::).
+
+Default Argument
+ The default for an argument is the value that is used if you do not
+ specify one. When Emacs prompts you in the minibuffer for an
+ argument, the default argument is used if you just type <RET>.
+ *Note Minibuffer::.
+
+Default Directory
+ When you specify a file name that does not start with `/' or `~',
+ it is interpreted relative to the current buffer's default
+ directory. *Note Default Directory: Minibuffer File.
+
+Defun
+ A defun is a list at the top level of parenthesis or bracket
+ structure in a program. It is so named because most such lists in
+ Lisp programs are calls to the Lisp function `defun'. *Note
+ Defuns::.
+
+<DEL>
+ The <DEL> character runs the command that deletes one character of
+ text. *Note DEL: Basic.
+
+Deletion
+ Deleting text means erasing it without saving it. Emacs deletes
+ text only when it is expected not to be worth saving (all
+ whitespace, or only one character). The alternative is killing
+ (q.v.). *Note Deletion: Killing.
+
+Deletion of Files
+ Deleting a file means removing it from the file system. *Note
+ Misc File Ops::.
+
+Deletion of Messages
+ Deleting a message means flagging it to be eliminated from your
+ mail file. Until the mail file is expunged, you can undo this by
+ undeleting the message.
+
+Deletion of Frames
+ When working under the multi-frame X-based version of XEmacs, you
+ can delete individual frames using the Close menu item from the
+ File menu.
+
+Deletion of Windows
+ When you delete a subwindow of an Emacs frame, you eliminate it
+ from the frame. Other windows expand to use up the space. The
+ deleted window can never come back, but no actual text is lost.
+ *Note Windows::.
+
+Directory
+ Files in the Unix file system are grouped into file directories.
+ *Note Directories: ListDir.
+
+Dired
+ Dired is the Emacs facility that displays the contents of a file
+ directory and allows you to "edit the directory", performing
+ operations on the files in the directory. *Note Dired::.
+
+Disabled Command
+ A disabled command is one that you may not run without special
+ confirmation. Commands are usually disabled because they are
+ confusing for beginning users. *Note Disabling::.
+
+Dribble File
+ A file into which Emacs writes all the characters that the user
+ types on the keyboard. Dribble files are used to make a record for
+ debugging Emacs bugs. Emacs does not make a dribble file unless
+ you tell it to. *Note Bugs::.
+
+Echo Area
+ The area at the bottom of the Emacs frame which is used for
+ echoing the arguments to commands, for asking questions, and for
+ printing brief messages (including error messages). *Note Echo
+ Area::.
+
+Echoing
+ Echoing refers to acknowledging the receipt of commands by
+ displaying them (in the echo area). Emacs never echoes
+ single-character keys; longer keys echo only if you pause while
+ typing them.
+
+Error
+ An error occurs when an Emacs command cannot execute in the current
+ circumstances. When an error occurs, execution of the command
+ stops (unless the command has been programmed to do otherwise) and
+ Emacs reports the error by printing an error message (q.v.).
+ Type-ahead is discarded. Then Emacs is ready to read another
+ editing command.
+
+Error Messages
+ Error messages are single lines of output printed by Emacs when the
+ user asks for something impossible to do (such as killing text
+ forward when point is at the end of the buffer). They appear in
+ the echo area, accompanied by a beep.
+
+<ESC>
+ <ESC> is a character used as a prefix for typing Meta characters on
+ keyboards lacking a <META> key. Unlike the <META> key (which,
+ like the <SHIFT> key, is held down while another character is
+ typed), the <ESC> key is pressed and released, and applies to the
+ next character typed.
+
+Fill Prefix
+ The fill prefix is a string that Emacs enters at the beginning of
+ each line when it performs filling. It is not regarded as part of
+ the text to be filled. *Note Filling::.
+
+Filling
+ Filling text means moving text from line to line so that all the
+ lines are approximately the same length. *Note Filling::.
+
+Frame
+ When running Emacs on a TTY terminal, "frame" means the terminal's
+ screen. When running Emacs under X, you can have multiple frames,
+ each corresponding to a top-level X window and each looking like
+ the screen on a TTY. Each frame contains one or more
+ non-overlapping Emacs windows (possibly with associated
+ scrollbars, under X), an echo area, and (under X) possibly a
+ menubar, toolbar, and/or gutter.
+
+Global
+ Global means `independent of the current environment; in effect
+ throughout Emacs'. It is the opposite of local (q.v.). Examples
+ of the use of `global' appear below.
+
+Global Abbrev
+ A global definition of an abbrev (q.v.) is effective in all major
+ modes that do not have local (q.v.) definitions for the same
+ abbrev. *Note Abbrevs::.
+
+Global Keymap
+ The global keymap (q.v.) contains key bindings that are in effect
+ unless local key bindings in a major mode's local keymap (q.v.)
+ override them.*Note Keymaps::.
+
+Global Substitution
+ Global substitution means replacing each occurrence of one string
+ by another string through a large amount of text. *Note Replace::.
+
+Global Variable
+ The global value of a variable (q.v.) takes effect in all buffers
+ that do not have their own local (q.v.) values for the variable.
+ *Note Variables::.
+
+Graphic Character
+ Graphic characters are those assigned pictorial images rather than
+ just names. All the non-Meta (q.v.) characters except for the
+ Control (q.v.) character are graphic characters. These include
+ letters, digits, punctuation, and spaces; they do not include
+ <RET> or <ESC>. In Emacs, typing a graphic character inserts that
+ character (in ordinary editing modes). *Note Basic Editing: Basic.
+
+Grinding
+ Grinding means adjusting the indentation in a program to fit the
+ nesting structure. *Note Grinding: Indentation.
+
+Hardcopy
+ Hardcopy means printed output. Emacs has commands for making
+ printed listings of text in Emacs buffers. *Note Hardcopy::.
+
+<HELP>
+ You can type <HELP> at any time to ask what options you have, or
+ to ask what any command does. <HELP> is really `Control-h'.
+ *Note Help::.
+
+Inbox
+ An inbox is a file in which mail is delivered by the operating
+ system. Some mail handlers transfers mail from inboxes to mail
+ files (q.v.) in which the mail is then stored permanently or until
+ explicitly deleted.
+
+Indentation
+ Indentation means blank space at the beginning of a line. Most
+ programming languages have conventions for using indentation to
+ illuminate the structure of the program, and Emacs has special
+ features to help you set up the correct indentation. *Note
+ Indentation::.
+
+Insertion
+ Insertion means copying text into the buffer, either from the
+ keyboard or from some other place in Emacs.
+
+Justification
+ Justification means adding extra spaces to lines of text to make
+ them come exactly to a specified width. *Note Justification:
+ Filling.
+
+Keyboard Macros
+ Keyboard macros are a way of defining new Emacs commands from
+ sequences of existing ones, with no need to write a Lisp program.
+ *Note Keyboard Macros::.
+
+Key
+ A key is a sequence of characters that, when input to Emacs,
+ specify or begin to specify a single action for Emacs to perform.
+ That is, the sequence is considered a single unit. If the key is
+ enough to specify one action, it is a complete key (q.v.); if it
+ is less than enough, it is a prefix key (q.v.). *Note
+ Keystrokes::.
+
+Keymap
+ The keymap is the data structure that records the bindings (q.v.)
+ of keys to the commands that they run. For example, the keymap
+ binds the character `C-n' to the command function `next-line'.
+ *Note Keymaps::.
+
+Kill Ring
+ The kill ring is the place where all text you have killed recently
+ is saved. You can re-insert any of the killed text still in the
+ ring; this is called yanking (q.v.). *Note Yanking::.
+
+Killing
+ Killing means erasing text and saving it on the kill ring so it
+ can be yanked (q.v.) later. Some other systems call this
+ "cutting." Most Emacs commands to erase text do killing, as
+ opposed to deletion (q.v.). *Note Killing::.
+
+Killing Jobs
+ Killing a job (such as, an invocation of Emacs) means making it
+ cease to exist. Any data within it, if not saved in a file, is
+ lost. *Note Exiting::.
+
+List
+ A list is, approximately, a text string beginning with an open
+ parenthesis and ending with the matching close parenthesis. In C
+ mode and other non-Lisp modes, groupings surrounded by other kinds
+ of matched delimiters appropriate to the language, such as braces,
+ are also considered lists. Emacs has special commands for many
+ operations on lists. *Note Lists::.
+
+Local
+ Local means `in effect only in a particular context'; the relevant
+ kind of context is a particular function execution, a particular
+ buffer, or a particular major mode. Local is the opposite of
+ `global' (q.v.). Specific uses of `local' in Emacs terminology
+ appear below.
+
+Local Abbrev
+ A local abbrev definition is effective only if a particular major
+ mode is selected. In that major mode, it overrides any global
+ definition for the same abbrev. *Note Abbrevs::.
+
+Local Keymap
+ A local keymap is used in a particular major mode; the key bindings
+ (q.v.) in the current local keymap override global bindings of the
+ same keys. *Note Keymaps::.
+
+Local Variable
+ A local value of a variable (q.v.) applies to only one buffer.
+ *Note Locals::.
+
+M-
+ `M-' in the name of a character is an abbreviation for <META>, one
+ of the modifier keys that can accompany any character. *Note
+ Keystrokes::.
+
+M-C-
+ `M-C-' in the name of a character is an abbreviation for
+ Control-Meta; it means the same thing as `C-M-'. If your terminal
+ lacks a real <META> key, you type a Control-Meta character by
+ typing <ESC> and then typing the corresponding Control character.
+ *Note C-M-: Keystrokes.
+
+M-x
+ `M-x' is the key which is used to call an Emacs command by name.
+ You use it to call commands that are not bound to keys. *Note
+ M-x::.
+
+Mail
+ Mail means messages sent from one user to another through the
+ computer system, to be read at the recipient's convenience. Emacs
+ has commands for composing and sending mail, and for reading and
+ editing the mail you have received. *Note Sending Mail::.
+
+Major Mode
+ The major modes are a mutually exclusive set of options each of
+ which configures Emacs for editing a certain sort of text.
+ Ideally, each programming language has its own major mode. *Note
+ Major Modes::.
+
+Mark
+ The mark points to a position in the text. It specifies one end
+ of the region (q.v.), point being the other end. Many commands
+ operate on the whole region, that is, all the text from point to
+ the mark. *Note Mark::.
+
+Mark Ring
+ The mark ring is used to hold several recent previous locations of
+ the mark, just in case you want to move back to them. *Note Mark
+ Ring::.
+
+Message
+ See `mail'.
+
+Meta
+ Meta is the name of a modifier bit which a command character may
+ have. It is present in a character if the character is typed with
+ the <META> key held down. Such characters are given names that
+ start with `Meta-'. For example, `Meta-<' is typed by holding down
+ <META> and at the same time typing `<' (which itself is done, on
+ most terminals, by holding down <SHIFT> and typing `,'). *Note
+ Meta: Keystrokes.
+
+Meta Character
+ A Meta character is one whose character code includes the Meta bit.
+
+Minibuffer
+ The minibuffer is the window that Emacs displays inside the echo
+ area (q.v.) when it prompts you for arguments to commands. *Note
+ Minibuffer::.
+
+Minor Mode
+ A minor mode is an optional feature of Emacs which can be switched
+ on or off independent of the major mode. Each minor mode has a
+ command to turn it on or off. *Note Minor Modes::.
+
+Mode Line
+ The mode line is the line at the bottom of each text window (q.v.),
+ which gives status information on the buffer displayed in that
+ window. *Note Mode Line::.
+
+Modified Buffer
+ A buffer (q.v.) is modified if its text has been changed since the
+ last time the buffer was saved (or since it was created, if it has
+ never been saved). *Note Saving::.
+
+Moving Text
+ Moving text means erasing it from one place and inserting it in
+ another. This is done by killing (q.v.) and then yanking (q.v.).
+ *Note Killing::.
+
+Named Mark
+ A named mark is a register (q.v.) in its role of recording a
+ location in text so that you can move point to that location.
+ *Note Registers::.
+
+Narrowing
+ Narrowing means creating a restriction (q.v.) that limits editing
+ in the current buffer to only a part of the text in the buffer.
+ Text outside that part is inaccessible to the user until the
+ boundaries are widened again, but it is still there, and saving
+ the file saves the invisible text. *Note Narrowing::.
+
+Newline
+ <LFD> characters in the buffer terminate lines of text and are
+ called newlines. *Note Newline: Keystrokes.
+
+Numeric Argument
+ A numeric argument is a number, specified before a command, to
+ change the effect of the command. Often the numeric argument
+ serves as a repeat count. *Note Arguments::.
+
+Option
+ An option is a variable (q.v.) that allows you to customize Emacs
+ by giving it a new value. *Note Variables::.
+
+Overwrite Mode
+ Overwrite mode is a minor mode. When it is enabled, ordinary text
+ characters replace the existing text after point rather than
+ pushing it to the right. *Note Minor Modes::.
+
+Page
+ A page is a unit of text, delimited by formfeed characters (ASCII
+ Control-L, code 014) coming at the beginning of a line. Some Emacs
+ commands are provided for moving over and operating on pages.
+ *Note Pages::.
+
+Paragraphs
+ Paragraphs are the medium-size unit of English text. There are
+ special Emacs commands for moving over and operating on paragraphs.
+ *Note Paragraphs::.
+
+Parsing
+ We say that Emacs parses words or expressions in the text being
+ edited. Really, all it knows how to do is find the other end of a
+ word or expression. *Note Syntax::.
+
+Point
+ Point is the place in the buffer at which insertion and deletion
+ occur. Point is considered to be between two characters, not at
+ one character. The terminal's cursor (q.v.) indicates the
+ location of point. *Note Point: Basic.
+
+Prefix Key
+ A prefix key is a key (q.v.) whose sole function is to introduce a
+ set of multi-character keys. `Control-x' is an example of a prefix
+ key; any two-character sequence starting with `C-x' is also a
+ legitimate key. *Note Keystrokes::.
+
+Prompt
+ A prompt is text printed to ask the user for input. Printing a
+ prompt is called prompting. Emacs prompts always appear in the
+ echo area (q.v.). One kind of prompting happens when the
+ minibuffer is used to read an argument (*note Minibuffer::); the
+ echoing which happens when you pause in the middle of typing a
+ multi-character key is also a kind of prompting (*note Echo
+ Area::).
+
+Quitting
+ Quitting means cancelling a partially typed command or a running
+ command, using `C-g'. *Note Quitting::.
+
+Quoting
+ Quoting means depriving a character of its usual special
+ significance. In Emacs this is usually done with `Control-q'.
+ What constitutes special significance depends on the context and
+ on convention. For example, an "ordinary" character as an Emacs
+ command inserts itself; so in this context, a special character is
+ any character that does not normally insert itself (such as <DEL>,
+ for example), and quoting it makes it insert itself as if it were
+ not special. Not all contexts allow quoting. *Note Quoting:
+ Basic.
+
+Read-only Buffer
+ A read-only buffer is one whose text you are not allowed to change.
+ Normally Emacs makes buffers read-only when they contain text which
+ has a special significance to Emacs, such as Dired buffers.
+ Visiting a file that is write-protected also makes a read-only
+ buffer. *Note Buffers::.
+
+Recursive Editing Level
+ A recursive editing level is a state in which part of the
+ execution of a command involves asking the user to edit some text.
+ This text may or may not be the same as the text to which the
+ command was applied. The mode line indicates recursive editing
+ levels with square brackets (`[' and `]'). *Note Recursive Edit::.
+
+Redisplay
+ Redisplay is the process of correcting the image on the screen to
+ correspond to changes that have been made in the text being edited.
+ *Note Redisplay: Frame.
+
+Regexp
+ See `regular expression'.
+
+Region
+ The region is the text between point (q.v.) and the mark (q.v.).
+ Many commands operate on the text of the region. *Note Region:
+ Mark.
+
+Registers
+ Registers are named slots in which text or buffer positions or
+ rectangles can be saved for later use. *Note Registers::.
+
+Regular Expression
+ A regular expression is a pattern that can match various text
+ strings; for example, `l[0-9]+' matches `l' followed by one or more
+ digits. *Note Regexps::.
+
+Replacement
+ See `global substitution'.
+
+Restriction
+ A buffer's restriction is the amount of text, at the beginning or
+ the end of the buffer, that is temporarily invisible and
+ inaccessible. Giving a buffer a nonzero amount of restriction is
+ called narrowing (q.v.). *Note Narrowing::.
+
+<RET>
+ <RET> is the character than runs the command to insert a newline
+ into the text. It is also used to terminate most arguments read
+ in the minibuffer (q.v.). *Note Return: Keystrokes.
+
+Saving
+ Saving a buffer means copying its text into the file that was
+ visited (q.v.) in that buffer. To actually change a file you have
+ edited in Emacs, you have to save it. *Note Saving::.
+
+Scrolling
+ Scrolling means shifting the text in the Emacs window to make a
+ different part of the buffer visible. *Note Scrolling: Display.
+
+Searching
+ Searching means moving point to the next occurrence of a specified
+ string. *Note Search::.
+
+Selecting
+ Selecting a buffer means making it the current (q.v.) buffer.
+ *Note Selecting: Buffers.
+
+Self-documentation
+ Self-documentation is the feature of Emacs which can tell you what
+ any command does, or can give you a list of all commands related
+ to a topic you specify. You ask for self-documentation with the
+ help character, `C-h'. *Note Help::.
+
+Sentences
+ Emacs has commands for moving by or killing by sentences. *Note
+ Sentences::.
+
+Sexp
+ An sexp (short for `s-expression,' itself short for `symbolic
+ expression') is the basic syntactic unit of Lisp in its textual
+ form: either a list, or Lisp atom. Many Emacs commands operate on
+ sexps. The term `sexp' is generalized to languages other than
+ Lisp to mean a syntactically recognizable expression. *Note
+ Sexps: Lists.
+
+Simultaneous Editing
+ Simultaneous editing means two users modifying the same file at
+ once. If simultaneous editing is not detected, you may lose your
+ work. Emacs detects all cases of simultaneous editing and warns
+ the user to investigate them. *Note Simultaneous Editing:
+ Interlocking.
+
+String
+ A string is a kind of Lisp data object which contains a sequence of
+ characters. Many Emacs variables are intended to have strings as
+ values. The Lisp syntax for a string consists of the characters in
+ the string with a `"' before and another `"' after. Write a `"'
+ that is part of the string as `\"' and a `\' that is part of the
+ string as `\\'. You can include all other characters, including
+ newline, just by writing them inside the string. You can also
+ include escape sequences as in C, such as `\n' for newline or
+ `\241' using an octal character code.
+
+String Substitution
+ See `global substitution'.
+
+Syntax Table
+ The syntax table tells Emacs which characters are part of a word,
+ which characters balance each other like parentheses, etc. *Note
+ Syntax::.
+
+Tag Table
+ A tag table is a file that serves as an index to the function
+ definitions in one or more other files. *Note Tags::.
+
+Termscript File
+ A termscript file contains a record of all characters Emacs sent to
+ the terminal. It is used for tracking down bugs in Emacs
+ redisplay. Emacs does not make a termscript file unless
+ explicitly instructed to do so. *Note Bugs::.
+
+Text
+ Text has two meanings (*note Text::):
+
+ * Data consisting of a sequence of characters, as opposed to
+ binary numbers, images, graphics commands, executable
+ programs, and the like. The contents of an Emacs buffer are
+ always text in this sense.
+
+ * Data consisting of written human language, as opposed to
+ programs, or something that follows the stylistic conventions
+ of human language.
+
+Top Level
+ Top level is the normal state of Emacs, in which you are editing
+ the text of the file you have visited. You are at top level
+ whenever you are not in a recursive editing level (q.v.) or the
+ minibuffer (q.v.), and not in the middle of a command. You can
+ get back to top level by aborting (q.v.) and quitting (q.v.).
+ *Note Quitting::.
+
+Transposition
+ Transposing two units of text means putting each one into the place
+ formerly occupied by the other. There are Emacs commands to
+ transpose two adjacent characters, words, sexps (q.v.), or lines
+ (*note Transpose::).
+
+Truncation
+ Truncating text lines in the display means leaving out any text on
+ a line that does not fit within the right margin of the window
+ displaying it. See also `continuation line'. *Note Truncation:
+ Basic.
+
+Undoing
+ Undoing means making your previous editing go in reverse, bringing
+ back the text that existed earlier in the editing session. *Note
+ Undo::.
+
+Variable
+ A variable is Lisp object that can store an arbitrary value.
+ Emacs uses some variables for internal purposes, and has others
+ (known as `options' (q.v.)) you can set to control the behavior of
+ Emacs. The variables used in Emacs that you are likely to be
+ interested in are listed in the Variables Index of this manual.
+ *Note Variables::, for information on variables.
+
+Visiting
+ Visiting a file means loading its contents into a buffer (q.v.)
+ where they can be edited. *Note Visiting::.
+
+Whitespace
+ Whitespace is any run of consecutive formatting characters (spaces,
+ tabs, newlines, and backspaces).
+
+Widening
+ Widening is removing any restriction (q.v.) on the current buffer;
+ it is the opposite of narrowing (q.v.). *Note Narrowing::.
+
+Window
+ Emacs divides the frame into one or more windows, each of which can
+ display the contents of one buffer (q.v.) at any time. *Note
+ Frame::, for basic information on how Emacs uses the frame. *Note
+ Windows::, for commands to control the use of windows. Note that if
+ you are running Emacs under X, terminology can be confusing: Each
+ Emacs frame occupies a separate X window and can, in turn, be
+ divided into different subwindows.
+
+Word Abbrev
+ Synonymous with `abbrev'.
+
+Word Search
+ Word search is searching for a sequence of words, considering the
+ punctuation between them as insignificant. *Note Word Search::.
+
+Yanking
+ Yanking means reinserting text previously killed. It can be used
+ to undo a mistaken kill, or for copying or moving text. Some other
+ systems call this "pasting". *Note Yanking::.
\1f
-File: xemacs.info, Node: Strict Completion, Next: Completion Options, Prev: Completion Commands, Up: Completion
-
-Strict Completion
------------------
-
- There are three different ways that <RET> can work in completing
-minibuffers, depending on how the argument will be used.
-
- * "Strict" completion is used when it is meaningless to give any
- argument except one of the known alternatives. For example, when
- `C-x k' reads the name of a buffer to kill, it is meaningless to
- give anything but the name of an existing buffer. In strict
- completion, <RET> refuses to exit if the text in the minibuffer
- does not complete to an exact match.
-
- * "Cautious" completion is similar to strict completion, except that
- <RET> exits only if the text was an exact match already, not
- needing completion. If the text is not an exact match, <RET> does
- not exit, but it does complete the text. If it completes to an
- exact match, a second <RET> will exit.
-
- Cautious completion is used for reading file names for files that
- must already exist.
-
- * "Permissive" completion is used when any string whatever is
- meaningful, and the list of completion alternatives is just a
- guide. For example, when `C-x C-f' reads the name of a file to
- visit, any file name is allowed, in case you want to create a
- file. In permissive completion, <RET> takes the text in the
- minibuffer exactly as given, without completing it.
-
- The completion commands display a list of all possible completions in
-a window whenever there is more than one possibility for the very next
-character. Also, typing `?' explicitly requests such a list. If the
-list of completions is long, you can scroll it with `C-M-v' (*note
-Other Window::).
+File: xemacs.info, Node: Manifesto, Next: Key Index, Prev: Glossary, Up: Top
+
+The GNU Manifesto
+*****************
+
+What's GNU? GNU's Not Unix!
+============================
+
+GNU, which stands for GNU's Not Unix, is the name for the complete
+Unix-compatible software system which I am writing so that I can give it
+away free to everyone who can use it. Several other volunteers are
+helping me. Contributions of time, money, programs, and equipment are
+greatly needed.
+
+ So far we have an Emacs text editor with Lisp for writing editor
+commands, a source level debugger, a yacc-compatible parser generator,
+a linker, and around 35 utilities. A shell (command interpreter) is
+nearly completed. A new portable optimizing C compiler has compiled
+itself and may be released this year. An initial kernel exists, but
+many more features are needed to emulate Unix. When the kernel and
+compiler are finished, it will be possible to distribute a GNU system
+suitable for program development. We will use TeX as our text
+formatter, but an nroff is being worked on. We will use the free,
+portable X window system as well. After this we will add a portable
+Common Lisp, an Empire game, a spreadsheet, and hundreds of other
+things, plus online documentation. We hope to supply, eventually,
+everything useful that normally comes with a Unix system, and more.
+
+ GNU will be able to run Unix programs, but will not be identical to
+Unix. We will make all improvements that are convenient, based on our
+experience with other operating systems. In particular, we plan to
+have longer filenames, file version numbers, a crashproof file system,
+filename completion perhaps, terminal-independent display support, and
+perhaps eventually a Lisp-based window system through which several
+Lisp programs and ordinary Unix programs can share a screen. Both C
+and Lisp will be available as system programming languages. We will
+try to support UUCP, MIT Chaosnet, and Internet protocols for
+communication.
+
+ GNU is aimed initially at machines in the 68000/16000 class with
+virtual memory, because they are the easiest machines to make it run
+on. The extra effort to make it run on smaller machines will be left
+to someone who wants to use it on them.
+
+ To avoid horrible confusion, please pronounce the `G' in the word
+`GNU' when it is the name of this project.
+
+Why I Must Write GNU
+====================
+
+I consider that the golden rule requires that if I like a program I must
+share it with other people who like it. Software sellers want to divide
+the users and conquer them, making each user agree not to share with
+others. I refuse to break solidarity with other users in this way. I
+cannot in good conscience sign a nondisclosure agreement or a software
+license agreement. For years I worked within the Artificial
+Intelligence Lab to resist such tendencies and other inhospitalities,
+but eventually they had gone too far: I could not remain in an
+institution where such things are done for me against my will.
+
+ So that I can continue to use computers without dishonor, I have
+decided to put together a sufficient body of free software so that I
+will be able to get along without any software that is not free. I
+have resigned from the AI lab to deny MIT any legal excuse to prevent
+me from giving GNU away.
+
+Why GNU Will Be Compatible With Unix
+====================================
+
+Unix is not my ideal system, but it is not too bad. The essential
+features of Unix seem to be good ones, and I think I can fill in what
+Unix lacks without spoiling them. And a system compatible with Unix
+would be convenient for many other people to adopt.
+
+How GNU Will Be Available
+=========================
+
+GNU is not in the public domain. Everyone will be permitted to modify
+and redistribute GNU, but no distributor will be allowed to restrict its
+further redistribution. That is to say, proprietary modifications will
+not be allowed. I want to make sure that all versions of GNU remain
+free.
+
+Why Many Other Programmers Want to Help
+=======================================
+
+I have found many other programmers who are excited about GNU and want
+to help.
+
+ Many programmers are unhappy about the commercialization of system
+software. It may enable them to make more money, but it requires them
+to feel in conflict with other programmers in general rather than feel
+as comrades. The fundamental act of friendship among programmers is the
+sharing of programs; marketing arrangements now typically used
+essentially forbid programmers to treat others as friends. The
+purchaser of software must choose between friendship and obeying the
+law. Naturally, many decide that friendship is more important. But
+those who believe in law often do not feel at ease with either choice.
+They become cynical and think that programming is just a way of making
+money.
+
+ By working on and using GNU rather than proprietary programs, we can
+be hospitable to everyone and obey the law. In addition, GNU serves as
+an example to inspire and a banner to rally others to join us in
+sharing. This can give us a feeling of harmony which is impossible if
+we use software that is not free. For about half the programmers I
+talk to, this is an important happiness that money cannot replace.
+
+How You Can Contribute
+======================
+
+I am asking computer manufacturers for donations of machines and money.
+I'm asking individuals for donations of programs and work.
+
+ One consequence you can expect if you donate machines is that GNU
+will run on them at an early date. The machines should be complete,
+ready-to-use systems, approved for use in a residential area, and not
+in need of sophisticated cooling or power.
+
+ I have found very many programmers eager to contribute part-time
+work for GNU. For most projects, such part-time distributed work would
+be very hard to coordinate; the independently-written parts would not
+work together. But for the particular task of replacing Unix, this
+problem is absent. A complete Unix system contains hundreds of utility
+programs, each of which is documented separately. Most interface
+specifications are fixed by Unix compatibility. If each contributor
+can write a compatible replacement for a single Unix utility, and make
+it work properly in place of the original on a Unix system, then these
+utilities will work right when put together. Even allowing for Murphy
+to create a few unexpected problems, assembling these components will
+be a feasible task. (The kernel will require closer communication and
+will be worked on by a small, tight group.)
+
+ If I get donations of money, I may be able to hire a few people full
+or part time. The salary won't be high by programmers' standards, but
+I'm looking for people for whom building community spirit is as
+important as making money. I view this as a way of enabling dedicated
+people to devote their full energies to working on GNU by sparing them
+the need to make a living in another way.
+
+Why All Computer Users Will Benefit
+===================================
+
+Once GNU is written, everyone will be able to obtain good system
+software free, just like air.
+
+ This means much more than just saving everyone the price of a Unix
+license. It means that much wasteful duplication of system programming
+effort will be avoided. This effort can go instead into advancing the
+state of the art.
+
+ Complete system sources will be available to everyone. As a result,
+a user who needs changes in the system will always be free to make them
+himself, or hire any available programmer or company to make them for
+him. Users will no longer be at the mercy of one programmer or company
+which owns the sources and is in sole position to make changes.
+
+ Schools will be able to provide a much more educational environment
+by encouraging all students to study and improve the system code.
+Harvard's computer lab used to have the policy that no program could be
+installed on the system if its sources were not on public display, and
+upheld it by actually refusing to install certain programs. I was very
+much inspired by this.
+
+ Finally, the overhead of considering who owns the system software
+and what one is or is not entitled to do with it will be lifted.
+
+ Arrangements to make people pay for using a program, including
+licensing of copies, always incur a tremendous cost to society through
+the cumbersome mechanisms necessary to figure out how much (that is,
+which programs) a person must pay for. And only a police state can
+force everyone to obey them. Consider a space station where air must
+be manufactured at great cost: charging each breather per liter of air
+may be fair, but wearing the metered gas mask all day and all night is
+intolerable even if everyone can afford to pay the air bill. And the
+TV cameras everywhere to see if you ever take the mask off are
+outrageous. It's better to support the air plant with a head tax and
+chuck the masks.
+
+ Copying all or parts of a program is as natural to a programmer as
+breathing, and as productive. It ought to be as free.
+
+Some Easily Rebutted Objections to GNU's Goals
+==============================================
+
+ "Nobody will use it if it is free, because that means they can't
+ rely on any support."
+
+ "You have to charge for the program to pay for providing the
+ support."
+
+ If people would rather pay for GNU plus service than get GNU free
+without service, a company to provide just service to people who have
+obtained GNU free ought to be profitable.
+
+ We must distinguish between support in the form of real programming
+work and mere handholding. The former is something one cannot rely on
+from a software vendor. If your problem is not shared by enough
+people, the vendor will tell you to get lost.
+
+ If your business needs to be able to rely on support, the only way
+is to have all the necessary sources and tools. Then you can hire any
+available person to fix your problem; you are not at the mercy of any
+individual. With Unix, the price of sources puts this out of
+consideration for most businesses. With GNU this will be easy. It is
+still possible for there to be no available competent person, but this
+problem cannot be blamed on distribution arrangements. GNU does not
+eliminate all the world's problems, only some of them.
+
+ Meanwhile, the users who know nothing about computers need
+handholding: doing things for them which they could easily do
+themselves but don't know how.
+
+ Such services could be provided by companies that sell just
+hand-holding and repair service. If it is true that users would rather
+spend money and get a product with service, they will also be willing
+to buy the service having got the product free. The service companies
+will compete in quality and price; users will not be tied to any
+particular one. Meanwhile, those of us who don't need the service
+should be able to use the program without paying for the service.
+
+ "You cannot reach many people without advertising, and you must
+ charge for the program to support that."
+
+ "It's no use advertising a program people can get free."
+
+ There are various forms of free or very cheap publicity that can be
+used to inform numbers of computer users about something like GNU. But
+it may be true that one can reach more microcomputer users with
+advertising. If this is really so, a business which advertises the
+service of copying and mailing GNU for a fee ought to be successful
+enough to pay for its advertising and more. This way, only the users
+who benefit from the advertising pay for it.
+
+ On the other hand, if many people get GNU from their friends, and
+such companies don't succeed, this will show that advertising was not
+really necessary to spread GNU. Why is it that free market advocates
+don't want to let the free market decide this?
+
+ "My company needs a proprietary operating system to get a
+ competitive edge."
+
+ GNU will remove operating system software from the realm of
+competition. You will not be able to get an edge in this area, but
+neither will your competitors be able to get an edge over you. You and
+they will compete in other areas, while benefitting mutually in this
+one. If your business is selling an operating system, you will not
+like GNU, but that's tough on you. If your business is something else,
+GNU can save you from being pushed into the expensive business of
+selling operating systems.
+
+ I would like to see GNU development supported by gifts from many
+manufacturers and users, reducing the cost to each.
+
+ "Don't programmers deserve a reward for their creativity?"
+
+ If anything deserves a reward, it is social contribution.
+Creativity can be a social contribution, but only in so far as society
+is free to use the results. If programmers deserve to be rewarded for
+creating innovative programs, by the same token they deserve to be
+punished if they restrict the use of these programs.
+
+ "Shouldn't a programmer be able to ask for a reward for his
+ creativity?"
+
+ There is nothing wrong with wanting pay for work, or seeking to
+maximize one's income, as long as one does not use means that are
+destructive. But the means customary in the field of software today
+are based on destruction.
+
+ Extracting money from users of a program by restricting their use of
+it is destructive because the restrictions reduce the amount and the
+ways that the program can be used. This reduces the amount of wealth
+that humanity derives from the program. When there is a deliberate
+choice to restrict, the harmful consequences are deliberate destruction.
+
+ The reason a good citizen does not use such destructive means to
+become wealthier is that, if everyone did so, we would all become
+poorer from the mutual destructiveness. This is Kantian ethics; or,
+the Golden Rule. Since I do not like the consequences that result if
+everyone hoards information, I am required to consider it wrong for one
+to do so. Specifically, the desire to be rewarded for one's creativity
+does not justify depriving the world in general of all or part of that
+creativity.
+
+ "Won't programmers starve?"
+
+ I could answer that nobody is forced to be a programmer. Most of us
+cannot manage to get any money for standing on the street and making
+faces. But we are not, as a result, condemned to spend our lives
+standing on the street making faces, and starving. We do something
+else.
+
+ But that is the wrong answer because it accepts the questioner's
+implicit assumption: that without ownership of software, programmers
+cannot possibly be paid a cent. Supposedly it is all or nothing.
+
+ The real reason programmers will not starve is that it will still be
+possible for them to get paid for programming; just not paid as much as
+now.
+
+ Restricting copying is not the only basis for business in software.
+It is the most common basis because it brings in the most money. If it
+were prohibited, or rejected by the customer, software business would
+move to other bases of organization which are now used less often.
+There are always numerous ways to organize any kind of business.
+
+ Probably programming will not be as lucrative on the new basis as it
+is now. But that is not an argument against the change. It is not
+considered an injustice that sales clerks make the salaries that they
+now do. If programmers made the same, that would not be an injustice
+either. (In practice they would still make considerably more than
+that.)
+
+ "Don't people have a right to control how their creativity is
+ used?"
+
+ "Control over the use of one's ideas" really constitutes control over
+other people's lives; and it is usually used to make their lives more
+difficult.
+
+ People who have studied the issue of intellectual property rights
+carefully (such as lawyers) say that there is no intrinsic right to
+intellectual property. The kinds of supposed intellectual property
+rights that the government recognizes were created by specific acts of
+legislation for specific purposes.
+
+ For example, the patent system was established to encourage
+inventors to disclose the details of their inventions. Its purpose was
+to help society rather than to help inventors. At the time, the life
+span of 17 years for a patent was short compared with the rate of
+advance of the state of the art. Since patents are an issue only among
+manufacturers, for whom the cost and effort of a license agreement are
+small compared with setting up production, the patents often do not do
+much harm. They do not obstruct most individuals who use patented
+products.
+
+ The idea of copyright did not exist in ancient times, when authors
+frequently copied other authors at length in works of non-fiction. This
+practice was useful, and is the only way many authors' works have
+survived even in part. The copyright system was created expressly for
+the purpose of encouraging authorship. In the domain for which it was
+invented--books, which could be copied economically only on a printing
+press--it did little harm, and did not obstruct most of the individuals
+who read the books.
+
+ All intellectual property rights are just licenses granted by society
+because it was thought, rightly or wrongly, that society as a whole
+would benefit by granting them. But in any particular situation, we
+have to ask: are we really better off granting such license? What kind
+of act are we licensing a person to do?
+
+ The case of programs today is very different from that of books a
+hundred years ago. The fact that the easiest way to copy a program is
+from one neighbor to another, the fact that a program has both source
+code and object code which are distinct, and the fact that a program is
+used rather than read and enjoyed, combine to create a situation in
+which a person who enforces a copyright is harming society as a whole
+both materially and spiritually; in which a person should not do so
+regardless of whether the law enables him to.
+
+ "Competition makes things get done better."
+
+ The paradigm of competition is a race: by rewarding the winner, we
+encourage everyone to run faster. When capitalism really works this
+way, it does a good job; but its defenders are wrong in assuming it
+always works this way. If the runners forget why the reward is offered
+and become intent on winning, no matter how, they may find other
+strategies--such as, attacking other runners. If the runners get into
+a fist fight, they will all finish late.
+
+ Proprietary and secret software is the moral equivalent of runners
+in a fist fight. Sad to say, the only referee we've got does not seem
+to object to fights; he just regulates them ("For every ten yards you
+run, you can fire one shot"). He really ought to break them up, and
+penalize runners for even trying to fight.
+
+ "Won't everyone stop programming without a monetary incentive?"
+
+ Actually, many people will program with absolutely no monetary
+incentive. Programming has an irresistible fascination for some
+people, usually the people who are best at it. There is no shortage of
+professional musicians who keep at it even though they have no hope of
+making a living that way.
+
+ But really this question, though commonly asked, is not appropriate
+to the situation. Pay for programmers will not disappear, only become
+less. So the right question is, will anyone program with a reduced
+monetary incentive? My experience shows that they will.
+
+ For more than ten years, many of the world's best programmers worked
+at the Artificial Intelligence Lab for far less money than they could
+have had anywhere else. They got many kinds of non-monetary rewards:
+fame and appreciation, for example. And creativity is also fun, a
+reward in itself.
+
+ Then most of them left when offered a chance to do the same
+interesting work for a lot of money.
+
+ What the facts show is that people will program for reasons other
+than riches; but if given a chance to make a lot of money as well, they
+will come to expect and demand it. Low-paying organizations do poorly
+in competition with high-paying ones, but they do not have to do badly
+if the high-paying ones are banned.
+
+ "We need the programmers desperately. If they demand that we stop
+ helping our neighbors, we have to obey."
+
+ You're never so desperate that you have to obey this sort of demand.
+Remember: millions for defense, but not a cent for tribute!
+
+ "Programmers need to make a living somehow."
+
+ In the short run, this is true. However, there are plenty of ways
+that programmers could make a living without selling the right to use a
+program. This way is customary now because it brings programmers and
+businessmen the most money, not because it is the only way to make a
+living. It is easy to find other ways if you want to find them. Here
+are a number of examples.
+
+ A manufacturer introducing a new computer will pay for the porting of
+operating systems onto the new hardware.
+
+ The sale of teaching, hand-holding, and maintenance services could
+also employ programmers.
+
+ People with new ideas could distribute programs as freeware and ask
+for donations from satisfied users or sell hand-holding services. I
+have met people who are already working this way successfully.
+
+ Users with related needs can form users' groups and pay dues. A
+group would contract with programming companies to write programs that
+the group's members would like to use.
+
+ All sorts of development can be funded with a Software Tax:
+
+ Suppose everyone who buys a computer has to pay a certain percent
+ of the price as a software tax. The government gives this to an
+ agency like the NSF to spend on software development.
+
+ But if the computer buyer makes a donation to software development
+ himself, he can take a credit against the tax. He can donate to
+ the project of his own choosing--often, chosen because he hopes to
+ use the results when
+
+ it is done. He can take a credit for any amount of donation up to
+ the total tax he had to pay.
+
+ The total tax rate could be decided by a vote of the payers of the
+ tax, weighted according to the amount they will be taxed on.
+
+ The consequences:
+
+ * The computer-using community supports software development.
+
+ * This community decides what level of support is needed.
+
+ * Users who care which projects their share is spent on can
+ choose this for themselves.
-\1f
-File: xemacs.info, Node: Completion Options, Prev: Strict Completion, Up: Completion
-
-Completion Options
-------------------
-
- When completion is done on file names, certain file names are usually
-ignored. The variable `completion-ignored-extensions' contains a list
-of strings; a file whose name ends in any of those strings is ignored
-as a possible completion. The standard value of this variable has
-several elements including `".o"', `".elc"', `".dvi"' and `"~"'. The
-effect is that, for example, `foo' can complete to `foo.c' even though
-`foo.o' exists as well. However, if _all_ the possible completions end
-in "ignored" strings, then they are not ignored. Ignored extensions do
-not apply to lists of completions--those always mention all possible
-completions.
-
- If a completion command finds the next character is undetermined, it
-automatically displays a list of all possible completions. If the
-variable `completion-auto-help' is set to `nil', this does not happen,
-and you must type `?' to display the possible completions.
-
- If the variable `minibuffer-confirm-incomplete' is set to `t', then
-in contexts where `completing-read' allows answers that are not valid
-completions, an extra <RET> must be typed to confirm the response.
-This is helpful for catching typos.
+ In the long run, making programs free is a step toward the
+post-scarcity world, where nobody will have to work very hard just to
+make a living. People will be free to devote themselves to activities
+that are fun, such as programming, after spending the necessary ten
+hours a week on required tasks such as legislation, family counseling,
+robot repair, and asteroid prospecting. There will be no need to be
+able to make a living from programming.
-\1f
-File: xemacs.info, Node: Minibuffer History, Next: Repetition, Prev: Completion, Up: Minibuffer
-
-Minibuffer History
-==================
-
- Every argument that you enter with the minibuffer is saved on a
-"minibuffer history list" so that you can use it again later in another
-argument. Special commands load the text of an earlier argument in the
-minibuffer. They discard the old minibuffer contents, so you can think
-of them as moving through the history of previous arguments.
-
-`<UP>'
-`M-p'
- Move to the next earlier argument string saved in the minibuffer
- history (`previous-history-element').
-
-`<DOWN>'
-`M-n'
- Move to the next later argument string saved in the minibuffer
- history (`next-history-element').
-
-`M-r REGEXP <RET>'
- Move to an earlier saved argument in the minibuffer history that
- has a match for REGEXP (`previous-matching-history-element').
-
-`M-s REGEXP <RET>'
- Move to a later saved argument in the minibuffer history that has a
- match for REGEXP (`next-matching-history-element').
-
- The simplest way to reuse the saved arguments in the history list is
-to move through the history list one element at a time. While in the
-minibuffer, use `M-p' or up-arrow (`previous-history-element') to "move
-to" the next earlier minibuffer input, and use `M-n' or down-arrow
-(`next-history-element') to "move to" the next later input.
-
- The previous input that you fetch from the history entirely replaces
-the contents of the minibuffer. To use it as the argument, exit the
-minibuffer as usual with <RET>. You can also edit the text before you
-reuse it; this does not change the history element that you "moved" to,
-but your new argument does go at the end of the history list in its own
-right.
-
- For many minibuffer arguments there is a "default" value. In some
-cases, the minibuffer history commands know the default value. Then you
-can insert the default value into the minibuffer as text by using `M-n'
-to move "into the future" in the history.
-
- There are also commands to search forward or backward through the
-history; they search for history elements that match a regular
-expression that you specify with the minibuffer. `M-r'
-(`previous-matching-history-element') searches older elements in the
-history, while `M-s' (`next-matching-history-element') searches newer
-elements. By special dispensation, these commands can use the
-minibuffer to read their arguments even though you are already in the
-minibuffer when you issue them. As with incremental searching, an
-uppercase letter in the regular expression makes the search
-case-sensitive (*note Search Case::).
-
- All uses of the minibuffer record your input on a history list, but
-there are separate history lists for different kinds of arguments. For
-example, there is a list for file names, used by all the commands that
-read file names.
-
- There are several other very specific history lists, including one
-for command names read by `M-x', one for buffer names, one for arguments
-of commands like `query-replace', and one for compilation commands read
-by `compile'. Finally, there is one "miscellaneous" history list that
-most minibuffer arguments use.
-
-\1f
-File: xemacs.info, Node: Repetition, Prev: Minibuffer History, Up: Minibuffer
-
-Repeating Minibuffer Commands
-=============================
-
- Every command that uses the minibuffer at least once is recorded on a
-special history list, together with the values of its arguments, so that
-you can repeat the entire command. In particular, every use of `M-x'
-is recorded there, since `M-x' uses the minibuffer to read the command
-name.
-
-`C-x <ESC> <ESC>'
- Re-execute a recent minibuffer command (`repeat-complex-command').
-
-`M-p'
- Within `C-x <ESC>', move to previous recorded command
- (`previous-history-element').
-
-`M-n'
- Within `C-x <ESC>', move to the next (more recent) recorded
- command (`next-history-element').
-
-`M-x list-command-history'
- Display the entire command history, showing all the commands `C-x
- <ESC> <ESC>' can repeat, most recent first.
-
- `C-x <ESC> <ESC>' is used to re-execute a recent minibuffer-using
-command. With no argument, it repeats the last such command. A
-numeric argument specifies which command to repeat; one means the last
-one, and larger numbers specify earlier ones.
-
- `C-x <ESC> <ESC>' works by turning the previous command into a Lisp
-expression and then entering a minibuffer initialized with the text for
-that expression. If you type just <RET>, the command is repeated as
-before. You can also change the command by editing the Lisp
-expression. Whatever expression you finally submit is what will be
-executed. The repeated command is added to the front of the command
-history unless it is identical to the most recently executed command
-already there.
-
- Even if you don't understand Lisp syntax, it will probably be obvious
-which command is displayed for repetition. If you do not change the
-text, you can be sure the command will repeat exactly as before.
-
- If you are in the minibuffer for `C-x <ESC> <ESC>' and the command
-shown to you is not the one you want to repeat, you can move around the
-list of previous commands using `M-n' and `M-p'. `M-p' replaces the
-contents of the minibuffer with the next earlier recorded command, and
-`M-n' replaces it with the next later command. After finding the
-desired previous command, you can edit its expression and then resubmit
-it by typing <RET>. Any editing you have done on the command to be
-repeated is lost if you use `M-n' or `M-p'.
-
- `M-n' and `M-p' are specially defined within `C-x <ESC> <ESC>' to
-run the commands `previous-history-element' and `next-history-element'.
-
- The list of previous commands using the minibuffer is stored as a
-Lisp list in the variable `command-history'. Each element of the list
-is a Lisp expression which describes one command and its arguments.
-Lisp programs can reexecute a command by feeding the corresponding
-`command-history' element to `eval'.
+ We have already greatly reduced the amount of work that the whole
+society must do for its actual productivity, but only a little of this
+has translated itself into leisure for workers because much
+nonproductive activity is required to accompany productive activity.
+The main causes of this are bureaucracy and isometric struggles against
+competition. Free software will greatly reduce these drains in the
+area of software production. We must do this, in order for technical
+gains in productivity to translate into less work for us.
\1f
-File: xemacs.info, Node: M-x, Next: Help, Prev: Minibuffer, Up: Top
-
-Running Commands by Name
-************************
-
- The Emacs commands that are used often or that must be quick to type
-are bound to keys--short sequences of characters--for convenient use.
-Other Emacs commands that are used more rarely are not bound to keys;
-to run them, you must refer to them by name.
-
- A command name consists, by convention, of one or more words,
-separated by hyphens: for example, `auto-fill-mode' or `manual-entry'.
-The use of English words makes the command name easier to remember than
-a key made up of obscure characters, even though it results in more
-characters to type. You can run any command by name, even if it can be
-run by keys as well.
-
- To run a command by name, start with `M-x', then type the command
-name, and finish with <RET>. `M-x' uses the minibuffer to read the
-command name. <RET> exits the minibuffer and runs the command.
-
- Emacs uses the minibuffer for reading input for many different
-purposes; on this occasion, the string `M-x' is displayed at the
-beginning of the minibuffer as a "prompt" to remind you that your input
-should be the name of a command to be run. *Note Minibuffer::, for
-full information on the features of the minibuffer.
-
- You can use completion to enter a command name. For example, to
-invoke the command `forward-char', type:
-
- M-x forward-char <RET>
- or
- M-x fo <TAB> c <RET>
-
-After you type in `M-x fo TAB' emacs will give you a possible list of
-completions from which you can choose. Note that `forward-char' is the
-same command that you invoke with the key `C-f'. You can call any
-command (interactively callable function) defined in Emacs by its name
-using `M-x' regardless of whether or not any keys are bound to it.
-
- If you type `C-g' while Emacs reads the command name, you cancel the
-`M-x' command and get out of the minibuffer, ending up at top level.
-
- To pass a numeric argument to a command you are invoking with `M-x',
-specify the numeric argument before the `M-x'. `M-x' passes the
-argument along to the function that it calls. The argument value
-appears in the prompt while the command name is being read.
-
- You can use the command `M-x interactive' to specify a way of
-parsing arguments for interactive use of a function. For example,
-write:
-
- (defun foo (arg) "Doc string" (interactive "p") ...use arg...)
-
- to make `arg' be the prefix argument when `foo' is called as a
-command. The call to `interactive' is actually a declaration rather
-than a function; it tells `call-interactively' how to read arguments to
-pass to the function. When actually called, `interactive' returns
-`nil'.
-
- The argument of INTERACTIVE is usually a string containing a code
-letter followed by a prompt. Some code letters do not use I/O to get
-the argument and do not need prompts. To prompt for multiple arguments,
-you must provide a code letter, its prompt, a newline, and another code
-letter, and so forth. If the argument is not a string, it is evaluated
-to get a list of arguments to pass to the function. If you do not
-provide an argument to `interactive', no arguments are passed when
-calling interactively.
-
- Available code letters are:
-
-`a'
- Function name: symbol with a function definition
-
-`b'
- Name of existing buffer
-
-`B'
- Name of buffer, possibly nonexistent
-
-`c'
- Character
-
-`C'
- Command name: symbol with interactive function definition
-
-`d'
- Value of point as number (does not do I/O)
-
-`D'
- Directory name
-
-`e'
- Last mouse event
+File: xemacs.info, Node: Key Index, Next: Command Index, Prev: Manifesto, Up: Top
-`f'
- Existing file name
-
-`F'
- Possibly nonexistent file name
-
-`k'
- Key sequence (string)
-
-`m'
- Value of mark as number (does not do I/O)
-
-`n'
- Number read using minibuffer
-
-`N'
- Prefix arg converted to number, or if none, do like code `n'
-
-`p'
- Prefix arg converted to number (does not do I/O)
-
-`P'
- Prefix arg in raw form (does not do I/O)
-
-`r'
- Region: point and mark as two numeric arguments, smallest first
- (does not do I/O)
-
-`s'
- Any string
-
-`S'
- Any symbol
-
-`v'
- Variable name: symbol that is `user-variable-p'
-
-`x'
- Lisp expression read but not evaluated
-
-`X'
- Lisp expression read and evaluated
-
- In addition, if the string begins with `*', an error is signaled if
-the buffer is read-only. This happens before reading any arguments.
-If the string begins with `@', the window the mouse is over is selected
-before anything else is done. You may use both `@' and `*'; they are
-processed in the order that they appear.
-
- Normally, when describing a command that is run by name, we omit the
-<RET> that is needed to terminate the name. Thus we may refer to `M-x
-auto-fill-mode' rather than `M-x auto-fill-mode' <RET>. We mention the
-<RET> only when it is necessary to emphasize its presence, for example,
-when describing a sequence of input that contains a command name and
-arguments that follow it.
-
- `M-x' is defined to run the command `execute-extended-command',
-which is responsible for reading the name of another command and
-invoking it.
-
-\1f
-File: xemacs.info, Node: Help, Next: Mark, Prev: M-x, Up: Top
-
-Help
-****
-
- XEmacs provides extensive help features accessible through a single
-character, `C-h'. `C-h' is a prefix key that is used only for
-documentation-printing commands. The characters that you can type after
-`C-h' are called "help options". One help option is `C-h'; that is how
-you ask for help about using `C-h'. To cancel, type `C-g'. The
-function key <F1> is equivalent to `C-h'.
-
- `C-h C-h' (`help-for-help') displays a list of the possible help
-options, and then asks you to type the desired option. It prompts with
-the string:
-
- A B C F I K L M N P S T V W C-c C-d C-f C-i C-k C-n C-w; ? for more help:
-
-You should type one of those characters.
-
- Typing a third `C-h' displays a description of what the options mean;
-Emacs still waits for you to type an option. To cancel, type `C-g'.
-
- Most help buffers use a special major mode, Help mode, which lets you
-scroll conveniently with <SPC> and <DEL> or <BS>.
+Key (Character) Index
+*********************
+\0\b[index\0\b]
* Menu:
-* Help Summary:: Brief list of all Help commands.
-* Key Help:: Asking what a key does in XEmacs.
-* Name Help:: Asking about a command, variable or function name.
-* Apropos:: Asking what pertains to a given topic.
-* Library Keywords:: Finding Lisp libraries by keywords (topics).
-* Help Mode:: Special features of Help mode and Help buffers.
-* Misc Help:: Other help commands.
-
-\1f
-File: xemacs.info, Node: Help Summary, Next: Key Help, Prev: Help, Up: Help
-
-Help Summary
-============
-
- Here is a summary of the defined help commands.
-
-`C-h a REGEXP <RET>'
- Display a list of functions and variables whose names match REGEXP
- (`heper-apropos').
-
-`C-h A REGEXP'
- Show all commands whose names contain matches for REGEXP
- (`command-apropos').
-
-`C-h b'
- Display a table of all key bindings currently in effect, with local
- bindings of the current major mode first, followed by all global
- bindings (`describe-bindings').
-
-`C-h c KEY'
- Print the name of the command that KEY runs
- (`describe-key-briefly'). Here `c' stands for `character'. For
- more extensive information on KEY, use `C-h k'.
-
-`C-h d FUNCTION <RET>'
-`C-h f FUNCTION <RET>'
- Display documentation on the Lisp function named FUNCTION
- (`describe-function'). Since commands are Lisp functions, a
- command name may be used.
-
-`C-h i'
- Run Info, the program for browsing documentation files (`info').
- The complete XEmacs manual is available online in Info.
-
-`C-h k KEY'
- Display the name and documentation of the command that KEY runs
- (`describe-key').
-
-`C-h l'
- Display a description of the last 100 characters you typed
- (`view-lossage').
-
-`C-h m'
- Display documentation of the current major mode (`describe-mode').
-
-`C-h n'
-`C-h C-n'
- Display documentation of XEmacs changes, most recent first
- (`view-emacs-news').
-
-`C-h p'
- Find packages by topic keyword (`finder-by-keyword').
-
-`C-h C-p'
- Display a table of all mouse bindings currently in effect now, with
- local bindings of the current major mode first, followed by all
- global bindings (`describe-pointer').
-
-`C-h s'
- Display current contents of the syntax table, plus an explanation
- of what they mean (`describe-syntax'). *Note Syntax::.
-
-`C-h t'
- Enter the XEmacs interactive tutorial (`help-with-tutorial').
-
-`C-h v VAR <RET>'
- Display the documentation of the Lisp variable VAR
- (`describe-variable').
-
-`C-h w COMMAND <RET>'
- Print which keys run the command named COMMAND (`where-is').
-
-`C-h B <RET>'
- Display info on how to deal with Beta versions of XEmacs
- (`describe-beta').
-
-`C-h C GROUP <RET>'
- Select customization buffer for GROUP (`customize').
-
-`C-h F <RET>'
- View the local copy of the XEmacs FAQ (`xemacs-local-faq').
-
-`C-h C-i FILE <RET>'
- Read Info file FILE with Info browser (`Info-query').
-
-`C-h C-c COMMAND <RET>'
- Look up an Emacs command COMMAND in the Emacs manual in the Info
- system (`Info-goto-emacs-command-node').
-
-`C-h C-f FUNCTION <RET>'
- Look up an Emacs Lisp function FUNCTION in the Elisp manual in the
- Info system (`Info-elisp-ref').
-
-\1f
-File: xemacs.info, Node: Key Help, Next: Name Help, Prev: Help Summary, Up: Help
-
-Documentation for a Key
-=======================
-
- The most basic `C-h' options are `C-h c' (`describe-key-briefly')
-and `C-h k' (`describe-key'). `C-h c KEY' prints in the echo area the
-name of the command that KEY is bound to. For example, `C-h c C-f'
-prints `forward-char'. Since command names are chosen to describe what
-the commands do, this is a good way to get a very brief description of
-what KEY does.
-
- `C-h k KEY' is similar to `C-h c' but gives more information. It
-displays the documentation string of the function KEY is bound to as
-well as its name. KEY is a string or vector of events. When called
-interactively, KEY may also be a menu selection. This information does
-not usually fit into the echo area, so a window is used for the display.
-
- `C-h c' and `C-h k' work for any sort of key sequences, including
-function keys and mouse events.
-
-\1f
-File: xemacs.info, Node: Name Help, Next: Apropos, Prev: Key Help, Up: Help
-
-Help by Command or Variable Name
-================================
-
- `C-h f' (`describe-function') reads the name of a Lisp function
-using the minibuffer, then displays that function's documentation
-string in a window. Since commands are Lisp functions, you can use the
-argument FUNCTION to get the documentation of a command that you know
-by name. For example,
-
- C-h f auto-fill-mode <RET>
-
-displays the documentation for `auto-fill-mode'. Using `C-h f' is the
-only way to see the documentation of a command that is not bound to any
-key, that is, a command you would normally call using `M-x'. If the
-variable `describe-function-show-arglist' is `t', `describe-function'
-shows its arglist if the FUNCTION is not an autoload function.
-
- `C-h f' is also useful for Lisp functions that you are planning to
-use in a Lisp program. For example, if you have just written the
-expression `(make-vector len)' and want to make sure you are using
-`make-vector' properly, type `C-h f make-vector <RET>'. Because `C-h
-f' allows all function names, not just command names, you may find that
-some of your favorite abbreviations that work in `M-x' don't work in
-`C-h f'. An abbreviation may be unique among command names, yet fail
-to be unique when other function names are allowed.
-
- The function name for `C-h f' to describe has a default which is
-used if you type <RET> leaving the minibuffer empty. The default is
-the function called by the innermost Lisp expression in the buffer
-around point, _provided_ that is a valid, defined Lisp function name.
-For example, if point is located following the text `(make-vector (car
-x)', the innermost list containing point is the one that starts with
-`(make-vector', so the default is to describe the function
-`make-vector'.
-
- `C-h f' is often useful just to verify that you have the right
-spelling for the function name. If `C-h f' mentions a name from the
-buffer as the default, that name must be defined as a Lisp function. If
-that is all you want to know, just type `C-g' to cancel the `C-h f'
-command, then go on editing.
-
- `C-h w COMMAND <RET>' (`where-is') tells you what keys are bound to
-COMMAND. It prints a list of the keys in the echo area. Alternatively,
-it informs you that a command is not bound to any keys, which implies
-that you must use `M-x' to call the command.
-
- `C-h v' (`describe-variable') is like `C-h f' but describes Lisp
-variables instead of Lisp functions. Its default is the Lisp symbol
-around or before point, if that is the name of a known Lisp variable.
-*Note Variables::.
-
-\1f
-File: xemacs.info, Node: Apropos, Next: Library Keywords, Prev: Name Help, Up: Help
-
-Apropos
-=======
-
-`C-h A'
- Show only symbols that are names of commands (`command-apropos').
-
-`M-x apropos REGEXP'
- Show all symbols whose names comtain matches for REGEXP.
-
- A more sophisticated sort of question to ask is, "What are the
-commands for working with files?" To ask this question, type `C-h a
-file <RET>', which displays a list of all command names that contain
-`file', including `copy-file', `find-file', and so on. With each
-command name appears a brief description of how to use the command, and
-what keys you can currently invoke it with. For example, it would say
-that you can invoke `find-file' by typing `C-x C-f'. The `A' in `C-h
-A' stands for `Apropos'; `C-h A' runs the command `command-apropos'.
-This command normally checks only commands (interactive functions); if
-you specify a prefix argument, it checks noninteractive functions as
-well.
-
- Because `C-h A' looks only for functions whose names contain the
-string you specify, you must use ingenuity in choosing the string. If
-you are looking for commands for killing backwards and `C-h a
-kill-backwards <RET>' doesn't reveal any, don't give up. Try just
-`kill', or just `backwards', or just `back'. Be persistent. Pretend
-you are playing Adventure. Also note that you can use a regular
-expression as the argument, for more flexibility (*note Regexps::).
-
- Here is a set of arguments to give to `C-h a' that covers many
-classes of XEmacs commands, since there are strong conventions for
-naming the standard XEmacs commands. By giving you a feel for the
-naming conventions, this set should also serve to aid you in developing
-a technique for picking `apropos' strings.
-
- char, line, word, sentence, paragraph, region, page, sexp, list,
- defun, rect, buffer, frame, window, face, file, dir, register,
- mode, beginning, end, forward, backward, next, previous, up, down,
- search, goto, kill, delete, mark, insert, yank, fill, indent,
- case, change, set, what, list, find, view, describe, default.
-
- To list all Lisp symbols that contain a match for a regexp, not just
-the ones that are defined as commands, use the command `M-x apropos'
-instead of `C-h A'. This command does not check key bindings by
-default; specify a numeric argument if you want it to check them.
-
- The `apropos-documentation' command is like `apropos' except that it
-searches documentation strings for matches for the specified regular
-expression.
-
- The `apropos-value' command is like `apropos' except that it
-searches symbols' values for matches for the specified regular
-expression. This command does not check function definitions or
-property lists by default; specify a numeric argument if you want it to
-check them.
-
- If the variable `apropos-do-all' is non-`nil', the commands above
-all behave as if they had been given a prefix argument.
-
- If you want more information about a function definition, variable or
-symbol property listed in the Apropos buffer, you can click on it with
-`Mouse-2' or move there and type <RET>.
+* ! (query-replace): Query Replace. (line 27)
+* " (TeX mode): TeX Editing. (line 31)
+* , (query-replace): Query Replace. (line 27)
+* . (Calendar mode): Specified Dates. (line 26)
+* . (query-replace): Query Replace. (line 27)
+* ? (Calendar mode): General Calendar. (line 26)
+* ^ (query-replace): Query Replace. (line 27)
+* a (Calendar mode): Holidays. (line 48)
+* BS: Inserting Text. (line 13)
+* button1: Intro to Keystrokes. (line 16)
+* button1up: Intro to Keystrokes. (line 16)
+* button2: Intro to Keystrokes. (line 16)
+* button2up: Intro to Keystrokes. (line 16)
+* button3: Intro to Keystrokes. (line 16)
+* button3up: Intro to Keystrokes. (line 16)
+* C-<: Setting Mark. (line 50)
+* C->: Setting Mark. (line 50)
+* C-@ (Calendar mode): Mark and Region. (line 24)
+* C-\: Select Input Method. (line 26)
+* C-] <1>: Quitting. (line 44)
+* C-]: Recursive Edit. (line 18)
+* C-_: Undo. (line 20)
+* C-a: Moving Point. (line 15)
+* C-a (Calendar mode): Move to Beginning or End.
+ (line 11)
+* C-b: Moving Point. (line 15)
+* C-b (Calendar mode): Calendar Unit Motion.
+ (line 34)
+* C-c: Key Sequences. (line 29)
+* C-c ' (Picture mode): Insert in Picture. (line 6)
+* C-c . (Picture mode): Insert in Picture. (line 6)
+* C-c / (Picture mode): Insert in Picture. (line 6)
+* C-c ; (Fortran mode): Fortran Comments. (line 71)
+* C-c < (Picture mode): Insert in Picture. (line 6)
+* C-c > (Picture mode): Insert in Picture. (line 6)
+* C-c \ (Picture mode): Insert in Picture. (line 6)
+* C-c ^ (Picture mode): Insert in Picture. (line 6)
+* C-c ` (Picture mode): Insert in Picture. (line 6)
+* C-c C-\ (Shell mode): Shell Mode. (line 12)
+* C-c C-b (Outline mode): Outline Motion. (line 36)
+* C-c C-b (Picture mode): Insert in Picture. (line 40)
+* C-c C-b (TeX mode): TeX Print. (line 32)
+* C-c C-c (Edit Abbrevs): Editing Abbrevs. (line 34)
+* C-c C-c (Edit Tab Stops): Tab Stops. (line 11)
+* C-c C-c (Mail mode): Mail Mode. (line 45)
+* C-c C-c (Occur mode): Other Repeating Search.
+ (line 15)
+* C-c C-c (Shell mode): Shell Mode. (line 12)
+* C-c C-d (Outline mode): Outline Visibility. (line 48)
+* C-c C-d (Picture mode): Basic Picture. (line 41)
+* C-c C-d (Shell mode): Shell Mode. (line 12)
+* C-c C-f (LaTeX mode): TeX Editing. (line 72)
+* C-c C-f (Outline mode): Outline Motion. (line 36)
+* C-c C-f (Picture mode): Insert in Picture. (line 40)
+* C-c C-f C-c (Mail mode): Mail Mode. (line 54)
+* C-c C-f C-s (Mail mode): Mail Mode. (line 54)
+* C-c C-f C-t (Mail mode): Mail Mode. (line 54)
+* C-c C-h (Outline mode): Outline Visibility. (line 48)
+* C-c C-i (Outline mode): Outline Visibility. (line 62)
+* C-c C-j (Term mode): Term Mode. (line 12)
+* C-c C-k (Picture mode): Rectangles in Picture.
+ (line 27)
+* C-c C-k (Term mode): Term Mode. (line 17)
+* C-c C-k (TeX mode): TeX Print. (line 38)
+* C-c C-l (Calendar mode): General Calendar. (line 33)
+* C-c C-l (TeX mode): TeX Print. (line 38)
+* C-c C-n (Fortran mode): Fortran Motion. (line 11)
+* C-c C-n (Outline mode): Outline Motion. (line 29)
+* C-c C-o (Shell mode): Shell Mode. (line 12)
+* C-c C-p (Fortran mode): Fortran Motion. (line 11)
+* C-c C-p (Outline mode): Outline Motion. (line 29)
+* C-c C-p (TeX mode): TeX Print. (line 32)
+* C-c C-q (Mail mode): Mail Mode. (line 78)
+* C-c C-q (Term mode): Paging in Term. (line 9)
+* C-c C-q (TeX mode): TeX Print. (line 32)
+* C-c C-r (Fortran mode): Fortran Columns. (line 15)
+* C-c C-r (Shell mode): Shell Mode. (line 12)
+* C-c C-r (TeX mode): TeX Print. (line 48)
+* C-c C-s (Mail mode): Mail Mode. (line 45)
+* C-c C-u (Outline mode): Outline Motion. (line 36)
+* C-c C-u (Shell mode): Shell Mode. (line 12)
+* C-c C-w (Fortran mode): Fortran Columns. (line 30)
+* C-c C-w (Mail mode): Mail Mode. (line 63)
+* C-c C-w (Picture mode): Rectangles in Picture.
+ (line 27)
+* C-c C-w (Shell mode): Shell Mode. (line 12)
+* C-c C-x (Picture mode): Rectangles in Picture.
+ (line 36)
+* C-c C-y (Mail mode): Mail Mode. (line 67)
+* C-c C-y (Picture mode): Rectangles in Picture.
+ (line 36)
+* C-c C-y (Shell mode): Shell Mode. (line 12)
+* C-c C-z (Shell mode): Shell Mode. (line 12)
+* C-c TAB (Picture mode): Tabs in Picture. (line 23)
+* C-c { (TeX mode): TeX Editing. (line 49)
+* C-c } (TeX mode): TeX Editing. (line 49)
+* C-d: Killing. (line 6)
+* C-d (Shell mode): Shell Mode. (line 12)
+* C-e: Moving Point. (line 15)
+* C-e (Calendar mode): Move to Beginning or End.
+ (line 12)
+* C-END: Moving Point. (line 15)
+* C-f: Moving Point. (line 15)
+* C-f (Calendar mode): Calendar Unit Motion.
+ (line 34)
+* C-g <1>: Quitting. (line 26)
+* C-g: Minibuffer. (line 26)
+* C-g (isearch-mode): Incremental Search. (line 130)
+* C-h <1>: Help. (line 6)
+* C-h: Key Sequences. (line 29)
+* C-h A: Apropos. (line 6)
+* C-h b: Misc Help. (line 37)
+* C-h c: Key Help. (line 6)
+* C-h C-\: Select Input Method. (line 14)
+* C-h C-c: Misc Help. (line 51)
+* C-h C-d: Misc Help. (line 51)
+* C-h C-f: Misc Help. (line 18)
+* C-h C-h: Help. (line 13)
+* C-h C-k: Misc Help. (line 18)
+* C-h C-w: Misc Help. (line 51)
+* C-h f: Documentation. (line 6)
+* C-h F: Misc Help. (line 51)
+* C-h f: Name Help. (line 6)
+* C-h h: Mule Intro. (line 59)
+* C-h I: Select Input Method. (line 14)
+* C-h i: Misc Help. (line 6)
+* C-h k: Key Help. (line 13)
+* C-h L: Language Environments.
+ (line 36)
+* C-h l: Misc Help. (line 27)
+* C-h m: Misc Help. (line 32)
+* C-h n: Misc Help. (line 51)
+* C-h p: Library Keywords. (line 6)
+* C-h s: Syntax Change. (line 48)
+* C-h t <1>: Misc Help. (line 51)
+* C-h t: Basic. (line 6)
+* C-h v <1>: Examining. (line 13)
+* C-h v <2>: Documentation. (line 6)
+* C-h v: Name Help. (line 49)
+* C-h w: Name Help. (line 44)
+* C-HOME: Moving Point. (line 15)
+* C-k: Killing. (line 73)
+* C-l <1>: Scrolling. (line 37)
+* C-l: Moving Point. (line 15)
+* C-l (query-replace): Query Replace. (line 27)
+* C-LEFT: Moving Point. (line 15)
+* C-M-@ <1>: Lists. (line 114)
+* C-M-@: Marking Objects. (line 28)
+* C-M-\ <1>: Multi-line Indent. (line 35)
+* C-M-\: Indentation Commands.
+ (line 33)
+* C-M-a: Defuns. (line 23)
+* C-M-a (Fortran mode): Fortran Motion. (line 11)
+* C-M-b: Lists. (line 67)
+* C-M-c: Recursive Edit. (line 13)
+* C-M-d: Lists. (line 96)
+* C-M-e: Defuns. (line 23)
+* C-M-e (Fortran mode): Fortran Motion. (line 11)
+* C-M-f: Lists. (line 67)
+* C-M-h <1>: Defuns. (line 23)
+* C-M-h: Marking Objects. (line 32)
+* C-M-h (Fortran mode): Fortran Motion. (line 11)
+* C-M-k <1>: Lists. (line 87)
+* C-M-k: Killing. (line 100)
+* C-M-n: Lists. (line 90)
+* C-M-o: Indentation Commands.
+ (line 17)
+* C-M-p: Lists. (line 90)
+* C-M-q: Multi-line Indent. (line 19)
+* C-M-q (Fortran mode): ForIndent Commands. (line 21)
+* C-M-t <1>: Lists. (line 108)
+* C-M-t: Transpose. (line 30)
+* C-M-u: Lists. (line 96)
+* C-M-v <1>: Other Window. (line 40)
+* C-M-v: Minibuffer Edit. (line 33)
+* C-M-w: Appending Kills. (line 33)
+* C-M-x <1>: External Lisp. (line 27)
+* C-M-x: Lisp Eval. (line 44)
+* C-n: Moving Point. (line 15)
+* C-n (Calendar mode): Calendar Unit Motion.
+ (line 34)
+* C-o: Blank Lines. (line 16)
+* C-p: Moving Point. (line 15)
+* C-p (Calendar mode): Calendar Unit Motion.
+ (line 34)
+* C-q: Inserting Text. (line 33)
+* C-q (isearch-mode): Incremental Search. (line 130)
+* C-r: Incremental Search. (line 19)
+* C-r (isearch-mode): Incremental Search. (line 130)
+* C-r (query-replace): Query Replace. (line 27)
+* C-RIGHT: Moving Point. (line 15)
+* C-s: Incremental Search. (line 19)
+* C-s (isearch-mode): Incremental Search. (line 130)
+* C-SPC: Setting Mark. (line 32)
+* C-SPC (Calendar mode): Mark and Region. (line 24)
+* C-t <1>: Transpose. (line 18)
+* C-t: Moving Point. (line 15)
+* C-u: Arguments. (line 28)
+* C-u - C-x ;: Comments. (line 58)
+* C-u C-@: Mark Ring. (line 6)
+* C-u C-SPC: Mark Ring. (line 6)
+* C-u C-x v v: Editing with VC. (line 107)
+* C-u TAB: Multi-line Indent. (line 27)
+* C-v <1>: Scrolling. (line 42)
+* C-v: Moving Point. (line 15)
+* C-v (Calendar mode): Scroll Calendar. (line 35)
+* C-w: Killing. (line 100)
+* C-w (isearch-mode): Incremental Search. (line 130)
+* C-w (query-replace): Query Replace. (line 27)
+* C-x: Key Sequences. (line 29)
+* C-x $: Selective Display. (line 6)
+* C-x (: Basic Kbd Macro. (line 6)
+* C-x ): Basic Kbd Macro. (line 6)
+* C-x .: Fill Prefix. (line 22)
+* C-x 0: Change Window. (line 23)
+* C-x 1: Change Window. (line 31)
+* C-x 2: Split Window. (line 21)
+* C-x 3: Split Window. (line 28)
+* C-x 4: Pop Up Window. (line 6)
+* C-x 4 .: Find Tag. (line 67)
+* C-x 4 b: Select Buffer. (line 16)
+* C-x 4 d: Dired Enter. (line 16)
+* C-x 4 f: Visiting. (line 108)
+* C-x 4 m: Sending Mail. (line 22)
+* C-x 5 b: Select Buffer. (line 16)
+* C-x 5 C-f: Visiting. (line 46)
+* C-x ;: Comments. (line 84)
+* C-x <: Horizontal Scrolling.
+ (line 12)
+* C-x < (Calendar mode): Scroll Calendar. (line 28)
+* C-x <RET> C: Coding Systems. (line 39)
+* C-x =: Position Info. (line 47)
+* C-x >: Horizontal Scrolling.
+ (line 12)
+* C-x > (Calendar mode): Scroll Calendar. (line 28)
+* C-x [: Pages. (line 28)
+* C-x [ (Calendar mode): Calendar Unit Motion.
+ (line 43)
+* C-x ]: Pages. (line 28)
+* C-x ] (Calendar mode): Calendar Unit Motion.
+ (line 43)
+* C-x ^: Change Window. (line 36)
+* C-x `: Compilation. (line 58)
+* C-x a g: Defining Abbrevs. (line 25)
+* C-x a i g: Defining Abbrevs. (line 44)
+* C-x a i l: Defining Abbrevs. (line 44)
+* C-x a l: Defining Abbrevs. (line 38)
+* C-x b: Select Buffer. (line 16)
+* C-x C-b: List Buffers. (line 9)
+* C-x C-c: Exiting. (line 64)
+* C-x C-d: ListDir. (line 17)
+* C-x C-e: Lisp Eval. (line 50)
+* C-x C-l: Case. (line 46)
+* C-x C-o <1>: Killing. (line 53)
+* C-x C-o: Blank Lines. (line 16)
+* C-x C-p <1>: Pages. (line 34)
+* C-x C-p: Marking Objects. (line 32)
+* C-x C-q: Misc Buffer. (line 15)
+* C-x C-q (version control): Editing with VC. (line 33)
+* C-x C-s: Saving. (line 26)
+* C-x C-t: Transpose. (line 30)
+* C-x C-u: Case. (line 46)
+* C-x C-v: Visiting. (line 96)
+* C-x C-w: Saving. (line 73)
+* C-x C-x: Setting Mark. (line 42)
+* C-x C-x (Calendar mode): Mark and Region. (line 24)
+* C-x d: Dired Enter. (line 6)
+* C-x DEL <1>: Sentences. (line 37)
+* C-x DEL <2>: Kill Errors. (line 19)
+* C-x DEL: Killing. (line 100)
+* C-x e: Basic Kbd Macro. (line 6)
+* C-x ESC ESC: Repetition. (line 27)
+* C-x f: Fill Commands. (line 53)
+* C-x h: Marking Objects. (line 32)
+* C-x k: Kill Buffer. (line 16)
+* C-x l: Pages. (line 46)
+* C-x m: Sending Mail. (line 22)
+* C-x n n: Narrowing. (line 28)
+* C-x n w: Narrowing. (line 39)
+* C-x o: Other Window. (line 20)
+* C-x q: Kbd Macro Query. (line 6)
+* C-x r +: RegNumbers. (line 14)
+* C-x r b: Bookmarks. (line 30)
+* C-x r g: RegText. (line 21)
+* C-x r i: RegText. (line 21)
+* C-x r j: RegPos. (line 20)
+* C-x r l: Bookmarks. (line 37)
+* C-x r m: Bookmarks. (line 30)
+* C-x r n: RegNumbers. (line 11)
+* C-x r r: RegRect. (line 11)
+* C-x r s: RegText. (line 21)
+* C-x r SPC: RegPos. (line 16)
+* C-x r w: RegConfig. (line 6)
+* C-x RET: Mule Intro. (line 68)
+* C-x RET c: Specify Coding. (line 34)
+* C-x RET C-\: Select Input Method. (line 20)
+* C-x RET f: Specify Coding. (line 27)
+* C-x RET k: Specify Coding. (line 73)
+* C-x RET p: Specify Coding. (line 91)
+* C-x RET t: Specify Coding. (line 62)
+* C-x s: Saving. (line 39)
+* C-x TAB: Indentation Commands.
+ (line 33)
+* C-x u: Undo. (line 20)
+* C-x v =: Old Versions. (line 22)
+* C-x v a: Change Logs and VC. (line 11)
+* C-x v c: Editing with VC. (line 76)
+* C-x v d: VC Status. (line 11)
+* C-x v h: Version Headers. (line 11)
+* C-x v i: Editing with VC. (line 92)
+* C-x v l: VC Status. (line 6)
+* C-x v r: Making Snapshots. (line 14)
+* C-x v s: Making Snapshots. (line 9)
+* C-x v u: Editing with VC. (line 66)
+* C-x v ~: Old Versions. (line 17)
+* C-x }: Change Window. (line 36)
+* C-y: Kill Ring. (line 6)
+* C-y (isearch-mode): Incremental Search. (line 130)
+* C-z: Exiting. (line 39)
+* control key: Intro to Keystrokes. (line 16)
+* d (Calendar mode): Diary Commands. (line 35)
+* DEL <1>: Program Modes. (line 50)
+* DEL <2>: Major Modes. (line 6)
+* DEL <3>: Kill Errors. (line 15)
+* DEL: Killing. (line 6)
+* DEL (isearch-mode): Incremental Search. (line 130)
+* DEL (query-replace): Query Replace. (line 27)
+* DOWN: Moving Point. (line 6)
+* END: Moving Point. (line 15)
+* ESC <1>: Meta Key. (line 6)
+* ESC: Key Sequences. (line 29)
+* ESC (query-replace): Query Replace. (line 27)
+* F1: Help. (line 6)
+* g CHAR (Calendar mode): From Other Calendar. (line 10)
+* g d (Calendar mode): Specified Dates. (line 18)
+* g m l (Calendar mode): Mayan Calendar. (line 42)
+* h (Calendar mode): Holidays. (line 33)
+* Help: Help. (line 6)
+* HOME: Moving Point. (line 15)
+* hyper key <1>: Super and Hyper Keys.
+ (line 6)
+* hyper key <2>: Representing Keystrokes.
+ (line 6)
+* hyper key: Intro to Keystrokes. (line 16)
+* i a (Calendar mode): Special Diary Entries.
+ (line 29)
+* i b (Calendar mode): Special Diary Entries.
+ (line 56)
+* i c (Calendar mode): Special Diary Entries.
+ (line 61)
+* i d (Calendar mode): Adding to Diary. (line 24)
+* i m (Calendar mode): Adding to Diary. (line 29)
+* i w (Calendar mode): Adding to Diary. (line 29)
+* i y (Calendar mode): Adding to Diary. (line 29)
+* LEFT: Moving Point. (line 6)
+* LFD <1>: Basic Indent. (line 26)
+* LFD <2>: Major Modes. (line 6)
+* LFD: String Key Sequences.
+ (line 15)
+* LFD (TeX mode): TeX Editing. (line 55)
+* m (Calendar mode): Diary Commands. (line 47)
+* M (Calendar mode): Lunar Phases. (line 19)
+* M-!: Single Shell. (line 6)
+* M-$: Spelling. (line 18)
+* M-%: Query Replace. (line 13)
+* M-': Expanding Abbrevs. (line 32)
+* M-(: Balanced Editing. (line 13)
+* M-): Balanced Editing. (line 13)
+* M-,: Tags Search. (line 28)
+* M--: Arguments. (line 16)
+* M-- M-c: Fixing Case. (line 16)
+* M-- M-l: Fixing Case. (line 16)
+* M-- M-u: Fixing Case. (line 16)
+* M-.: Find Tag. (line 19)
+* M-/: Dynamic Abbrevs. (line 12)
+* M-1: Arguments. (line 16)
+* M-:: Lisp Eval. (line 38)
+* M-;: Comments. (line 6)
+* M-<: Moving Point. (line 15)
+* M-< (Calendar mode): Move to Beginning or End.
+ (line 21)
+* M-=: Position Info. (line 31)
+* M-= (Calendar mode): Mark and Region. (line 31)
+* M->: Moving Point. (line 15)
+* M-> (Calendar mode): Move to Beginning or End.
+ (line 24)
+* M-?: Nroff Mode. (line 14)
+* M-@ <1>: Words. (line 61)
+* M-@: Marking Objects. (line 28)
+* M-\ <1>: Indentation Commands.
+ (line 24)
+* M-\: Killing. (line 53)
+* M-^ <1>: Indentation Commands.
+ (line 24)
+* M-^: Killing. (line 53)
+* M-a: Sentences. (line 22)
+* M-a (Calendar mode): Move to Beginning or End.
+ (line 15)
+* M-b: Words. (line 32)
+* M-c: Case. (line 24)
+* M-C-r: Regexp Search. (line 28)
+* M-C-s: Regexp Search. (line 28)
+* M-d <1>: Words. (line 41)
+* M-d: Killing. (line 100)
+* M-DEL <1>: Words. (line 50)
+* M-DEL <2>: Kill Errors. (line 19)
+* M-DEL: Killing. (line 100)
+* M-e: Sentences. (line 22)
+* M-e (Calendar mode): Move to Beginning or End.
+ (line 18)
+* M-f: Words. (line 32)
+* M-g: Fill Commands. (line 27)
+* M-h <1>: Paragraphs. (line 31)
+* M-h: Marking Objects. (line 32)
+* M-i: Tab Stops. (line 6)
+* M-k <1>: Sentences. (line 37)
+* M-k: Killing. (line 100)
+* M-l: Case. (line 24)
+* M-LFD: Comments. (line 72)
+* M-LFD (Fortran mode): ForIndent Commands. (line 25)
+* M-m: Indentation Commands.
+ (line 9)
+* M-n <1>: Nroff Mode. (line 14)
+* M-n: Repetition. (line 45)
+* M-n (isearch-mode): Incremental Search. (line 130)
+* M-n (minibuffer history): Minibuffer History. (line 30)
+* M-n (Shell mode): Shell Mode. (line 12)
+* M-p <1>: Nroff Mode. (line 14)
+* M-p: Repetition. (line 45)
+* M-p (isearch-mode): Incremental Search. (line 130)
+* M-p (minibuffer history): Minibuffer History. (line 30)
+* M-p (Shell mode): Shell Mode. (line 12)
+* M-q: Fill Commands. (line 21)
+* M-r: Moving Point. (line 15)
+* M-r (minibuffer history): Minibuffer History. (line 48)
+* M-s: Fill Commands. (line 44)
+* M-s (minibuffer history): Minibuffer History. (line 48)
+* M-SPC: Killing. (line 53)
+* M-t <1>: Words. (line 55)
+* M-t: Transpose. (line 30)
+* M-TAB <1>: Tabs in Picture. (line 6)
+* M-TAB: Lisp Completion. (line 9)
+* M-TAB (customization buffer): Changing an Option. (line 52)
+* M-TAB (isearch-mode): Incremental Search. (line 130)
+* M-u: Case. (line 24)
+* M-v <1>: Scrolling. (line 42)
+* M-v: Moving Point. (line 15)
+* M-v (Calendar mode): Scroll Calendar. (line 35)
+* M-w: Kill Ring. (line 30)
+* M-x: M-x. (line 18)
+* M-y: Earlier Kills. (line 6)
+* M-z: Killing. (line 129)
+* M-{: Paragraphs. (line 6)
+* M-{ (Calendar mode): Calendar Unit Motion.
+ (line 43)
+* M-|: Single Shell. (line 15)
+* M-}: Paragraphs. (line 6)
+* M-} (Calendar mode): Calendar Unit Motion.
+ (line 43)
+* M-~: Saving. (line 45)
+* META: Meta Key. (line 6)
+* meta key: Intro to Keystrokes. (line 16)
+* next: Scrolling. (line 42)
+* o (Calendar mode): Specified Dates. (line 23)
+* p (Calendar mode): To Other Calendar. (line 11)
+* p d (Calendar mode): General Calendar. (line 21)
+* pgdn: Scrolling. (line 42)
+* PGDN: Moving Point. (line 15)
+* pgup: Scrolling. (line 42)
+* PGUP: Moving Point. (line 15)
+* prior: Scrolling. (line 42)
+* q (Calendar mode): General Calendar. (line 41)
+* RET: Inserting Text. (line 19)
+* RET (isearch-mode): Incremental Search. (line 130)
+* RET (Shell mode): Shell Mode. (line 12)
+* RIGHT: Moving Point. (line 6)
+* s (Calendar mode): Diary Commands. (line 55)
+* S (Calendar mode): Sunrise/Sunset. (line 22)
+* S-TAB (customization buffer): Changing an Option. (line 90)
+* shift key: Intro to Keystrokes. (line 16)
+* SPC: Completion Commands. (line 34)
+* SPC (Calendar mode): General Calendar. (line 29)
+* SPC (query-replace): Query Replace. (line 27)
+* super key <1>: Super and Hyper Keys.
+ (line 6)
+* super key <2>: Representing Keystrokes.
+ (line 6)
+* super key: Intro to Keystrokes. (line 16)
+* t (Calendar mode): LaTeX Calendar. (line 10)
+* TAB <1>: Basic Indent. (line 12)
+* TAB <2>: Text Mode. (line 6)
+* TAB <3>: Indentation. (line 39)
+* TAB <4>: Major Modes. (line 6)
+* TAB <5>: Completion Example. (line 6)
+* TAB: String Key Sequences.
+ (line 15)
+* TAB (customization buffer): Changing an Option. (line 90)
+* TAB (Shell mode): Shell Mode. (line 12)
+* u (Calendar mode) <1>: Diary Commands. (line 47)
+* u (Calendar mode): Holidays. (line 40)
+* UP: Moving Point. (line 6)
+* x (Calendar mode): Holidays. (line 40)
\1f
-File: xemacs.info, Node: Library Keywords, Next: Help Mode, Prev: Apropos, Up: Help
-
-Keyword Search for Lisp Libraries
-=================================
-
- The `C-h p' command lets you search the standard Emacs Lisp
-libraries by topic keywords. Here is a partial list of keywords you can
-use:
-
- abbrev abbreviation handling, typing shortcuts, macros
- bib code related to the `bib' bibliography processor
- c C, C++, and Objective-C language support
- calendar calendar and time management support
- comm communications, networking, remote access to files
- data support for editing files of data
- docs support for Emacs documentation
- dumped files preloaded into Emacs
- emulations emulations of other editors
- extensions Emacs Lisp language extensions
- faces support for multiple fonts
- frames support for Emacs frames and window systems
- games games, jokes and amusements
- hardware support for interfacing with exotic hardware
- help support for on-line help systems
- hypermedia support for links between text or other media types
- i18n internationalization and alternate character-set support
- internal code for Emacs internals, build process, defaults
- languages specialized modes for editing programming languages
- lisp Lisp support, including Emacs Lisp
- local code local to your site
- maint maintenance aids for the Emacs development group
- mail modes for electronic-mail handling
- matching various sorts of searching and matching
- mouse mouse support
- mule multi-language extensions
- news support for netnews reading and posting
- oop support for object-oriented programming
- outlines support for hierarchical outlining
- processes process, subshell, compilation, and job control support
- terminals support for terminal types
- tex code related to the TeX formatter
- tools programming tools
- unix front-ends/assistants for, or emulators of, UNIX features
- vms support code for vms
- wp word processing
-
-\1f
-File: xemacs.info, Node: Help Mode, Next: Misc Help, Prev: Library Keywords, Up: Help
-
-Help Mode Commands
-==================
-
- Help buffers provide the commands of View mode (*note Misc File
-Ops::), plus a few special commands of their own.
-
-`<SPC>'
- Scroll forward.
+File: xemacs.info, Node: Command Index, Next: Variable Index, Prev: Key Index, Up: Top
-`<DEL>'
-`<BS>'
- Scroll backward.
+Command and Function Index
+**************************
- When a command name (*note Running Commands by Name: M-x.) or
-variable name (*note Variables::) appears in the documentation, it
-normally appears inside paired single-quotes.
+\0\b[index\0\b]
+* Menu:
-\1f
-File: xemacs.info, Node: Misc Help, Prev: Help Mode, Up: Help
-
-Other Help Commands
-===================
-
- `C-h i' (`info') runs the Info program, which is used for browsing
-through structured documentation files. The entire XEmacs manual is
-available within Info. Eventually all the documentation of the GNU
-system will be available. Type `h' after entering Info to run a
-tutorial on using Info.
-
- If you specify a numeric argument, `C-h i' prompts for the name of a
-documentation file. This way, you can browse a file which doesn't have
-an entry in the top-level Info menu. It is also handy when you need to
-get to the documentation quickly, and you know the exact name of the
-file.
-
- There are two special help commands for accessing XEmacs
-documentation through Info. `C-h C-f FUNCTION <RET>' enters Info and
-goes straight to the documentation of the XEmacs function FUNCTION.
-`C-h C-k KEY' enters Info and goes straight to the documentation of the
-key KEY. These two keys run the commands `Info-elisp-ref' and
-`Info-goto-emacs-key-command-node'.
-
- If something surprising happens, and you are not sure what commands
-you typed, use `C-h l' (`view-lossage'). `C-h l' prints the last 100
-command characters you typed in. If you see commands that you don't
-know, you can use `C-h c' to find out what they do.
-
- XEmacs has several major modes. Each mode redefines a few keys and
-makes a few other changes in how editing works. `C-h m'
-(`describe-mode') prints documentation on the current major mode, which
-normally describes all the commands that are changed in this mode.
-
- `C-h b' (`describe-bindings') and `C-h s' (`describe-syntax')
-present information about the current XEmacs mode that is not covered
-by `C-h m'. `C-h b' displays a list of all the key bindings currently
-in effect, with the local bindings of the current major mode first,
-followed by the global bindings (*note Key Bindings::). `C-h s'
-displays the contents of the syntax table with explanations of each
-character's syntax (*note Syntax::).
-
- You can get a similar list for a particular prefix key by typing
-`C-h' after the prefix key. (There are a few prefix keys for which
-this does not work--those that provide their own bindings for `C-h'.
-One of these is <ESC>, because `<ESC> C-h' is actually `C-M-h', which
-marks a defun.)
-
- The other `C-h' options display various files of useful information.
-`C-h C-w' (`describe-no-warranty') displays the full details on the
-complete absence of warranty for XEmacs. `C-h n' (`view-emacs-news')
-displays the file `xemacs/etc/NEWS', which contains documentation on
-XEmacs changes arranged chronologically. `C-h F' (`xemacs-local-faq')
-displays local version of the XEmacs
-frequentliy-answered-questions-list. `C-h t' (`help-with-tutorial')
-displays the learn-by-doing XEmacs tutorial. `C-h C-c'
-(`describe-copying') displays the file `xemacs/etc/COPYING', which
-tells you the conditions you must obey in distributing copies of
-XEmacs. `C-h C-d' (`describe-distribution') displays another file named
-`xemacs/etc/DISTRIB', which tells you how you can order a copy of the
-latest version of XEmacs.
+* abbrev-mode <1>: Minor Modes. (line 31)
+* abbrev-mode: Abbrevs. (line 12)
+* abbrev-prefix-mark: Expanding Abbrevs. (line 32)
+* abort-recursive-edit <1>: Quitting. (line 44)
+* abort-recursive-edit: Recursive Edit. (line 18)
+* add-change-log-entry: Change Log. (line 6)
+* add-global-abbrev: Defining Abbrevs. (line 25)
+* add-hook: Mode Hooks. (line 6)
+* add-menu: Menu Customization. (line 30)
+* add-menu-item: Menu Customization. (line 53)
+* add-mode-abbrev: Defining Abbrevs. (line 38)
+* add-name-to-file: Misc File Ops. (line 9)
+* american-calendar: Date Formats. (line 39)
+* append-next-kill: Appending Kills. (line 33)
+* append-to-buffer: Accumulating Text. (line 6)
+* append-to-file <1>: Misc File Ops. (line 13)
+* append-to-file: Accumulating Text. (line 6)
+* apropos: Apropos. (line 44)
+* apropos-documentation: Apropos. (line 49)
+* apropos-value: Apropos. (line 53)
+* ask-user-about-lock: Interlocking. (line 18)
+* auto-fill-mode <1>: Minor Modes. (line 22)
+* auto-fill-mode: Auto Fill. (line 17)
+* auto-save-mode: Auto Save Control. (line 6)
+* awk-mode: CC Mode. (line 6)
+* back-to-indentation: Indentation Commands.
+ (line 9)
+* backward-char: Moving Point. (line 15)
+* backward-delete-char-untabify: Program Modes. (line 50)
+* backward-kill-sentence <1>: Sentences. (line 37)
+* backward-kill-sentence <2>: Kill Errors. (line 19)
+* backward-kill-sentence: Killing. (line 100)
+* backward-kill-word <1>: Words. (line 50)
+* backward-kill-word <2>: Kill Errors. (line 19)
+* backward-kill-word: Killing. (line 100)
+* backward-list: Lists. (line 90)
+* backward-or-forward-delete-char: Inserting Text. (line 55)
+* backward-page: Pages. (line 28)
+* backward-paragraph: Paragraphs. (line 6)
+* backward-sentence: Sentences. (line 22)
+* backward-sexp: Lists. (line 67)
+* backward-text-line: Nroff Mode. (line 14)
+* backward-up-list: Lists. (line 96)
+* backward-word: Words. (line 32)
+* batch-byte-compile: Compiling Libraries. (line 52)
+* beginning-of-buffer: Moving Point. (line 15)
+* beginning-of-defun: Defuns. (line 23)
+* beginning-of-fortran-subprogram: Fortran Motion. (line 11)
+* beginning-of-line: Moving Point. (line 15)
+* bookmark-delete: Bookmarks. (line 74)
+* bookmark-insert: Bookmarks. (line 81)
+* bookmark-insert-location: Bookmarks. (line 77)
+* bookmark-jump: Bookmarks. (line 22)
+* bookmark-load: Bookmarks. (line 65)
+* bookmark-save: Bookmarks. (line 28)
+* bookmark-set: Bookmarks. (line 19)
+* bookmark-write: Bookmarks. (line 71)
+* buffer-menu: Several Buffers. (line 14)
+* byte-compile-and-load-file: Compiling Libraries. (line 34)
+* byte-compile-buffer: Compiling Libraries. (line 34)
+* byte-compile-file: Compiling Libraries. (line 34)
+* byte-recompile-directory: Compiling Libraries. (line 44)
+* c++-mode: CC Mode. (line 6)
+* c-indent-line: Basic Indent. (line 12)
+* c-mode: CC Mode. (line 6)
+* calendar: Calendar/Diary. (line 6)
+* calendar-backward-day: Calendar Unit Motion.
+ (line 34)
+* calendar-backward-month: Calendar Unit Motion.
+ (line 43)
+* calendar-backward-week: Calendar Unit Motion.
+ (line 34)
+* calendar-beginning-of-month: Move to Beginning or End.
+ (line 15)
+* calendar-beginning-of-week: Move to Beginning or End.
+ (line 11)
+* calendar-beginning-of-year: Move to Beginning or End.
+ (line 21)
+* calendar-count-days-region: Mark and Region. (line 31)
+* calendar-cursor-holidays: Holidays. (line 33)
+* calendar-end-of-month: Move to Beginning or End.
+ (line 18)
+* calendar-end-of-week: Move to Beginning or End.
+ (line 12)
+* calendar-end-of-year: Move to Beginning or End.
+ (line 24)
+* calendar-exchange-point-and-mark: Mark and Region. (line 24)
+* calendar-forward-day: Calendar Unit Motion.
+ (line 34)
+* calendar-forward-month: Calendar Unit Motion.
+ (line 43)
+* calendar-forward-week: Calendar Unit Motion.
+ (line 34)
+* calendar-forward-year: Calendar Unit Motion.
+ (line 43)
+* calendar-goto-astro-day-number: From Other Calendar. (line 10)
+* calendar-goto-chinese-date: From Other Calendar. (line 10)
+* calendar-goto-coptic-date: From Other Calendar. (line 10)
+* calendar-goto-date: Specified Dates. (line 18)
+* calendar-goto-ethiopic-date: From Other Calendar. (line 10)
+* calendar-goto-french-date: From Other Calendar. (line 10)
+* calendar-goto-hebrew-date: From Other Calendar. (line 10)
+* calendar-goto-islamic-date: From Other Calendar. (line 10)
+* calendar-goto-iso-date: From Other Calendar. (line 10)
+* calendar-goto-julian-date: From Other Calendar. (line 10)
+* calendar-goto-mayan-long-count-date: Mayan Calendar. (line 42)
+* calendar-goto-persian-date: From Other Calendar. (line 10)
+* calendar-goto-today: Specified Dates. (line 26)
+* calendar-mark-today: Calendar Customizing.
+ (line 61)
+* calendar-next-calendar-round-date: Mayan Calendar. (line 64)
+* calendar-next-haab-date: Mayan Calendar. (line 56)
+* calendar-next-tzolkin-date: Mayan Calendar. (line 48)
+* calendar-other-month: Specified Dates. (line 23)
+* calendar-phases-of-moon: Lunar Phases. (line 19)
+* calendar-previous-haab-date: Mayan Calendar. (line 56)
+* calendar-previous-tzolkin-date: Mayan Calendar. (line 48)
+* calendar-print-astro-day-number: To Other Calendar. (line 19)
+* calendar-print-chinese-date: To Other Calendar. (line 35)
+* calendar-print-coptic-date: To Other Calendar. (line 39)
+* calendar-print-day-of-year: General Calendar. (line 21)
+* calendar-print-ethiopic-date: To Other Calendar. (line 43)
+* calendar-print-french-date: To Other Calendar. (line 31)
+* calendar-print-hebrew-date: To Other Calendar. (line 23)
+* calendar-print-islamic-date: To Other Calendar. (line 27)
+* calendar-print-iso-date: To Other Calendar. (line 11)
+* calendar-print-julian-date: To Other Calendar. (line 15)
+* calendar-print-mayan-date: To Other Calendar. (line 51)
+* calendar-print-persian-date: To Other Calendar. (line 47)
+* calendar-set-mark: Mark and Region. (line 24)
+* calendar-star-date: Calendar Customizing.
+ (line 56)
+* calendar-sunrise-sunset: Sunrise/Sunset. (line 22)
+* calendar-unmark <1>: Diary Commands. (line 47)
+* calendar-unmark: Holidays. (line 40)
+* call-last-kbd-macro: Basic Kbd Macro. (line 6)
+* cancel-debug-on-entry: Lisp Debug. (line 18)
+* capitalize-word <1>: Case. (line 24)
+* capitalize-word: Fixing Case. (line 16)
+* center-line: Fill Commands. (line 44)
+* choose-completion: Completion Commands. (line 60)
+* clear-rectangle: Rectangles. (line 68)
+* comint-delchar-or-maybe-eof: Shell Mode. (line 12)
+* comint-dynamic-complete: Shell Mode. (line 12)
+* comint-next-input: Shell Mode. (line 12)
+* comint-previous-input: Shell Mode. (line 12)
+* command-apropos: Apropos. (line 6)
+* compare-windows <1>: Other Window. (line 45)
+* compare-windows: Comparing Files. (line 22)
+* compile: Compilation. (line 29)
+* compile-defun: Defuns. (line 34)
+* convert-mocklisp-buffer: Mocklisp. (line 6)
+* conx: CONX. (line 28)
+* conx-buffer: CONX. (line 28)
+* conx-init: CONX. (line 28)
+* conx-load: CONX. (line 28)
+* conx-region: CONX. (line 28)
+* conx-save: CONX. (line 28)
+* copy-file: Misc File Ops. (line 16)
+* copy-last-shell-input: Shell Mode. (line 12)
+* copy-rectangle-to-register: RegRect. (line 11)
+* copy-region-as-kill: Kill Ring. (line 30)
+* copy-to-buffer: Accumulating Text. (line 6)
+* copy-to-register: RegText. (line 21)
+* count-lines-page: Pages. (line 46)
+* count-lines-region: Position Info. (line 31)
+* count-matches: Other Repeating Search.
+ (line 9)
+* count-text-lines: Nroff Mode. (line 14)
+* customize: Easy Customization. (line 6)
+* customize-apropos: Specific Customization.
+ (line 47)
+* customize-browse: Customization Groups.
+ (line 51)
+* customize-customized: Specific Customization.
+ (line 54)
+* customize-face: Specific Customization.
+ (line 38)
+* customize-group: Specific Customization.
+ (line 41)
+* customize-option: Specific Customization.
+ (line 31)
+* customize-saved: Specific Customization.
+ (line 54)
+* dabbrev-expand: Dynamic Abbrevs. (line 12)
+* debug: Lisp Debug. (line 18)
+* debug-on-entry: Lisp Debug. (line 18)
+* default-value: Locals. (line 68)
+* define-abbrevs: Saving Abbrevs. (line 42)
+* define-key <1>: Programmatic Rebinding.
+ (line 9)
+* define-key: Interactive Rebinding.
+ (line 44)
+* delete-backward-char <1>: Kill Errors. (line 15)
+* delete-backward-char: Killing. (line 6)
+* delete-blank-lines <1>: Killing. (line 53)
+* delete-blank-lines: Blank Lines. (line 16)
+* delete-char <1>: Basic Picture. (line 41)
+* delete-char: Killing. (line 6)
+* delete-file: Misc File Ops. (line 21)
+* delete-horizontal-space <1>: Indentation Commands.
+ (line 24)
+* delete-horizontal-space: Killing. (line 53)
+* delete-indentation <1>: Indentation Commands.
+ (line 24)
+* delete-indentation: Killing. (line 53)
+* delete-matching-lines: Other Repeating Search.
+ (line 9)
+* delete-menu-item: Menu Customization. (line 90)
+* delete-non-matching-lines: Other Repeating Search.
+ (line 9)
+* delete-other-windows: Change Window. (line 31)
+* delete-rectangle: Rectangles. (line 42)
+* delete-window: Change Window. (line 23)
+* describe-bindings: Misc Help. (line 37)
+* describe-calendar-mode: General Calendar. (line 26)
+* describe-coding-system: Coding Systems. (line 39)
+* describe-copying: Misc Help. (line 51)
+* describe-distribution: Misc Help. (line 51)
+* describe-function <1>: Documentation. (line 6)
+* describe-function: Name Help. (line 6)
+* describe-input-method: Select Input Method. (line 14)
+* describe-key: Key Help. (line 13)
+* describe-key-briefly: Key Help. (line 6)
+* describe-language-environment: Language Environments.
+ (line 36)
+* describe-mode: Misc Help. (line 32)
+* describe-no-warranty: Misc Help. (line 51)
+* describe-syntax: Syntax Change. (line 48)
+* describe-variable <1>: Examining. (line 13)
+* describe-variable <2>: Documentation. (line 6)
+* describe-variable: Name Help. (line 49)
+* diary: Diary Commands. (line 67)
+* diary-anniversary <1>: Sexp Diary Entries. (line 13)
+* diary-anniversary: Special Diary Entries.
+ (line 35)
+* diary-astro-day-number: Sexp Diary Entries. (line 69)
+* diary-block: Special Diary Entries.
+ (line 50)
+* diary-cyclic <1>: Sexp Diary Entries. (line 32)
+* diary-cyclic: Special Diary Entries.
+ (line 66)
+* diary-day-of-year: Sexp Diary Entries. (line 69)
+* diary-float: Special Diary Entries.
+ (line 87)
+* diary-french-date: Sexp Diary Entries. (line 69)
+* diary-hebrew-date: Sexp Diary Entries. (line 69)
+* diary-islamic-date: Sexp Diary Entries. (line 69)
+* diary-iso-date: Sexp Diary Entries. (line 69)
+* diary-julian-date: Sexp Diary Entries. (line 69)
+* diary-mail-entries: Diary Commands. (line 77)
+* diary-mayan-date: Sexp Diary Entries. (line 69)
+* diary-omer: Sexp Diary Entries. (line 119)
+* diary-parasha: Sexp Diary Entries. (line 119)
+* diary-phases-of-moon: Sexp Diary Entries. (line 69)
+* diary-rosh-hodesh: Sexp Diary Entries. (line 119)
+* diary-sabbath-candles: Sexp Diary Entries. (line 119)
+* diary-sunrise-sunset: Sexp Diary Entries. (line 69)
+* diary-yahrzeit: Sexp Diary Entries. (line 119)
+* diff: Comparing Files. (line 6)
+* diff-backup: Comparing Files. (line 18)
+* digit-argument: Arguments. (line 16)
+* dired: Dired Enter. (line 6)
+* dired-other-window <1>: Pop Up Window. (line 11)
+* dired-other-window: Dired Enter. (line 16)
+* disable-command: Disabling. (line 25)
+* disable-menu-item: Menu Customization. (line 98)
+* disassemble: Compiling Libraries. (line 64)
+* display-time: Mode Line. (line 70)
+* dissociated-press: Dissociated Press. (line 6)
+* do-auto-save: Auto Save Control. (line 15)
+* doctor: Total Frustration. (line 13)
+* down-list: Lists. (line 96)
+* downcase-region: Case. (line 46)
+* downcase-word <1>: Case. (line 24)
+* downcase-word: Fixing Case. (line 16)
+* edit-abbrevs: Editing Abbrevs. (line 34)
+* edit-abbrevs-redefine: Editing Abbrevs. (line 34)
+* edit-options: Edit Options. (line 30)
+* edit-picture: Picture. (line 6)
+* edit-tab-stops <1>: Text Mode. (line 6)
+* edit-tab-stops: Tab Stops. (line 11)
+* edit-tab-stops-note-changes: Tab Stops. (line 11)
+* edt-emulation-off: Emulation. (line 29)
+* edt-emulation-on: Emulation. (line 29)
+* electric-nroff-mode: Nroff Mode. (line 25)
+* emacs-lisp-mode: Lisp Eval. (line 6)
+* emacs-version: Bugs. (line 63)
+* enable-command: Disabling. (line 25)
+* enable-menu-item: Menu Customization. (line 98)
+* end-kbd-macro: Basic Kbd Macro. (line 6)
+* end-of-buffer: Moving Point. (line 15)
+* end-of-defun: Defuns. (line 23)
+* end-of-fortran-subprogram: Fortran Motion. (line 11)
+* end-of-line: Moving Point. (line 15)
+* enlarge-window: Change Window. (line 36)
+* enlarge-window-horizontally: Change Window. (line 36)
+* european-calendar: Date Formats. (line 39)
+* eval-current-buffer: Lisp Eval. (line 60)
+* eval-defun: Lisp Eval. (line 44)
+* eval-expression: Lisp Eval. (line 38)
+* eval-last-sexp: Lisp Eval. (line 50)
+* eval-region: Lisp Eval. (line 60)
+* exchange-point-and-mark: Setting Mark. (line 42)
+* execute-extended-command: M-x. (line 152)
+* exit-calendar: General Calendar. (line 41)
+* exit-recursive-edit: Recursive Edit. (line 13)
+* expand-abbrev: Expanding Abbrevs. (line 23)
+* expand-region-abbrevs: Expanding Abbrevs. (line 54)
+* fancy-diary-display: Fancy Diary Display. (line 11)
+* fill-individual-paragraphs: Fill Prefix. (line 45)
+* fill-paragraph: Fill Commands. (line 21)
+* fill-region: Fill Commands. (line 27)
+* fill-region-as-paragraph: Fill Commands. (line 30)
+* find-alternate-file: Visiting. (line 96)
+* find-file: Visiting. (line 46)
+* find-file-other-frame <1>: Visiting. (line 46)
+* find-file-other-frame: XEmacs under X. (line 22)
+* find-file-other-window <1>: Pop Up Window. (line 11)
+* find-file-other-window: Visiting. (line 108)
+* find-tag: Find Tag. (line 19)
+* find-tag-other-window <1>: Find Tag. (line 67)
+* find-tag-other-window: Pop Up Window. (line 11)
+* find-this-file: Visiting. (line 67)
+* find-this-file-other-window: Visiting. (line 119)
+* finder-by-keyword: Library Keywords. (line 6)
+* fortran-column-ruler: Fortran Columns. (line 15)
+* fortran-comment-region: Fortran Comments. (line 71)
+* fortran-indent-line: ForIndent Commands. (line 16)
+* fortran-indent-subprogram: ForIndent Commands. (line 21)
+* fortran-mode: Fortran. (line 16)
+* fortran-next-statement: Fortran Motion. (line 11)
+* fortran-previous-statement: Fortran Motion. (line 11)
+* fortran-split-line: ForIndent Commands. (line 25)
+* fortran-window-create: Fortran Columns. (line 30)
+* forward-char: Moving Point. (line 15)
+* forward-list: Lists. (line 90)
+* forward-page: Pages. (line 28)
+* forward-paragraph: Paragraphs. (line 6)
+* forward-sentence: Sentences. (line 22)
+* forward-sexp: Lists. (line 67)
+* forward-text-line: Nroff Mode. (line 14)
+* forward-word: Words. (line 32)
+* frame-configuration-to-register: RegConfig. (line 6)
+* global-set-key <1>: Programmatic Rebinding.
+ (line 9)
+* global-set-key: Interactive Rebinding.
+ (line 6)
+* goto-char: Moving Point. (line 15)
+* goto-line: Moving Point. (line 15)
+* hanoi: Amusements. (line 6)
+* help-command: Help. (line 6)
+* help-for-help: Help. (line 13)
+* help-with-tutorial <1>: Misc Help. (line 51)
+* help-with-tutorial: Basic. (line 6)
+* hide-body: Outline Visibility. (line 66)
+* hide-entry: Outline Visibility. (line 43)
+* hide-leaves: Outline Visibility. (line 56)
+* hide-subtree: Outline Visibility. (line 48)
+* holidays: Holidays. (line 53)
+* idl-mode: CC Mode. (line 6)
+* include-other-diary-files: Included Diary Files.
+ (line 17)
+* increment-register: RegNumbers. (line 14)
+* indent-c-exp: Multi-line Indent. (line 19)
+* indent-for-comment: Comments. (line 6)
+* indent-new-comment-line: Comments. (line 72)
+* indent-region <1>: Multi-line Indent. (line 35)
+* indent-region: Indentation Commands.
+ (line 33)
+* indent-relative: Indentation Commands.
+ (line 43)
+* indent-rigidly: Indentation Commands.
+ (line 33)
+* indent-sexp: Multi-line Indent. (line 19)
+* indented-text-mode: Text Mode. (line 15)
+* info: Misc Help. (line 6)
+* Info-elisp-ref: Misc Help. (line 18)
+* Info-goto-emacs-command-node: Misc Help. (line 18)
+* Info-goto-emacs-key-command-node: Misc Help. (line 18)
+* insert-abbrevs: Saving Abbrevs. (line 42)
+* insert-anniversary-diary-entry: Special Diary Entries.
+ (line 29)
+* insert-block-diary-entry: Special Diary Entries.
+ (line 56)
+* insert-cyclic-diary-entry: Special Diary Entries.
+ (line 61)
+* insert-diary-entry: Adding to Diary. (line 24)
+* insert-file: Misc File Ops. (line 25)
+* insert-hebrew-diary-entry: Hebrew/Islamic Entries.
+ (line 74)
+* insert-islamic-diary-entry: Hebrew/Islamic Entries.
+ (line 74)
+* insert-kbd-macro: Save Kbd Macro. (line 15)
+* insert-monthly-diary-entry: Adding to Diary. (line 29)
+* insert-monthly-hebrew-diary-entry: Hebrew/Islamic Entries.
+ (line 74)
+* insert-monthly-islamic-diary-entry: Hebrew/Islamic Entries.
+ (line 74)
+* insert-parentheses: Balanced Editing. (line 13)
+* insert-register: RegText. (line 21)
+* insert-weekly-diary-entry: Adding to Diary. (line 29)
+* insert-yearly-diary-entry: Adding to Diary. (line 29)
+* insert-yearly-hebrew-diary-entry: Hebrew/Islamic Entries.
+ (line 74)
+* insert-yearly-islamic-diary-entry: Hebrew/Islamic Entries.
+ (line 74)
+* interactive: M-x. (line 49)
+* interrupt-shell-subjob: Shell Mode. (line 12)
+* inverse-add-global-abbrev: Defining Abbrevs. (line 44)
+* inverse-add-mode-abbrev: Defining Abbrevs. (line 44)
+* invert-face: Faces. (line 70)
+* isearch-abort: Incremental Search. (line 130)
+* isearch-backward: Incremental Search. (line 19)
+* isearch-backward-regexp: Regexp Search. (line 28)
+* isearch-complete: Incremental Search. (line 130)
+* isearch-delete-char: Incremental Search. (line 130)
+* isearch-exit: Incremental Search. (line 130)
+* isearch-forward: Incremental Search. (line 19)
+* isearch-forward-regexp: Regexp Search. (line 28)
+* isearch-quote-char: Incremental Search. (line 130)
+* isearch-repeat-backward: Incremental Search. (line 130)
+* isearch-repeat-forward: Incremental Search. (line 130)
+* isearch-ring-advance: Incremental Search. (line 130)
+* isearch-ring-retreat: Incremental Search. (line 130)
+* isearch-yank-line: Incremental Search. (line 130)
+* isearch-yank-word: Incremental Search. (line 130)
+* java-mode: CC Mode. (line 6)
+* jump-to-register <1>: Split Window. (line 46)
+* jump-to-register: RegPos. (line 20)
+* just-one-space: Killing. (line 53)
+* kbd-macro-query: Kbd Macro Query. (line 6)
+* kill-all-abbrevs: Defining Abbrevs. (line 58)
+* kill-buffer: Kill Buffer. (line 16)
+* kill-comment: Comments. (line 58)
+* kill-compilation: Compilation. (line 51)
+* kill-line: Killing. (line 73)
+* kill-local-variable: Locals. (line 50)
+* kill-output-from-shell: Shell Mode. (line 12)
+* kill-rectangle: Rectangles. (line 42)
+* kill-region: Killing. (line 100)
+* kill-sentence <1>: Sentences. (line 37)
+* kill-sentence: Killing. (line 100)
+* kill-sexp <1>: Lists. (line 87)
+* kill-sexp: Killing. (line 100)
+* kill-some-buffers: Kill Buffer. (line 16)
+* kill-word <1>: Words. (line 41)
+* kill-word: Killing. (line 100)
+* latex-mode: TeX Mode. (line 6)
+* LaTeX-mode: TeX Mode. (line 6)
+* lisp-complete-symbol: Lisp Completion. (line 9)
+* lisp-indent-line: Basic Indent. (line 12)
+* lisp-interaction-mode: Lisp Interaction. (line 22)
+* lisp-mode: External Lisp. (line 22)
+* lisp-send-defun: External Lisp. (line 27)
+* list-abbrevs: Editing Abbrevs. (line 12)
+* list-bookmarks: Bookmarks. (line 25)
+* list-buffers: List Buffers. (line 9)
+* list-calendar-holidays: Holidays. (line 48)
+* list-coding-systems: Coding Systems. (line 46)
+* list-command-history: Repetition. (line 12)
+* list-directory: ListDir. (line 17)
+* list-hebrew-diary-entries: Hebrew/Islamic Entries.
+ (line 13)
+* list-holidays: Holidays. (line 63)
+* list-input-methods: Select Input Method. (line 47)
+* list-islamic-diary-entries: Hebrew/Islamic Entries.
+ (line 18)
+* list-matching-lines: Other Repeating Search.
+ (line 9)
+* list-options: Edit Options. (line 13)
+* list-tags: List Tags. (line 12)
+* list-yahrzeit-dates: From Other Calendar. (line 57)
+* load: Loading. (line 21)
+* load-default-sounds: Audible Bell. (line 6)
+* load-file: Loading. (line 15)
+* load-library <1>: Loading. (line 21)
+* load-library: Startup Paths. (line 124)
+* load-sound-file: Audible Bell. (line 59)
+* local-set-key: Interactive Rebinding.
+ (line 6)
+* local-unset-key: Interactive Rebinding.
+ (line 6)
+* locate-library: Loading. (line 57)
+* lpr-buffer: Hardcopy. (line 24)
+* lpr-region: Hardcopy. (line 24)
+* mail: Sending Mail. (line 22)
+* mail-cc: Mail Mode. (line 54)
+* mail-fill-yanked-message: Mail Mode. (line 78)
+* mail-interactive-insert-alias: Mail Headers. (line 99)
+* mail-other-window <1>: Sending Mail. (line 22)
+* mail-other-window: Pop Up Window. (line 11)
+* mail-send: Mail Mode. (line 45)
+* mail-send-and-exit: Mail Mode. (line 45)
+* mail-signature: Mail Mode. (line 63)
+* mail-subject: Mail Mode. (line 54)
+* mail-to: Mail Mode. (line 54)
+* mail-yank-original: Mail Mode. (line 67)
+* make-directory: File Names. (line 51)
+* make-face-bold: Faces. (line 77)
+* make-face-bold-italic: Faces. (line 77)
+* make-face-italic: Faces. (line 77)
+* make-face-larger: Faces. (line 70)
+* make-face-smaller: Faces. (line 70)
+* make-face-unbold: Faces. (line 77)
+* make-face-unitalic: Faces. (line 77)
+* make-frame: XEmacs under X. (line 16)
+* make-local-variable: Locals. (line 26)
+* make-obsolete: Compiling Libraries. (line 28)
+* make-symbolic-link: Misc File Ops. (line 29)
+* make-variable-buffer-local: Locals. (line 31)
+* manual-entry: Documentation. (line 17)
+* mark-beginning-of-buffer: Setting Mark. (line 50)
+* mark-calendar-holidays: Holidays. (line 40)
+* mark-defun <1>: Defuns. (line 23)
+* mark-defun: Marking Objects. (line 32)
+* mark-diary-entries: Diary Commands. (line 47)
+* mark-end-of-buffer: Setting Mark. (line 50)
+* mark-fortran-subprogram: Fortran Motion. (line 11)
+* mark-hebrew-diary-entries: Hebrew/Islamic Entries.
+ (line 13)
+* mark-included-diary-files: Included Diary Files.
+ (line 17)
+* mark-islamic-diary-entries: Hebrew/Islamic Entries.
+ (line 18)
+* mark-page <1>: Pages. (line 34)
+* mark-page: Marking Objects. (line 32)
+* mark-paragraph <1>: Paragraphs. (line 31)
+* mark-paragraph: Marking Objects. (line 32)
+* mark-sexp <1>: Lists. (line 114)
+* mark-sexp: Marking Objects. (line 28)
+* mark-whole-buffer: Marking Objects. (line 32)
+* mark-word <1>: Words. (line 61)
+* mark-word: Marking Objects. (line 28)
+* minibuffer-complete: Completion Example. (line 6)
+* minibuffer-complete-word: Completion Commands. (line 34)
+* modify-syntax-entry: Syntax Change. (line 12)
+* mouse-choose-completion: Completion Commands. (line 45)
+* mouse-del-char: Additional Mouse Operations.
+ (line 14)
+* mouse-delete-window: Additional Mouse Operations.
+ (line 14)
+* mouse-keep-one-window: Additional Mouse Operations.
+ (line 14)
+* mouse-kill-line: Additional Mouse Operations.
+ (line 14)
+* mouse-line-length: Additional Mouse Operations.
+ (line 14)
+* mouse-scroll: Additional Mouse Operations.
+ (line 14)
+* mouse-select: Additional Mouse Operations.
+ (line 14)
+* mouse-select-and-split: Additional Mouse Operations.
+ (line 14)
+* mouse-set-mark: Additional Mouse Operations.
+ (line 14)
+* mouse-set-point: Additional Mouse Operations.
+ (line 14)
+* mouse-track: Additional Mouse Operations.
+ (line 14)
+* mouse-track-adjust: Additional Mouse Operations.
+ (line 14)
+* mouse-track-and-copy-to-cutbuffer: Additional Mouse Operations.
+ (line 14)
+* mouse-track-delete-and-insert: Additional Mouse Operations.
+ (line 14)
+* move-over-close-and-reindent: Balanced Editing. (line 13)
+* move-to-window-line: Moving Point. (line 15)
+* name-last-kbd-macro: Save Kbd Macro. (line 6)
+* narrow-to-region: Narrowing. (line 28)
+* negative-argument: Arguments. (line 16)
+* newline: Inserting Text. (line 55)
+* newline-and-indent: Basic Indent. (line 26)
+* next-complex-command: Repetition. (line 45)
+* next-error: Compilation. (line 58)
+* next-history-element: Minibuffer History. (line 30)
+* next-line: Moving Point. (line 15)
+* next-list-mode-item: Completion Commands. (line 66)
+* next-matching-history-element: Minibuffer History. (line 48)
+* not-modified: Saving. (line 45)
+* nroff-mode: Nroff Mode. (line 6)
+* number-to-register: RegNumbers. (line 11)
+* objc-mode: CC Mode. (line 6)
+* occur: Other Repeating Search.
+ (line 9)
+* open-dribble-file: Bugs. (line 144)
+* open-line: Blank Lines. (line 16)
+* open-rectangle: Rectangles. (line 68)
+* open-termscript: Bugs. (line 153)
+* other-window: Other Window. (line 20)
+* other-window-any-frame: Other Window. (line 34)
+* outline-backward-same-level: Outline Motion. (line 36)
+* outline-forward-same-level: Outline Motion. (line 36)
+* outline-next-visible-heading: Outline Motion. (line 29)
+* outline-previous-visible-heading: Outline Motion. (line 29)
+* outline-up-heading: Outline Motion. (line 36)
+* overwrite-mode: Minor Modes. (line 26)
+* phases-of-moon: Lunar Phases. (line 23)
+* picture-backward-clear-column: Basic Picture. (line 27)
+* picture-backward-column: Basic Picture. (line 6)
+* picture-clear-column: Basic Picture. (line 27)
+* picture-clear-line: Basic Picture. (line 27)
+* picture-clear-rectangle: Rectangles in Picture.
+ (line 27)
+* picture-clear-rectangle-to-register: Rectangles in Picture.
+ (line 27)
+* picture-forward-column: Basic Picture. (line 6)
+* picture-motion: Insert in Picture. (line 40)
+* picture-motion-reverse: Insert in Picture. (line 40)
+* picture-move-down: Basic Picture. (line 6)
+* picture-move-up: Basic Picture. (line 6)
+* picture-movement-down: Insert in Picture. (line 6)
+* picture-movement-left: Insert in Picture. (line 6)
+* picture-movement-ne: Insert in Picture. (line 6)
+* picture-movement-nw: Insert in Picture. (line 6)
+* picture-movement-right: Insert in Picture. (line 6)
+* picture-movement-se: Insert in Picture. (line 6)
+* picture-movement-sw: Insert in Picture. (line 6)
+* picture-movement-up: Insert in Picture. (line 6)
+* picture-newline: Basic Picture. (line 20)
+* picture-open-line: Basic Picture. (line 34)
+* picture-set-tab-stops: Tabs in Picture. (line 23)
+* picture-tab: Tabs in Picture. (line 18)
+* picture-tab-search: Tabs in Picture. (line 6)
+* picture-yank-rectangle: Rectangles in Picture.
+ (line 36)
+* picture-yank-rectangle-from-register: Rectangles in Picture.
+ (line 36)
+* pike-mode: CC Mode. (line 6)
+* plain-TeX-mode: TeX Mode. (line 6)
+* plain-tex-mode: TeX Mode. (line 6)
+* play-sound: Audible Bell. (line 6)
+* point-to-register: RegPos. (line 16)
+* prefer-coding-system: Recognize Coding. (line 28)
+* prepend-to-buffer: Accumulating Text. (line 6)
+* previous-complex-command: Repetition. (line 45)
+* previous-history-element: Minibuffer History. (line 30)
+* previous-line: Moving Point. (line 15)
+* previous-list-mode-item: Completion Commands. (line 73)
+* previous-matching-history-element: Minibuffer History. (line 48)
+* print-buffer: Hardcopy. (line 24)
+* print-diary-entries <1>: Diary Customizing. (line 26)
+* print-diary-entries: Diary Commands. (line 61)
+* print-region: Hardcopy. (line 24)
+* quail-set-keyboard-layout: Select Input Method. (line 41)
+* query-replace: Query Replace. (line 13)
+* query-replace-regexp: Query Replace. (line 20)
+* quietly-read-abbrev-file: Saving Abbrevs. (line 30)
+* quit-shell-subjob: Shell Mode. (line 12)
+* quoted-insert: Inserting Text. (line 33)
+* re-search-backward: Regexp Search. (line 42)
+* re-search-forward: Regexp Search. (line 42)
+* read-abbrev-file: Saving Abbrevs. (line 30)
+* read-key-sequence: Representing Keystrokes.
+ (line 6)
+* recenter <1>: Scrolling. (line 37)
+* recenter: Moving Point. (line 15)
+* recover-file: Recover. (line 6)
+* redraw-calendar: General Calendar. (line 33)
+* relabel-menu-item: Menu Customization. (line 103)
+* remove-directory: File Names. (line 51)
+* remove-hook: Mode Hooks. (line 6)
+* rename-buffer: Misc Buffer. (line 25)
+* rename-file: Misc File Ops. (line 37)
+* repeat-complex-command: Repetition. (line 27)
+* replace-regexp: Unconditional Replace.
+ (line 6)
+* replace-string: Unconditional Replace.
+ (line 6)
+* revert-buffer: Reverting. (line 6)
+* run-lisp: External Lisp. (line 12)
+* save-buffer: Saving. (line 26)
+* save-buffers-kill-emacs: Exiting. (line 64)
+* save-some-buffers: Saving. (line 39)
+* scroll-calendar-left: Scroll Calendar. (line 28)
+* scroll-calendar-left-three-months: Scroll Calendar. (line 35)
+* scroll-calendar-right: Scroll Calendar. (line 28)
+* scroll-calendar-right-three-months: Scroll Calendar. (line 35)
+* scroll-down: Scrolling. (line 42)
+* scroll-left: Horizontal Scrolling.
+ (line 12)
+* scroll-other-window <1>: General Calendar. (line 29)
+* scroll-other-window: Other Window. (line 40)
+* scroll-right: Horizontal Scrolling.
+ (line 12)
+* scroll-up: Scrolling. (line 42)
+* search-backward: Non-Incremental Search.
+ (line 25)
+* search-forward: Non-Incremental Search.
+ (line 25)
+* select-input-method: Select Input Method. (line 20)
+* self-insert: Inserting Text. (line 55)
+* send-shell-input: Shell Mode. (line 12)
+* set-buffer-file-coding-system: Specify Coding. (line 27)
+* set-buffer-process-coding-system: Specify Coding. (line 91)
+* set-comment-column: Comments. (line 84)
+* set-default-file-modes: Interlocking. (line 77)
+* set-face-background: Faces. (line 98)
+* set-face-background-pixmap: Faces. (line 104)
+* set-face-font: Faces. (line 120)
+* set-face-foreground: Faces. (line 126)
+* set-face-underline-p: Faces. (line 132)
+* set-fill-column: Fill Commands. (line 53)
+* set-fill-prefix: Fill Prefix. (line 22)
+* set-gnu-bindings: Emulation. (line 38)
+* set-goal-column: Moving Point. (line 95)
+* set-gosmacs-bindings: Emulation. (line 38)
+* set-keyboard-coding-system: Specify Coding. (line 73)
+* set-language-environment: Language Environments.
+ (line 19)
+* set-mark-command: Setting Mark. (line 32)
+* set-selective-display: Selective Display. (line 6)
+* set-terminal-coding-system: Specify Coding. (line 62)
+* set-variable: Examining. (line 8)
+* set-visited-file-name: Saving. (line 62)
+* setq-default: Locals. (line 56)
+* shell: Interactive Shell. (line 6)
+* shell-command: Single Shell. (line 6)
+* shell-command-on-region: Single Shell. (line 15)
+* shell-send-eof: Shell Mode. (line 12)
+* show-all: Outline Visibility. (line 66)
+* show-all-diary-entries: Diary Commands. (line 55)
+* show-branches: Outline Visibility. (line 56)
+* show-children: Outline Visibility. (line 62)
+* show-entry: Outline Visibility. (line 43)
+* show-output-from-shell: Shell Mode. (line 12)
+* show-subtree: Outline Visibility. (line 48)
+* simple-diary-display: Fancy Diary Display. (line 6)
+* sort-columns: Sorting. (line 87)
+* sort-diary-entries: Fancy Diary Display. (line 35)
+* sort-fields: Sorting. (line 23)
+* sort-lines: Sorting. (line 23)
+* sort-numeric-fields: Sorting. (line 23)
+* sort-pages: Sorting. (line 23)
+* sort-paragraphs: Sorting. (line 23)
+* spell-buffer: Spelling. (line 30)
+* spell-region: Spelling. (line 34)
+* spell-string: Spelling. (line 37)
+* spell-word: Spelling. (line 18)
+* split-line: Indentation Commands.
+ (line 17)
+* split-window-horizontally: Split Window. (line 28)
+* split-window-vertically: Split Window. (line 21)
+* start-kbd-macro: Basic Kbd Macro. (line 6)
+* stop-shell-subjob: Shell Mode. (line 12)
+* substitute-key-definition: Interactive Rebinding.
+ (line 44)
+* sunrise-sunset: Sunrise/Sunset. (line 22)
+* suspend-emacs: Exiting. (line 39)
+* switch-to-buffer: Select Buffer. (line 16)
+* switch-to-buffer-other-frame <1>: Select Buffer. (line 16)
+* switch-to-buffer-other-frame: XEmacs under X. (line 27)
+* switch-to-buffer-other-window <1>: Pop Up Window. (line 11)
+* switch-to-buffer-other-window: Select Buffer. (line 16)
+* switch-to-completions: Completion Commands. (line 52)
+* switch-to-other-buffer: Select Buffer. (line 35)
+* tab-to-tab-stop <1>: Text Mode. (line 6)
+* tab-to-tab-stop: Tab Stops. (line 6)
+* tabify: Just Spaces. (line 12)
+* tags-apropos: List Tags. (line 21)
+* tags-loop-continue: Tags Search. (line 28)
+* tags-query-replace: Tags Search. (line 33)
+* tags-search: Tags Search. (line 22)
+* term: Terminal emulator. (line 6)
+* term-line-mode: Term Mode. (line 17)
+* term-pager-toggle: Paging in Term. (line 9)
+* tex-buffer: TeX Print. (line 32)
+* tex-close-latex-block: TeX Editing. (line 72)
+* tex-insert-braces: TeX Editing. (line 49)
+* tex-insert-quote: TeX Editing. (line 31)
+* tex-kill-job: TeX Print. (line 38)
+* tex-mode: TeX Mode. (line 6)
+* TeX-mode: TeX Mode. (line 6)
+* tex-print: TeX Print. (line 32)
+* tex-recenter-output-buffer: TeX Print. (line 38)
+* tex-region: TeX Print. (line 48)
+* tex-show-print-queue: TeX Print. (line 32)
+* tex-terminate-paragraph: TeX Editing. (line 55)
+* text-mode: Text Mode. (line 6)
+* toggle-input-method: Select Input Method. (line 26)
+* toggle-read-only: Misc Buffer. (line 15)
+* top-level <1>: Quitting. (line 53)
+* top-level: Recursive Edit. (line 28)
+* transpose-chars <1>: Transpose. (line 18)
+* transpose-chars: Moving Point. (line 15)
+* transpose-lines: Transpose. (line 30)
+* transpose-sexps <1>: Lists. (line 108)
+* transpose-sexps: Transpose. (line 30)
+* transpose-words <1>: Words. (line 55)
+* transpose-words: Transpose. (line 30)
+* undo: Undo. (line 20)
+* unexpand-abbrev: Expanding Abbrevs. (line 48)
+* universal-argument: Arguments. (line 28)
+* universal-coding-system-argument: Specify Coding. (line 34)
+* untabify: Just Spaces. (line 12)
+* up-list: TeX Editing. (line 49)
+* upcase-region: Case. (line 46)
+* upcase-word <1>: Case. (line 24)
+* upcase-word: Fixing Case. (line 16)
+* validate-tex-buffer: TeX Editing. (line 55)
+* vc-cancel-version: Editing with VC. (line 76)
+* vc-create-snapshot: Making Snapshots. (line 9)
+* vc-diff: Old Versions. (line 22)
+* vc-directory: VC Status. (line 11)
+* vc-insert-headers: Version Headers. (line 11)
+* vc-next-action: Editing with VC. (line 107)
+* vc-print-log: VC Status. (line 6)
+* vc-register: Editing with VC. (line 92)
+* vc-rename-file: Renaming and VC. (line 6)
+* vc-retrieve-snapshot: Making Snapshots. (line 14)
+* vc-revert-buffer: Editing with VC. (line 66)
+* vc-update-change-log: Change Logs and VC. (line 11)
+* vc-version-other-window: Old Versions. (line 17)
+* view-buffer: Misc Buffer. (line 30)
+* view-diary-entries: Diary Commands. (line 35)
+* view-emacs-news: Misc Help. (line 51)
+* view-file: Misc File Ops. (line 44)
+* view-hello-file: Mule Intro. (line 59)
+* view-lossage: Misc Help. (line 27)
+* view-register: Registers. (line 12)
+* visit-tags-table: Select Tags Table. (line 70)
+* what-cursor-position: Position Info. (line 47)
+* what-line: Position Info. (line 31)
+* what-page: Position Info. (line 31)
+* where-is: Name Help. (line 44)
+* widen: Narrowing. (line 39)
+* widget-backward: Changing an Option. (line 90)
+* widget-complete: Changing an Option. (line 52)
+* widget-forward: Changing an Option. (line 90)
+* window-configuration-to-register <1>: Split Window. (line 46)
+* window-configuration-to-register: RegConfig. (line 6)
+* word-search-backward: Word Search. (line 33)
+* word-search-forward: Word Search. (line 33)
+* write-abbrev-file: Saving Abbrevs. (line 24)
+* write-file: Saving. (line 73)
+* x-copy-primary-selection: X Selection Commands.
+ (line 6)
+* x-create-frame: X Resources. (line 6)
+* x-delete-primary-selection: X Selection Commands.
+ (line 6)
+* x-insert-selection: X Selection Commands.
+ (line 6)
+* x-kill-primary-selection: X Selection Commands.
+ (line 6)
+* x-mouse-kill: X Selection Commands.
+ (line 6)
+* x-own-secondary-selection: X Selection Commands.
+ (line 6)
+* x-own-selection: X Selection Commands.
+ (line 6)
+* x-set-point-and-insert-selection: X Selection Commands.
+ (line 6)
+* xemacs-local-faq: Misc Help. (line 51)
+* Yank: Kill Ring. (line 6)
+* yank-pop: Earlier Kills. (line 6)
+* yank-rectangle: Rectangles. (line 63)
+* yow: Amusements. (line 6)
+* zap-to-char: Killing. (line 129)
+* zmacs-activate-region: Active Regions. (line 88)
+* zmacs-deactivate-region: Active Regions. (line 93)
\1f
-File: xemacs.info, Node: Mark, Next: Mouse Selection, Prev: Help, Up: Top
+File: xemacs.info, Node: Variable Index, Next: Concept Index, Prev: Command Index, Up: Top
-Selecting Text
+Variable Index
**************
- Many Emacs commands operate on an arbitrary contiguous part of the
-current buffer. You can select text in two ways:
-
- * You use special keys to select text by defining a region between
- point and the mark.
-
- * If you are running XEmacs under X, you can also select text with
- the mouse.
-
-The Mark and the Region
-=======================
-
- To specify the text for a command to operate on, set "the mark" at
-one end of it, and move point to the other end. The text between point
-and the mark is called "the region". You can move point or the mark to
-adjust the boundaries of the region. It doesn't matter which one is
-set first chronologically, or which one comes earlier in the text.
-
- Once the mark has been set, it remains until it is set again at
-another place. The mark remains fixed with respect to the preceding
-character if text is inserted or deleted in a buffer. Each Emacs
-buffer has its own mark; when you return to a buffer that had been
-selected previously, it has the same mark it had before.
-
- Many commands that insert text, such as `C-y' (`yank') and `M-x
-insert-buffer', position the mark at one end of the inserted text--the
-opposite end from where point is positioned, so that the region
-contains the text just inserted.
-
- Aside from delimiting the region, the mark is useful for marking a
-spot that you may want to go back to. To make this feature more useful,
-Emacs remembers 16 previous locations of the mark in the `mark ring'.
-
+\0\b[index\0\b]
* Menu:
-* Setting Mark:: Commands to set the mark.
-* Using Region:: Summary of ways to operate on contents of the region.
-* Marking Objects:: Commands to put region around textual units.
-* Mark Ring:: Previous mark positions saved so you can go back there.
-
-\1f
-File: xemacs.info, Node: Setting Mark, Next: Using Region, Prev: Mark, Up: Mark
-
-Setting the Mark
-----------------
-
- Here are some commands for setting the mark:
-
-`C-<SPC>'
- Set the mark where point is (`set-mark-command').
-
-`C-@'
- The same.
-
-`C-x C-x'
- Interchange mark and point (`exchange-point-and-mark').
-
-`C-<'
- Pushes a mark at the beginning of the buffer.
-
-`C->'
- Pushes a mark at the end of the buffer.
-
- For example, to convert part of the buffer to all upper-case, you
-can use the `C-x C-u' (`upcase-region') command, which operates on the
-text in the region. First go to the beginning of the text you want to
-capitalize and type `C-<SPC>' to put the mark there, then move to the
-end, and then type `C-x C-u' to capitalize the selected region. You
-can also set the mark at the end of the text, move to the beginning,
-and then type `C-x C-u'. Most commands that operate on the text in the
-region have the word `region' in their names.
-
- The most common way to set the mark is with the `C-<SPC>' command
-(`set-mark-command'). This command sets the mark where point is. You
-can then move point away, leaving the mark behind. It is actually
-incorrect to speak of the character `C-<SPC>'; there is no such
-character. When you type <SPC> while holding down <CTRL>, you get the
-character `C-@' on most terminals. This character is actually bound to
-`set-mark-command'. But unless you are unlucky enough to have a
-terminal where typing `C-<SPC>' does not produce `C-@', you should
-think of this character as `C-<SPC>'.
-
- Since terminals have only one cursor, Emacs cannot show you where the
-mark is located. Most people use the mark soon after they set it, before
-they forget where it is. But you can see where the mark is with the
-command `C-x C-x' (`exchange-point-and-mark') which puts the mark where
-point was and point where the mark was. The extent of the region is
-unchanged, but the cursor and point are now at the previous location of
-the mark.
-
- Another way to set the mark is to push the mark to the beginning of a
-buffer while leaving point at its original location. If you supply an
-argument to `C-<' (`mark-beginning-of-buffer'), the mark is pushed N/10
-of the way from the true beginning of the buffer. You can also set the
-mark at the end of a buffer with `C->' (`mark-end-of-buffer'). It
-pushes the mark to the end of the buffer, leaving point alone.
-Supplying an argument to the command pushes the mark N/10 of the way
-from the true end of the buffer.
-
- If you are using XEmacs under the X window system, you can set the
-variable `zmacs-regions' to `t'. This makes the current region (defined
-by point and mark) highlight and makes it available as the X clipboard
-selection, which means you can use the menu bar items on it. *Note
-Active Regions::, for more information.
-
- `C-x C-x' is also useful when you are satisfied with the location of
-point but want to move the mark; do `C-x C-x' to put point there and
-then you can move it. A second use of `C-x C-x', if necessary, puts
-the mark at the new location with point back at its original location.
+* abbrev-all-caps: Expanding Abbrevs. (line 10)
+* abbrev-file-name: Saving Abbrevs. (line 30)
+* abbrev-mode: Abbrevs. (line 12)
+* after-load-alist: Loading. (line 79)
+* after-save-hook: Saving. (line 92)
+* all-christian-calendar-holidays: Holiday Customizing. (line 22)
+* all-hebrew-calendar-holidays: Holiday Customizing. (line 22)
+* all-islamic-calendar-holidays: Holiday Customizing. (line 22)
+* appt-audible: Appt Customizing. (line 9)
+* appt-display-duration: Appt Customizing. (line 9)
+* appt-display-mode-line: Appt Customizing. (line 9)
+* appt-message-warning-time: Appt Customizing. (line 9)
+* appt-msg-window: Appt Customizing. (line 9)
+* appt-visible: Appt Customizing. (line 9)
+* apropos-do-all: Apropos. (line 59)
+* auto-fill-inhibit-regexp: Fill Commands. (line 41)
+* auto-lower-frame: XEmacs under X. (line 59)
+* auto-mode-alist: Choosing Modes. (line 15)
+* auto-raise-frame: XEmacs under X. (line 59)
+* auto-save-default: Auto Save Control. (line 6)
+* auto-save-interval: Auto Save Control. (line 15)
+* auto-save-timeout: Auto Save Control. (line 25)
+* auto-save-visited-file-name: Auto Save Files. (line 26)
+* awk-mode-hook: CC Mode. (line 6)
+* backup-by-copying: Backup Copying. (line 25)
+* backup-by-copying-when-linked: Backup Copying. (line 25)
+* backup-by-copying-when-mismatch: Backup Copying. (line 25)
+* bell-volume: Audible Bell. (line 49)
+* blink-matching-paren: Matching. (line 23)
+* blink-matching-paren-distance: Matching. (line 23)
+* bookmark-save-flag: Bookmarks. (line 50)
+* bookmark-search-size: Bookmarks. (line 56)
+* buffer-file-coding-system: Recognize Coding. (line 57)
+* buffer-file-name: Visiting. (line 75)
+* buffer-file-truename: Visiting. (line 81)
+* buffer-read-only: Misc Buffer. (line 15)
+* buffer-tag-table: Find Tag. (line 49)
+* c++-mode-hook: CC Mode. (line 6)
+* c-initialization-hook: CC Mode. (line 6)
+* c-mode-common-hook: CC Mode. (line 6)
+* c-mode-hook: CC Mode. (line 6)
+* c-mode-map: Keymaps. (line 12)
+* calendar-date-display-form: Date Display Format. (line 6)
+* calendar-daylight-savings-ends: Daylight Savings. (line 21)
+* calendar-daylight-savings-ends-time: Daylight Savings. (line 65)
+* calendar-daylight-savings-starts: Daylight Savings. (line 21)
+* calendar-daylight-time-offset: Daylight Savings. (line 61)
+* calendar-daylight-time-zone-name: Sunrise/Sunset. (line 53)
+* calendar-holiday-marker: Calendar Customizing.
+ (line 33)
+* calendar-holidays: Holiday Customizing. (line 6)
+* calendar-latitude: Sunrise/Sunset. (line 41)
+* calendar-load-hook: Calendar Customizing.
+ (line 41)
+* calendar-location-name: Sunrise/Sunset. (line 41)
+* calendar-longitude: Sunrise/Sunset. (line 41)
+* calendar-standard-time-zone-name: Sunrise/Sunset. (line 53)
+* calendar-time-display-form: Time Display Format. (line 6)
+* calendar-time-zone: Sunrise/Sunset. (line 53)
+* calendar-today-marker: Calendar Customizing.
+ (line 63)
+* calendar-week-start-day: Move to Beginning or End.
+ (line 33)
+* case-fold-search <1>: Replacement and Case.
+ (line 6)
+* case-fold-search: Search Case. (line 6)
+* case-replace: Replacement and Case.
+ (line 6)
+* christian-holidays: Holiday Customizing. (line 6)
+* coding: Recognize Coding. (line 48)
+* command-history: Repetition. (line 57)
+* command-line-args: Command Switches. (line 188)
+* comment-column: Comments. (line 84)
+* comment-end: Comments. (line 107)
+* comment-indent-hook: Comments. (line 124)
+* comment-line-start: Fortran Comments. (line 61)
+* comment-line-start-skip: Fortran Comments. (line 61)
+* comment-multi-line: Comments. (line 113)
+* comment-start: Comments. (line 107)
+* comment-start-skip: Comments. (line 97)
+* compare-ignore-case: Comparing Files. (line 29)
+* compile-command: Compilation. (line 36)
+* completion-auto-help: Completion Options. (line 17)
+* completion-ignored-extensions: Completion Options. (line 6)
+* create-frame-hook: XEmacs under X. (line 47)
+* ctl-arrow: Display Vars. (line 24)
+* ctl-x-map: Keymaps. (line 41)
+* current-input-method: Select Input Method. (line 20)
+* data-directory: Startup Paths. (line 152)
+* data-directory-list: Startup Paths. (line 157)
+* debug-on-error: Lisp Debug. (line 6)
+* debug-on-quit: Lisp Debug. (line 6)
+* default-buffer-file-coding-system: Specify Coding. (line 55)
+* default-directory: File Names. (line 27)
+* default-directory-alist: File Names. (line 46)
+* default-frame-alist: XEmacs under X. (line 31)
+* default-frame-plist: XEmacs under X. (line 31)
+* default-input-method: Select Input Method. (line 35)
+* default-major-mode: Choosing Modes. (line 51)
+* delete-auto-save-files: Auto Save Files. (line 30)
+* delete-old-versions: Backup Deletion. (line 17)
+* describe-function-show-arglist: Name Help. (line 6)
+* diary-date-forms: Diary Customizing. (line 36)
+* diary-display-hook: Fancy Diary Display. (line 6)
+* diary-entry-marker: Calendar Customizing.
+ (line 33)
+* diary-file: Format of Diary File.
+ (line 6)
+* diary-list-include-blanks: Fancy Diary Display. (line 26)
+* diary-mail-days: Diary Commands. (line 77)
+* diff-switches: Comparing Files. (line 6)
+* dired-kept-versions: Dired Deletion. (line 64)
+* dired-listing-switches: Dired Enter. (line 6)
+* display-buffer-function: Pop Up Window. (line 33)
+* doc-directory: Startup Paths. (line 148)
+* echo-keystrokes: Display Vars. (line 19)
+* emacs-lisp-mode-hook: Mode Hooks. (line 6)
+* emacs-roots: Startup Paths. (line 38)
+* EMACSDATA: Startup Paths. (line 153)
+* EMACSLOADPATH: Startup Paths. (line 127)
+* EMACSPATH: Startup Paths. (line 145)
+* enable-local-variables: File Variables. (line 86)
+* enable-recursive-minibuffers: Minibuffer Edit. (line 56)
+* esc-map: Keymaps. (line 41)
+* european-calendar-style: Date Formats. (line 39)
+* exec-directory: Startup Paths. (line 137)
+* exec-path: Startup Paths. (line 142)
+* explicit-shell-file-name: Interactive Shell. (line 27)
+* face-frob-from-locale-first: Faces. (line 77)
+* file-coding-system-alist: Recognize Coding. (line 35)
+* file-name-coding-system: Specify Coding. (line 100)
+* fill-column: Fill Commands. (line 48)
+* fill-prefix: Fill Prefix. (line 39)
+* find-file-compare-truenames: Visiting. (line 81)
+* find-file-hooks: Visiting. (line 127)
+* find-file-not-found-hooks: Visiting. (line 127)
+* find-file-run-dired: Visiting. (line 103)
+* find-file-use-truenames: Visiting. (line 75)
+* fortran-check-all-num-for-matching-do: ForIndent Vars. (line 6)
+* fortran-comment-indent-char: Fortran Comments. (line 57)
+* fortran-comment-indent-style: Fortran Comments. (line 46)
+* fortran-comment-line-column: Fortran Comments. (line 46)
+* fortran-comment-region: Fortran Comments. (line 71)
+* fortran-continuation-char: ForIndent Conv. (line 10)
+* fortran-continuation-indent: ForIndent Vars. (line 6)
+* fortran-do-indent: ForIndent Vars. (line 6)
+* fortran-electric-line-number: ForIndent Num. (line 21)
+* fortran-if-indent: ForIndent Vars. (line 6)
+* fortran-line-number-indent: ForIndent Num. (line 14)
+* fortran-minimum-statement-indent: ForIndent Vars. (line 6)
+* frame-icon-title-format <1>: Command Switches. (line 218)
+* frame-icon-title-format: XEmacs under X. (line 53)
+* frame-title-format <1>: Command Switches. (line 218)
+* frame-title-format: XEmacs under X. (line 53)
+* general-holidays: Holiday Customizing. (line 14)
+* global-map: Keymaps. (line 6)
+* hebrew-holidays: Holiday Customizing. (line 6)
+* help-map: Keymaps. (line 41)
+* holidays-in-diary-buffer: Diary Customizing. (line 6)
+* idl-mode-hook: CC Mode. (line 6)
+* indent-tabs-mode: Just Spaces. (line 6)
+* Info-directory-list: Startup Paths. (line 130)
+* INFOPATH: Startup Paths. (line 134)
+* initial-calendar-window-hook: Calendar Customizing.
+ (line 45)
+* initial-major-mode: Entering Emacs. (line 22)
+* input-method-highlight-flag: Input Methods. (line 67)
+* input-method-verbose-flag: Input Methods. (line 67)
+* input-ring-size: Interactive Shell. (line 55)
+* insert-default-directory <1>: File Names. (line 68)
+* insert-default-directory: Minibuffer File. (line 35)
+* isearch-mode-map: Keymaps. (line 23)
+* islamic-holidays: Holiday Customizing. (line 6)
+* java-mode-hook: CC Mode. (line 6)
+* kept-new-versions: Backup Deletion. (line 6)
+* kept-old-versions: Backup Deletion. (line 6)
+* keyboard-translate-table: Intro to Keystrokes. (line 53)
+* kill-ring-max: Earlier Kills. (line 48)
+* LaTeX-mode-hook: TeX Print. (line 69)
+* lisp-body-indention: Lisp Indent. (line 22)
+* lisp-directory: Startup Paths. (line 118)
+* lisp-indent-offset: Lisp Indent. (line 17)
+* lisp-interaction-mode-hook: Mode Hooks. (line 6)
+* lisp-mode-hook: Mode Hooks. (line 6)
+* lisp-mode-map: Keymaps. (line 12)
+* list-diary-entries-hook: Included Diary Files.
+ (line 17)
+* list-directory-brief-switches: ListDir. (line 33)
+* list-directory-verbose-switches: ListDir. (line 33)
+* load-path <1>: Loading. (line 39)
+* load-path: Startup Paths. (line 123)
+* local-holidays: Holiday Customizing. (line 18)
+* lpr-switches: Hardcopy. (line 24)
+* mail-abbrev-mailrc-file: Mail Headers. (line 65)
+* mail-abbrev-mode-regexp: Mail Headers. (line 88)
+* mail-alias-separator-string: Mail Headers. (line 135)
+* mail-archive-file-name: Mail Headers. (line 140)
+* mail-header-separator: Mail Format. (line 21)
+* mail-mode-hook: Mail Mode. (line 86)
+* make-backup-files: Backup. (line 6)
+* make-tags-files-invisible: Find Tag. (line 49)
+* mark-diary-entries-hook: Included Diary Files.
+ (line 17)
+* mark-diary-entries-in-calendar: Calendar Customizing.
+ (line 22)
+* mark-holidays-in-calendar: Calendar Customizing.
+ (line 29)
+* mark-ring: Mark Ring. (line 32)
+* mark-ring-max: Mark Ring. (line 27)
+* meta-flag: Meta Key. (line 23)
+* minibuffer-confirm-incomplete <1>: Completion Options. (line 22)
+* minibuffer-confirm-incomplete: Minibuffer Edit. (line 40)
+* minibuffer-local-completion-map: Keymaps. (line 23)
+* minibuffer-local-map: Keymaps. (line 23)
+* minibuffer-local-must-match-map: Keymaps. (line 23)
+* minibuffer-local-ns-map: Keymaps. (line 23)
+* mode-line-inverse-video: Mode Line. (line 86)
+* modeline-pointer-glyph: Mouse Selection. (line 10)
+* next-line-add-newlines: Moving Point. (line 110)
+* next-screen-context-lines: Scrolling. (line 50)
+* no-redraw-on-reenter: Display Vars. (line 9)
+* nongregorian-diary-listing-hook: Hebrew/Islamic Entries.
+ (line 13)
+* nongregorian-diary-marking-hook: Hebrew/Islamic Entries.
+ (line 13)
+* nontext-pointer-glyph: Mouse Selection. (line 10)
+* nroff-mode-hook: Nroff Mode. (line 34)
+* number-of-diary-entries: Diary Customizing. (line 14)
+* objc-mode-hook: CC Mode. (line 6)
+* other-holidays: Holiday Customizing. (line 31)
+* outline-mode-hook: Outline Mode. (line 12)
+* outline-regexp: Outline Format. (line 41)
+* page-delimiter: Pages. (line 56)
+* paragraph-separate: Paragraphs. (line 40)
+* paragraph-start: Paragraphs. (line 40)
+* parse-sexp-ignore-comments: Syntax Entry. (line 94)
+* PATH: Startup Paths. (line 144)
+* picture-mode-hook: Picture. (line 41)
+* picture-tab-chars: Tabs in Picture. (line 6)
+* pike-mode-hook: CC Mode. (line 6)
+* plain-TeX-mode-hook: TeX Print. (line 69)
+* print-diary-entries-hook: Diary Customizing. (line 26)
+* repeat-complex-command-map: Keymaps. (line 23)
+* require-final-newline: Saving. (line 88)
+* save-abbrevs: Saving Abbrevs. (line 38)
+* scheme-mode-hook: Mode Hooks. (line 6)
+* scroll-conservatively: Scrolling. (line 84)
+* scroll-step: Scrolling. (line 70)
+* search-slow-speed: Incremental Search. (line 193)
+* search-slow-window-lines: Incremental Search. (line 197)
+* selective-display-ellipses <1>: Outline Visibility. (line 72)
+* selective-display-ellipses: Display Vars. (line 50)
+* sentence-end: Sentences. (line 47)
+* shell-cd-regexp: Interactive Shell. (line 39)
+* shell-file-name: Single Shell. (line 21)
+* shell-popd-regexp: Interactive Shell. (line 39)
+* shell-prompt-pattern: Shell Mode. (line 12)
+* shell-pushd-regexp: Interactive Shell. (line 39)
+* sound-alist: Audible Bell. (line 6)
+* tab-stop-list: Tab Stops. (line 11)
+* tab-width: Display Vars. (line 42)
+* tag-mark-stack-max: Find Tag. (line 49)
+* tag-table-alist <1>: Find Tag. (line 49)
+* tag-table-alist: Select Tags Table. (line 6)
+* tags-always-build-completion-table: Select Tags Table. (line 66)
+* tags-build-completion-table: Find Tag. (line 49)
+* tags-file-name <1>: Find Tag. (line 49)
+* tags-file-name: Select Tags Table. (line 70)
+* term-file-prefix: Terminal Init. (line 24)
+* term-setup-hook: Terminal Init. (line 29)
+* TeX-mode-hook: TeX Print. (line 69)
+* text-mode-hook: Text Mode. (line 22)
+* text-pointer-glyph: Mouse Selection. (line 10)
+* today-invisible-calendar-hook: Calendar Customizing.
+ (line 70)
+* today-visible-calendar-hook: Calendar Customizing.
+ (line 50)
+* track-eol: Moving Point. (line 105)
+* truncate-lines: Continuation Lines. (line 18)
+* truncate-partial-width-windows: Split Window. (line 36)
+* vc-command-messages: Variables for Check-in/out.
+ (line 11)
+* vc-comment-alist: Version Headers. (line 35)
+* vc-default-back-end: Editing with VC. (line 92)
+* vc-header-alist: Version Headers. (line 17)
+* vc-initial-comment: Editing with VC. (line 103)
+* vc-keep-workfiles: Editing with VC. (line 53)
+* vc-log-mode-hook: Log Entries. (line 26)
+* vc-make-backup-files: Editing with VC. (line 49)
+* vc-mistrust-permissions: Variables for Check-in/out.
+ (line 22)
+* vc-path: Variables for Check-in/out.
+ (line 34)
+* vc-static-header-alist: Version Headers. (line 42)
+* vc-suppress-confirm: Variables for Check-in/out.
+ (line 6)
+* version-control: Backup Names. (line 21)
+* view-calendar-holidays-initially: Calendar Customizing.
+ (line 17)
+* view-diary-entries-initially: Calendar Customizing.
+ (line 6)
+* window-min-height: Change Window. (line 36)
+* window-min-width: Change Window. (line 36)
+* write-file-hooks: Saving. (line 92)
+* x-frame-defaults: XEmacs under X. (line 41)
+* zmacs-region-stays: Active Regions. (line 81)
+* zmacs-regions: Active Regions. (line 28)
\1f
-File: xemacs.info, Node: Using Region, Next: Marking Objects, Prev: Setting Mark, Up: Mark
-
-Operating on the Region
------------------------
-
- Once you have created an active region, you can do many things to
-the text in it:
- * Kill it with `C-w' (*note Killing::).
-
- * Save it in a register with `C-x r s' (*note Registers::).
-
- * Save it in a buffer or a file (*note Accumulating Text::).
-
- * Convert case with `C-x C-l' or `C-x C-u'
- (*note Case::).
-
- * Evaluate it as Lisp code with `M-x eval-region' (*note Lisp
- Eval::).
-
- * Fill it as text with `M-q' (*note Filling::).
-
- * Print hardcopy with `M-x print-region' (*note Hardcopy::).
-
- * Indent it with `C-x <TAB>' or `C-M-\' (*note Indentation::).
-
-\1f
-File: xemacs.info, Node: Marking Objects, Next: Mark Ring, Prev: Using Region, Up: Mark
-
-Commands to Mark Textual Objects
---------------------------------
-
- There are commands for placing point and the mark around a textual
-object such as a word, list, paragraph or page.
-
-`M-@'
- Set mark after end of next word (`mark-word'). This command and
- the following one do not move point.
-
-`C-M-@'
- Set mark after end of next Lisp expression (`mark-sexp').
-
-`M-h'
- Put region around current paragraph (`mark-paragraph').
+File: xemacs.info, Node: Concept Index, Next: Frame, Prev: Variable Index, Up: Top
-`C-M-h'
- Put region around current Lisp defun (`mark-defun').
+Concept Index
+*************
-`C-x h'
- Put region around entire buffer (`mark-whole-buffer').
-
-`C-x C-p'
- Put region around current page (`mark-page').
-
- `M-@' (`mark-word') puts the mark at the end of the next word, while
-`C-M-@' (`mark-sexp') puts it at the end of the next Lisp expression.
-These characters sometimes save you some typing.
-
- A number of commands are available that set both point and mark and
-thus delimit an object in the buffer. `M-h' (`mark-paragraph') moves
-point to the beginning of the paragraph that surrounds or follows
-point, and puts the mark at the end of that paragraph (*note
-Paragraphs::). You can then indent, case-convert, or kill the whole
-paragraph. In the same fashion, `C-M-h' (`mark-defun') puts point
-before and the mark after the current or following defun (*note
-Defuns::). `C-x C-p' (`mark-page') puts point before the current page
-(or the next or previous, depending on the argument), and mark at the
-end (*note Pages::). The mark goes after the terminating page
-delimiter (to include it), while point goes after the preceding page
-delimiter (to exclude it). Finally, `C-x h' (`mark-whole-buffer') sets
-up the entire buffer as the region by putting point at the beginning
-and the mark at the end.
-
-\1f
-File: xemacs.info, Node: Mark Ring, Prev: Marking Objects, Up: Mark
-
-The Mark Ring
--------------
-
- Aside from delimiting the region, the mark is also useful for marking
-a spot that you may want to go back to. To make this feature more
-useful, Emacs remembers 16 previous locations of the mark in the "mark
-ring". Most commands that set the mark push the old mark onto this
-ring. To return to a marked location, use `C-u C-<SPC>' (or `C-u
-C-@'); this is the command `set-mark-command' given a numeric argument.
-The command moves point to where the mark was, and restores the mark
-from the ring of former marks. Repeated use of this command moves point
-to all the old marks on the ring, one by one. The marks you have seen
-go to the end of the ring, so no marks are lost.
-
- Each buffer has its own mark ring. All editing commands use the
-current buffer's mark ring. In particular, `C-u C-<SPC>' always stays
-in the same buffer.
-
- Many commands that can move long distances, such as `M-<'
-(`beginning-of-buffer'), start by setting the mark and saving the old
-mark on the mark ring. This makes it easier for you to move back
-later. Searches set the mark, unless they do not actually move point.
-When a command sets the mark, `Mark Set' is printed in the echo area.
-
- The variable `mark-ring-max' is the maximum number of entries to
-keep in the mark ring. If that many entries exist and another entry is
-added, the last entry in the list is discarded. Repeating `C-u
-C-<SPC>' circulates through the entries that are currently in the ring.
-
- The variable `mark-ring' holds the mark ring itself, as a list of
-marker objects in the order most recent first. This variable is local
-in every buffer.
-
-\1f
-File: xemacs.info, Node: Mouse Selection, Next: Additional Mouse Operations, Prev: Mark, Up: Top
-
-Selecting Text with the Mouse
-=============================
-
- If you are using XEmacs under X, you can use the mouse pointer to
-select text. (The normal mouse pointer is an I-beam, the same pointer
-that `xterm' uses.)
-
- The glyph variable `text-pointer-glyph' controls the shape of the
-mouse pointer when over text. You can also control the shape of the
-mouse pointer when over nontext using `nontext-pointer-glyph', and the
-shape of the mouse pointer when over the modeline using
-`modeline-pointer-glyph'. (Remember, you should use `set-glyph-image',
-not `setq', to set one of these variables.)
-
- If you want to get fancy, you can set the foreground and background
-colors of the mouse pointer by setting the `pointer' face.
-
- There are two ways to select a region of text with the mouse:
-
- To select a word in text, double-click with the left mouse button
-while the mouse cursor is over the word. The word is highlighted when
-selected. On monochrome monitors, a stippled background indicates that a
-region of text has been highlighted. On color monitors, a color
-background indicates highlighted text. You can triple-click to select
-whole lines.
-
- To select an arbitrary region of text:
-
- 1. Move the mouse cursor over the character at the beginning of the
- region of text you want to select.
-
- 2. Press and hold the left mouse button.
-
- 3. While holding the left mouse button down, drag the cursor to the
- character at the end of the region of text you want to select.
+\0\b[index\0\b]
+* Menu:
- 4. Release the left mouse button.
- The selected region of text is highlighted.
+* $ in regexp: Regexps. (line 155)
+* ( in regexp: Regexps. (line 198)
+* ) in regexp: Regexps. (line 198)
+* * in regexp: Regexps. (line 35)
+* *? in regexp: Regexps. (line 78)
+* + in regexp: Regexps. (line 65)
+* +? in regexp: Regexps. (line 91)
+* . in regexp: Regexps. (line 29)
+* .mailrc file: Mail Headers. (line 71)
+* // in file name: Minibuffer File. (line 30)
+* ? in regexp: Regexps. (line 72)
+* ?? in regexp: Regexps. (line 94)
+* [ in regexp: Regexps. (line 106)
+* \ in regexp: Regexps. (line 162)
+* \' in regexp: Regexps. (line 283)
+* \(?: in regexp: Regexps. (line 237)
+* \< in regexp: Regexps. (line 301)
+* \= in regexp: Regexps. (line 287)
+* \> in regexp: Regexps. (line 304)
+* \` in regexp: Regexps. (line 279)
+* \B in regexp: Regexps. (line 297)
+* \b in regexp: Regexps. (line 291)
+* \S in regexp: Regexps. (line 272)
+* \s in regexp: Regexps. (line 265)
+* \W in regexp: Regexps. (line 262)
+* \w in regexp: Regexps. (line 258)
+* \{n,m\} in regexp: Regexps. (line 97)
+* ] in regexp: Regexps. (line 106)
+* ^ in regexp: Regexps. (line 134)
+* Abbrev mode: Minor Modes. (line 31)
+* abbrevs: Abbrevs. (line 6)
+* aborting: Quitting. (line 44)
+* accumulating text: Accumulating Text. (line 6)
+* active fields (customization buffer): Customization Groups.
+ (line 35)
+* active regions: Active Regions. (line 6)
+* adding menu items: Menu Customization. (line 53)
+* adding menus: Menu Customization. (line 30)
+* againformation: Dissociated Press. (line 27)
+* Apps menu <1>: Apps Menu. (line 6)
+* Apps menu: Pull-down Menus. (line 25)
+* apropos: Apropos. (line 6)
+* architecture-specific directories: Startup Paths. (line 105)
+* arguments (from shell): Command Switches. (line 6)
+* arrow keys: Moving Point. (line 6)
+* ASCII: Intro to Keystrokes. (line 6)
+* Asm mode: Asm Mode. (line 6)
+* astronomical day numbers: Calendar Systems. (line 12)
+* audible bell, changing: Audible Bell. (line 6)
+* Auto Delete Selection menu item: Options Menu. (line 14)
+* Auto Fill mode <1>: Minor Modes. (line 22)
+* Auto Fill mode <2>: Comments. (line 72)
+* Auto Fill mode: Auto Fill. (line 6)
+* Auto-Save mode: Auto Save. (line 6)
+* autoload: Loading. (line 63)
+* automatic package install: Automatically. (line 3)
+* available packages: Available Packages. (line 3)
+* AWK Mode: CC Mode. (line 6)
+* AWK Mode without CC Mode: Older Modes. (line 6)
+* backup file: Backup. (line 6)
+* batch mode: Command Switches. (line 118)
+* beginning of line in regexp: Regexps. (line 146)
+* bell, changing: Audible Bell. (line 6)
+* binary packages: Package Terminology. (line 33)
+* binding: Commands. (line 6)
+* blank lines <1>: Comments. (line 72)
+* blank lines: Blank Lines. (line 16)
+* body lines (Outline mode): Outline Format. (line 6)
+* bold font: Face Customization. (line 6)
+* bookmarks: Bookmarks. (line 6)
+* boredom: Amusements. (line 6)
+* buffer: Frame. (line 6)
+* buffer menu: Several Buffers. (line 6)
+* buffers: Buffers. (line 6)
+* Buffers menu <1>: Buffers Menu. (line 6)
+* Buffers menu: Pull-down Menus. (line 35)
+* Buffers Menu Length... menu item: Options Menu. (line 14)
+* Buffers Sub-Menus menu item: Options Menu. (line 14)
+* buggestion: Dissociated Press. (line 44)
+* bugs: Bugs. (line 6)
+* building packages: Building Packages. (line 3)
+* byte code: Compiling Libraries. (line 6)
+* C Mode: CC Mode. (line 6)
+* C Mode without CC Mode: Older Modes. (line 6)
+* C++ class browser, tags: Tags. (line 27)
+* C++ Mode: CC Mode. (line 6)
+* calendar: Calendar/Diary. (line 6)
+* calendar and LaTeX: LaTeX Calendar. (line 6)
+* calendar, first day of week: Move to Beginning or End.
+ (line 33)
+* candle lighting times: Sexp Diary Entries. (line 119)
+* case conversion <1>: Case. (line 6)
+* case conversion: Fixing Case. (line 16)
+* Case Sensitive Search menu item: Options Menu. (line 14)
+* CCL programs: Mule and Fonts. (line 6)
+* centering: Fill Commands. (line 44)
+* change log: Change Log. (line 6)
+* changing buffers: Select Buffer. (line 6)
+* changing menu items: Menu Customization. (line 103)
+* character set: Intro to Keystrokes. (line 6)
+* character set (in regexp): Regexps. (line 106)
+* checking in files: Concepts of VC. (line 17)
+* checking out files: Concepts of VC. (line 17)
+* Chinese: Mule. (line 6)
+* Chinese calendar: Calendar Systems. (line 53)
+* choosing packages <1>: Which Packages. (line 3)
+* choosing packages: Installing Packages. (line 20)
+* class browser, C++: Tags. (line 27)
+* Clear menu item: Edit Menu. (line 13)
+* clipboard selections: X Clipboard Selection.
+ (line 6)
+* coding systems: Coding Systems. (line 6)
+* command <1>: Key Bindings. (line 7)
+* command: Commands. (line 6)
+* command history: Repetition. (line 6)
+* command line arguments: Command Switches. (line 6)
+* command name: Key Bindings. (line 7)
+* comments: Comments. (line 6)
+* comparing files: Comparing Files. (line 6)
+* compilation errors: Compilation. (line 6)
+* compiling files: Compilation. (line 45)
+* completion: Completion. (line 6)
+* completion (symbol names): Lisp Completion. (line 6)
+* continuation line: Continuation Lines. (line 6)
+* Control-Meta: Lists. (line 6)
+* Coptic calendar: Calendar Systems. (line 41)
+* Copy menu item: Edit Menu. (line 13)
+* copying files: Misc File Ops. (line 16)
+* copying text <1>: Accumulating Text. (line 6)
+* copying text: Yanking. (line 6)
+* CORBA IDL Mode: CC Mode. (line 6)
+* core distribution: Installing Packages. (line 10)
+* crashes: Auto Save. (line 6)
+* creating directories: File Names. (line 51)
+* creating files: Visiting. (line 91)
+* current buffer: Buffers. (line 13)
+* current stack frame: Lisp Debug. (line 44)
+* cursor <1>: Inserting Text. (line 6)
+* cursor: Point. (line 6)
+* cursor motion: Moving Point. (line 6)
+* customization <1>: Customization. (line 6)
+* customization <2>: Lisp Indent. (line 6)
+* customization: Commands. (line 6)
+* customization buffer: Easy Customization. (line 6)
+* customization groups: Customization Groups.
+ (line 6)
+* customizing faces: Face Customization. (line 6)
+* cut buffers: X Selection Commands.
+ (line 6)
+* Cut menu item: Edit Menu. (line 13)
+* cutting: Killing. (line 6)
+* Cyrillic: Mule. (line 6)
+* day of year: General Calendar. (line 21)
+* daylight savings time: Daylight Savings. (line 6)
+* debugger: Lisp Debug. (line 6)
+* default argument: Minibuffer. (line 19)
+* defuns: Defuns. (line 6)
+* Delete Frame menu item: File Menu. (line 11)
+* deleting blank lines: Blank Lines. (line 6)
+* deleting characters and lines: Erasing. (line 24)
+* deleting menu items: Menu Customization. (line 90)
+* deleting packages: Removing Packages. (line 3)
+* deletion <1>: Killing. (line 6)
+* deletion: Inserting Text. (line 13)
+* deletion (of files) <1>: Misc File Ops. (line 21)
+* deletion (of files): Dired. (line 6)
+* diary: Diary. (line 6)
+* diary buffer: Fancy Diary Display. (line 11)
+* diary file: Format of Diary File.
+ (line 6)
+* ding: Audible Bell. (line 15)
+* directories: Startup Paths. (line 6)
+* directory hierarchies: Startup Paths. (line 16)
+* directory listing: ListDir. (line 6)
+* Dired: Dired. (line 6)
+* disabled command: Disabling. (line 6)
+* disabling menu items: Menu Customization. (line 98)
+* Distribution: License. (line 64)
+* doctor: Total Frustration. (line 6)
+* double slash in file name: Minibuffer File. (line 30)
+* drastic changes: Reverting. (line 6)
+* dribble file: Bugs. (line 144)
+* early package hierarchies: Startup Paths. (line 49)
+* Ebrowse: Tags. (line 27)
+* echo area: Echo Area. (line 6)
+* Edit menu <1>: Edit Menu. (line 6)
+* Edit menu: Pull-down Menus. (line 20)
+* editable fields (customization buffer): Customization Groups.
+ (line 35)
+* editing level, recursive <1>: Quitting. (line 44)
+* editing level, recursive: Recursive Edit. (line 6)
+* EDT: Emulation. (line 6)
+* Eliza: Total Frustration. (line 6)
+* Emacs initialization file: Init File. (line 6)
+* Emacs-Lisp mode: Lisp Eval. (line 6)
+* enabling menu items: Menu Customization. (line 98)
+* encoding of characters: Mule. (line 6)
+* End Macro Recording menu item: Edit Menu. (line 13)
+* entering XEmacs: Entering Emacs. (line 6)
+* environment: Single Shell. (line 21)
+* erasing characters and lines: Erasing. (line 24)
+* error log: Compilation. (line 6)
+* etags program: Create Tags Table. (line 6)
+* Ethiopic calendar: Calendar Systems. (line 41)
+* Execute Last Macro menu item: Edit Menu. (line 13)
+* Exit Emacs menu item: File Menu. (line 11)
+* exiting <1>: Recursive Edit. (line 13)
+* exiting: Exiting. (line 6)
+* expansion (of abbrevs): Abbrevs. (line 6)
+* expression: Lists. (line 13)
+* file dates: Interlocking. (line 6)
+* file directory: ListDir. (line 6)
+* File menu <1>: File Menu. (line 6)
+* File menu: Pull-down Menus. (line 16)
+* file names: File Names. (line 6)
+* file protection: Interlocking. (line 77)
+* files <1>: Visiting. (line 21)
+* files <2>: Files. (line 6)
+* files: Basic Files. (line 6)
+* files, remote: Files. (line 13)
+* fill prefix: Fill Prefix. (line 6)
+* filling: Filling. (line 6)
+* font encoding: Mule and Fonts. (line 6)
+* Font menu item: Options Menu. (line 14)
+* font registry: Mule and Fonts. (line 6)
+* fonts: Mule and Fonts. (line 6)
+* fonts and faces: Face Customization. (line 6)
+* formfeed: Pages. (line 6)
+* Fortran mode: Fortran. (line 6)
+* frame: Frame. (line 6)
+* French Revolutionary calendar: Calendar Systems. (line 29)
+* function <1>: Key Bindings. (line 7)
+* function: Commands. (line 6)
+* General Public License: License. (line 7)
+* getting help with keys: Basic Help. (line 6)
+* global keymap: Keymaps. (line 6)
+* global substitution: Replace. (line 6)
+* graphic characters: Inserting Text. (line 6)
+* Greek: Mule. (line 6)
+* Gregorian calendar: Other Calendars. (line 6)
+* grinding: Grinding. (line 6)
+* hardcopy: Hardcopy. (line 6)
+* header (TeX mode): TeX Print. (line 57)
+* headers (of mail message): Mail Headers. (line 6)
+* heading lines (Outline mode): Outline Format. (line 6)
+* Hebrew calendar: Calendar Systems. (line 16)
+* help: Help. (line 6)
+* Help menu <1>: Help Menu. (line 6)
+* Help menu: Pull-down Menus. (line 43)
+* hierarchies: Startup Paths. (line 16)
+* history of commands: Repetition. (line 6)
+* history of minibuffer input: Minibuffer History. (line 6)
+* holiday forms: Holiday Customizing. (line 34)
+* holidays: Holidays. (line 6)
+* Hook variables: Mode Hooks. (line 6)
+* horizontal scrolling: Horizontal Scrolling.
+ (line 12)
+* Icomplete mode: Completion Options. (line 27)
+* ignoriginal: Dissociated Press. (line 36)
+* indentation <1>: Comments. (line 6)
+* indentation <2>: Grinding. (line 6)
+* indentation: Indentation. (line 6)
+* inferior process: Compilation. (line 6)
+* Info: Misc Help. (line 6)
+* init file: Init File. (line 6)
+* input methods: Input Methods. (line 6)
+* Insert File... menu item: File Menu. (line 11)
+* inserting blank lines: Blank Lines. (line 6)
+* insertion: Inserting Text. (line 6)
+* install: Installing Packages. (line 3)
+* installing packages: Installing Packages. (line 3)
+* international scripts: Mule. (line 6)
+* interval operator (in regexps): Etags Regexps. (line 21)
+* invisible lines: Outline Mode. (line 6)
+* IPA: Mule. (line 6)
+* Islamic calendar: Calendar Systems. (line 20)
+* ISO commercial calendar: Calendar Systems. (line 6)
+* italic font: Face Customization. (line 6)
+* Japanese: Mule. (line 6)
+* Java Mode: CC Mode. (line 6)
+* Julian calendar: Calendar Systems. (line 8)
+* Julian day numbers: Calendar Systems. (line 12)
+* justification: Fill Commands. (line 36)
+* key rebinding, permanent: Init File. (line 6)
+* key rebinding, this session: Rebinding. (line 6)
+* keyboard macros: Keyboard Macros. (line 6)
+* keycode: Super and Hyper Keys.
+ (line 38)
+* keymap <1>: Keymaps. (line 6)
+* keymap: Commands. (line 6)
+* keystroke: Intro to Keystrokes. (line 6)
+* keysym: Intro to Keystrokes. (line 16)
+* keysyms: Super and Hyper Keys.
+ (line 38)
+* Kill Buffer menu item: File Menu. (line 11)
+* kill ring: Yanking. (line 6)
+* killing: Killing. (line 6)
+* killing characters and lines: Erasing. (line 24)
+* killing Emacs: Exiting. (line 6)
+* Korean: Mule. (line 6)
+* language environments: Language Environments.
+ (line 6)
+* last package hierarchies: Startup Paths. (line 49)
+* late package hierarchies: Startup Paths. (line 49)
+* LaTeX: TeX Mode. (line 6)
+* leaving Emacs: Exiting. (line 6)
+* libraries: Lisp Libraries. (line 6)
+* license to copy XEmacs: License. (line 7)
+* line number: Position Info. (line 31)
+* line wrapping: Continuation Lines. (line 6)
+* Lisp: Programs. (line 6)
+* Lisp mode: Program Modes. (line 6)
+* list: Lists. (line 13)
+* loading libraries: Loading. (line 34)
+* loading Lisp code: Lisp Libraries. (line 6)
+* local keymap: Keymaps. (line 12)
+* local variables: Locals. (line 16)
+* local variables in files: File Variables. (line 6)
+* local.rules: Local.rules File. (line 3)
+* locking and version control: Concepts of VC. (line 17)
+* log entry: Editing with VC. (line 38)
+* mail <1>: Reading Mail. (line 6)
+* mail: Sending Mail. (line 6)
+* major modes: Major Modes. (line 6)
+* make: Compilation. (line 6)
+* manual package install: Manually. (line 3)
+* manuals, on-line: Misc Help. (line 6)
+* mark: Mark. (line 6)
+* mark ring <1>: Mark and Region. (line 35)
+* mark ring: Mark Ring. (line 6)
+* Markov chain: Dissociated Press. (line 36)
+* master file: Concepts of VC. (line 6)
+* matching parentheses: Matching. (line 6)
+* Mayan calendar: Calendar Systems. (line 35)
+* Mayan calendar round: Mayan Calendar. (line 64)
+* Mayan haab calendar: Mayan Calendar. (line 56)
+* Mayan long count: Mayan Calendar. (line 36)
+* Mayan tzolkin calendar: Mayan Calendar. (line 48)
+* menus <1>: Change Window. (line 54)
+* menus: Pull-down Menus. (line 44)
+* message <1>: Reading Mail. (line 6)
+* message: Sending Mail. (line 6)
+* Meta: Words. (line 6)
+* minibuffer <1>: Keymaps. (line 23)
+* minibuffer <2>: M-x. (line 18)
+* minibuffer: Minibuffer. (line 6)
+* minibuffer history: Minibuffer History. (line 6)
+* minor modes: Minor Modes. (line 6)
+* mistakes, correcting <1>: Fixit. (line 6)
+* mistakes, correcting: Undo. (line 6)
+* mocklisp: Mocklisp. (line 6)
+* mode hook: Mode Hooks. (line 6)
+* mode line <1>: Minor Modes. (line 6)
+* mode line: Mode Line. (line 6)
+* mode, Term: Term Mode. (line 6)
+* modified (buffer): Visiting. (line 41)
+* modifier key: Intro to Keystrokes. (line 16)
+* modifier mapping: Super and Hyper Keys.
+ (line 83)
+* moon, phases of: Lunar Phases. (line 6)
+* mouse operations: Additional Mouse Operations.
+ (line 6)
+* mouse selection: Mouse Selection. (line 6)
+* movement: Moving Point. (line 6)
+* moving inside the calendar: Calendar Motion. (line 6)
+* moving point: Moving Point. (line 6)
+* moving text: Yanking. (line 6)
+* moving the cursor: Moving Point. (line 6)
+* MULE: Mule. (line 6)
+* multi-frame XEmacs: XEmacs under X. (line 16)
+* multibyte characters: Mule. (line 6)
+* named configurations (RCS): Snapshot Caveats. (line 6)
+* narrowing: Narrowing. (line 6)
+* New Frame menu item: File Menu. (line 11)
+* newline: Inserting Text. (line 19)
+* non-incremental search: Non-Incremental Search.
+ (line 6)
+* nroff: Nroff Mode. (line 6)
+* numeric arguments: Arguments. (line 6)
+* Objective C Mode: CC Mode. (line 6)
+* Old AWK Mode: Older Modes. (line 6)
+* Old C Mode: Older Modes. (line 6)
+* old-c-mode: Older Modes. (line 6)
+* omer count: Sexp Diary Entries. (line 119)
+* on-line manuals: Misc Help. (line 6)
+* Open File, New Frame... menu item: File Menu. (line 11)
+* Open File... menu item: File Menu. (line 11)
+* option <1>: Examining. (line 28)
+* option: Variables. (line 6)
+* Options menu <1>: Options Menu. (line 6)
+* Options menu: Pull-down Menus. (line 31)
+* other editors: Emulation. (line 6)
+* outlines: Outline Mode. (line 6)
+* outragedy: Dissociated Press. (line 44)
+* Overstrike menu item: Options Menu. (line 14)
+* Overwrite mode: Minor Modes. (line 26)
+* package building: Building Packages. (line 3)
+* package distributions: Package Terminology. (line 24)
+* package hierarchies: Startup Paths. (line 43)
+* package path: Startup Paths. (line 73)
+* package tools: Automatically. (line 3)
+* packages <1>: Available Packages. (line 3)
+* packages: Packages. (line 6)
+* page number: Position Info. (line 31)
+* pages: Pages. (line 6)
+* paragraphs: Paragraphs. (line 6)
+* parasha, weekly: Sexp Diary Entries. (line 119)
+* Paren Highlighting menu item: Options Menu. (line 14)
+* parentheses: Matching. (line 6)
+* Paste menu item: Edit Menu. (line 13)
+* pasting: Yanking. (line 6)
+* path: Startup Paths. (line 9)
+* paths: Startup Paths. (line 91)
+* per-buffer variables: Locals. (line 31)
+* Persian calendar: Calendar Systems. (line 47)
+* phases of the moon: Lunar Phases. (line 6)
+* pictures: Picture. (line 6)
+* point <1>: Inserting Text. (line 6)
+* point: Point. (line 6)
+* pointer face: Mouse Selection. (line 17)
+* pointer shapes: Mouse Selection. (line 6)
+* prefix key sequence: Key Sequences. (line 29)
+* presidentagon: Dissociated Press. (line 18)
+* primary selections: X Selection Commands.
+ (line 6)
+* Print Buffer menu item: File Menu. (line 11)
+* Programming Languages: Programs. (line 6)
+* prompt: Minibuffer. (line 13)
+* properbose: Dissociated Press. (line 44)
+* Pull-down Menus <1>: Change Window. (line 54)
+* Pull-down Menus: Pull-down Menus. (line 44)
+* query replace: Query Replace. (line 6)
+* quitting: Quitting. (line 6)
+* quitting (in search): Incremental Search. (line 76)
+* quitting Emacs: Exiting. (line 6)
+* quoting: Inserting Text. (line 33)
+* random sentences: CONX. (line 6)
+* RCS: Concepts of VC. (line 6)
+* Read Only menu item: Options Menu. (line 14)
+* read-only buffer: Misc Buffer. (line 15)
+* rebinding keys, permanently: Init File. (line 6)
+* rebinding keys, this session: Rebinding. (line 6)
+* rectangle <1>: Rectangles in Picture.
+ (line 6)
+* rectangle: RegRect. (line 6)
+* rectangles: Rectangles. (line 6)
+* recursive editing level <1>: Quitting. (line 44)
+* recursive editing level: Recursive Edit. (line 6)
+* redefining keys: Key Bindings Using Strings.
+ (line 22)
+* regexp: Regexp Search. (line 6)
+* regexp alternative: Regexps. (line 184)
+* regexp grouping: Regexps. (line 198)
+* region <1>: Case. (line 46)
+* region: Mark. (line 6)
+* registered file: Concepts of VC. (line 6)
+* registers: Registers. (line 6)
+* regular expression: Regexp Search. (line 6)
+* regular packages: Package Terminology. (line 11)
+* remote files: Files. (line 13)
+* removing directories: File Names. (line 51)
+* removing packages: Removing Packages. (line 3)
+* replacement: Replace. (line 6)
+* restriction: Narrowing. (line 6)
+* Revert Buffer menu item: File Menu. (line 11)
+* root of a hierarchy: Startup Paths. (line 34)
+* rosh hodesh: Sexp Diary Entries. (line 119)
+* Russian: Mule. (line 6)
+* Save Buffer As ... menu item: File Menu. (line 11)
+* Save Buffer menu item: File Menu. (line 11)
+* Save Options: Options Menu. (line 14)
+* saving: Visiting. (line 21)
+* saving option value: Changing an Option. (line 101)
+* SCCS: Concepts of VC. (line 6)
+* scrolling: Scrolling. (line 10)
+* scrolling in the calendar: Scroll Calendar. (line 6)
+* searching: Search. (line 6)
+* selected buffer: Buffers. (line 13)
+* selected window: Basic Window. (line 12)
+* selective display: Outline Mode. (line 6)
+* self-documentation: Help. (line 6)
+* sentences: Sentences. (line 6)
+* setting option value: Changing an Option. (line 40)
+* setting variables: Examining. (line 6)
+* sexp: Lists. (line 13)
+* sexp diary entries: Sexp Diary Entries. (line 6)
+* shell commands: Shell. (line 6)
+* Shell mode: Shell Mode. (line 6)
+* shift modifier: Representing Keystrokes.
+ (line 31)
+* shrinking XEmacs frame: Exiting. (line 6)
+* simultaneous editing: Interlocking. (line 6)
+* single-file packages: Package Terminology. (line 14)
+* site-specific directories: Startup Paths. (line 101)
+* Size menu item: Options Menu. (line 14)
+* slashes repeated in file name: Minibuffer File. (line 30)
+* snapshots and version control: Snapshots. (line 6)
+* sorting: Sorting. (line 6)
+* sorting diary entries: Fancy Diary Display. (line 31)
+* source packages: Package Terminology. (line 39)
+* spelling: Spelling. (line 6)
+* Split Frame: File Menu. (line 11)
+* Start Macro Recording menu item: Edit Menu. (line 13)
+* starting XEmacs: Entering Emacs. (line 6)
+* startup paths: Startup Paths. (line 6)
+* string substitution: Replace. (line 6)
+* subshell: Shell. (line 6)
+* subtree (Outline mode): Outline Visibility. (line 48)
+* sumo package install: Sumo. (line 3)
+* sunrise and sunset: Sunrise/Sunset. (line 6)
+* suspending: Exiting. (line 6)
+* switching buffers: Select Buffer. (line 6)
+* Syntax Highlighting menu item: Options Menu. (line 14)
+* syntax table <1>: Syntax. (line 6)
+* syntax table: Words. (line 67)
+* tags table: Tags. (line 6)
+* tags, C++: Tags. (line 27)
+* Teach Extended Commands menu item: Options Menu. (line 14)
+* techniquitous: Dissociated Press. (line 36)
+* television: Appending Kills. (line 6)
+* Term mode: Term Mode. (line 6)
+* termscript file: Bugs. (line 153)
+* TeX: TeX Mode. (line 6)
+* text: Text. (line 6)
+* Text mode: Text Mode. (line 6)
+* Tools menu <1>: Tools Menu. (line 6)
+* Tools menu: Pull-down Menus. (line 40)
+* top level: Mode Line. (line 6)
+* transposition <1>: Lists. (line 108)
+* transposition <2>: Words. (line 55)
+* transposition: Transpose. (line 18)
+* truncation: Continuation Lines. (line 18)
+* typos: Fixit. (line 6)
+* Un-split (Keep Others): File Menu. (line 11)
+* Un-split (Keep This): File Menu. (line 11)
+* undo: Undo. (line 6)
+* Undo menu item: Edit Menu. (line 13)
+* variable: Variables. (line 6)
+* variables: Commands. (line 43)
+* version control: Version Control. (line 6)
+* version-specific directories: Startup Paths. (line 97)
+* vi: Emulation. (line 6)
+* viewing: Misc File Ops. (line 44)
+* Viper: Emulation. (line 10)
+* visiting: Visiting. (line 21)
+* visiting files: Visiting. (line 6)
+* weeks, which day they start on: Move to Beginning or End.
+ (line 33)
+* Weight menu item: Options Menu. (line 14)
+* which packages: Which Packages. (line 3)
+* widening: Narrowing. (line 6)
+* window: Frame. (line 6)
+* windows: Windows. (line 6)
+* Windows menu: Change Window. (line 54)
+* word search: Word Search. (line 6)
+* words <1>: Case. (line 24)
+* words <2>: Words. (line 6)
+* words: Fixing Case. (line 16)
+* work file: Concepts of VC. (line 6)
+* wrapping: Continuation Lines. (line 6)
+* X resources: X Resources. (line 6)
+* yahrzeits <1>: Sexp Diary Entries. (line 119)
+* yahrzeits: From Other Calendar. (line 57)
+* yanking: Yanking. (line 6)
+* | in regexp: Regexps. (line 184)
- Once a region of text is selected, it becomes the primary X selection
-(*note Using X Selections::) as well as the Emacs selected region. You
-can paste it into other X applications and use the options from the
-Edit pull-down menu on it. Since it is also the Emacs region, you can
-use Emacs region commands on it.
projects / chise / xemacs-chise.git- / blobdiff