-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
-xemacs/xemacs.texi.
+This is Info file ../../info/xemacs.info, produced by Makeinfo version
+1.68 from the input file xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
START-INFO-DIR-ENTRY
are in Emacs. The meanings of `C-z' and `C-x C-c' as keys in Emacs were
inspired by the standard Berkeley Unix meanings of `C-z' and `C-c', but
that is their only relationship with Unix. You could customize these
-keys to do anything (*note Keymaps::).
+keys to do anything (*note Keymaps::.).
\1f
File: xemacs.info, Node: Command Switches, Next: Startup Paths, Prev: Exiting, Up: Top
`-debug-paths'
Displays information on how XEmacs constructs the various paths
- into its hierarchy on startup. (See also *note Startup Paths::.)
+ into its hierarchy on startup. (See also *note Startup Paths::..)
`-unmapped'
Do not map the initial frame. This is useful if you want to start
xemacs *.c
passes each `.c' file as a separate argument to Emacs, so that Emacs
-visits each file (*note Visiting::).
+visits each file (*note Visiting::.).
Here is an advanced example that assumes you have a Lisp program file
called `hack-c-program.el' which, when loaded, performs some useful
hierarchies respectively. If two components are present, they locate
the early and late hierarchies. If only one component is present, it
locates the late hierarchy. At run time, the package path may also be
-specified via the `EMACSPACKAGEPATH' environment variable.
+specified via the `PACKAGEPATH' environment variable.
An XEmacs package is laid out just like a normal installed XEmacs
lisp directory. It may have `lisp', `etc', `info', and `lib-src'
tarball.
If XEmacs runs with the `-debug-paths' option (*note Command
-Switches::), it will print the values of these variables, hopefully
+Switches::.), it will print the values of these variables, hopefully
aiding in debugging any problems which come up.
`lisp-directory'
To insert printing characters into the text you are editing, just
type them. This inserts the characters into the buffer at the cursor
-(that is, at "point"; *note Point::). The cursor moves forward. Any
+(that is, at "point"; *note Point::.). The cursor moves forward. Any
characters after the cursor move forward too. If the text in the buffer
is `FOOBAR', with the cursor before the `B', and you type `XX', the
result is `FOOXXBAR', with the cursor still before the `B'.
with the specified character code.
A numeric argument to `C-q' specifies how many copies of the quoted
-character should be inserted (*note Arguments::).
+character should be inserted (*note Arguments::.).
If you prefer to have text characters replace (overwrite) existing
text instead of moving it to the right, you can enable Overwrite mode, a
==============================
To do more than insert characters, you have to know how to move point
-(*note Point::). Here are a few of the available commands.
+(*note Point::.). Here are a few of the available commands.
NOTE: Many of the following commands have two versions, one that uses
the function keys (e.g. <LEFT> or <END>) and one that doesn't. The
The file name is given as an "argument" to the command `C-x C-f'
(`find-file'). The command uses the "minibuffer" to read the argument.
-You have to type <RET> to terminate the argument (*note Minibuffer::).
+You have to type <RET> to terminate the argument (*note Minibuffer::.).
You can also use the Open... menu item from the File menu, then type
the name of the file to the prompt.
save the buffer with `C-x C-s', or by choosing Save Buffer from the
File menu, the file is created.
- To learn more about using files, *note Files::.
+ To learn more about using files, *note Files::..
Help
====
curved arrow at the extreme right margin of all but the last line. The
curved arrow indicates that the following screen line is not really a
distinct line in the text, but just the "continuation" of a line too
-long to fit the frame. You can use Auto Fill mode (*note Filling::) to
-have Emacs insert newlines automatically when a line gets too long.
+long to fit the frame. You can use Auto Fill mode (*note Filling::.)
+to have Emacs insert newlines automatically when a line gets too long.
Instead of continuation, long lines can be displayed by "truncation".
This means that all the characters that do not fit in the width of the
To turn off continuation for a particular buffer, set the variable
`truncate-lines' to non-`nil' in that buffer. Truncation instead of
continuation also happens whenever horizontal scrolling is in use, and
-optionally whenever side-by-side windows are in use (*note Windows::).
+optionally whenever side-by-side windows are in use (*note Windows::.).
Altering the value of `truncate-lines' makes it local to the current
buffer; until that time, the default value is in effect. The default
is initially `nil'. *Note Locals::.
current page.
* `M-=' (`count-lines-region') prints the number of lines in the
- region (*note Mark::).
+ region (*note Mark::.).
The command `C-x =' (`what-cursor-position') provides information
about point and about the column the cursor is in. It prints a line in
The Minibuffer
**************
- The "minibuffer" is the facility used by XEmacs commands to read
-arguments more complicated than a single number. Minibuffer arguments
-can be file names, buffer names, Lisp function names, XEmacs command
-names, Lisp expressions, and many other things, depending on the command
-reading the argument. You can use the usual XEmacs editing commands in
-the minibuffer to edit the argument text.
+ Emacs commands use the "minibuffer" to read arguments more
+complicated than a single number. Minibuffer arguments can be file
+names, buffer names, Lisp function names, Emacs command names, Lisp
+expressions, and many other things, depending on the command reading the
+argument. To edit the argument in the minibuffer, you can use Emacs
+editing commands.
When the minibuffer is in use, it appears in the echo area, and the
cursor moves there. The beginning of the minibuffer line displays a
-"prompt" which says what kind of input you should supply and how it
-will be used. Often this prompt is derived from the name of the command
-that the argument is for. The prompt normally ends with a colon.
+"prompt" indicating what kind of input you should supply and how it
+will be used. The prompt is often derived from the name of the command
+the argument is for. The prompt normally ends with a colon.
Sometimes a "default argument" appears in parentheses after the
colon; it, too, is part of the prompt. The default is used as the
default, which is the name of the buffer that will be used if you type
just <RET>.
- The simplest way to enter a minibuffer argument is to type the text
-you want, terminated by <RET> which exits the minibuffer. You can
-cancel the command that wants the argument, and get out of the
-minibuffer, by typing `C-g'.
+ The simplest way to give a minibuffer argument is to type the text
+you want, terminated by <RET> to exit the minibuffer. To get out of
+the minibuffer and cancel the command that it was for, type `C-g'.
Since the minibuffer uses the screen space of the echo area, it can
-conflict with other ways XEmacs customarily uses the echo area. Here is
-how XEmacs handles such conflicts:
+conflict with other ways Emacs customarily uses the echo area. Here is
+how Emacs handles such conflicts:
* If a command gets an error while you are in the minibuffer, this
does not cancel the minibuffer. However, the echo area is needed
hidden for a while. It comes back after a few seconds, or as soon
as you type anything.
- * If in the minibuffer you use a command whose purpose is to print a
- message in the echo area, such as `C-x =', the message is printed
- normally, and the minibuffer is hidden for a while. It comes back
- after a few seconds, or as soon as you type anything.
+ * If you use a command in the minibuffer whose purpose is to print a
+ message in the echo area (for example `C-x =') the message is
+ displayed normally, and the minibuffer is hidden for a while. It
+ comes back after a few seconds, or as soon as you type anything.
* Echoing of keystrokes does not take place while the minibuffer is
in use.
* File: Minibuffer File. Entering file names with the minibuffer.
* Edit: Minibuffer Edit. How to edit in the minibuffer.
* Completion:: An abbreviation facility for minibuffer input.
-* Minibuffer History:: Reusing recent minibuffer arguments.
* Repetition:: Re-executing commands that used the minibuffer.
\1f
Sometimes the minibuffer starts out with text in it. For example,
when you are supposed to give a file name, the minibuffer starts out
-containing the "default directory", which ends with a slash. This is
-to inform you which directory the file will be found in if you do not
-specify a directory.
-
- For example, the minibuffer might start out with these contents:
+containing the "default directory", which ends with a slash. This
+informs you in which directory the file will be looked for if you do
+not specify a different one. For example, the minibuffer might start
+out with:
Find File: /u2/emacs/src/
-where `Find File: ' is the prompt. Typing `buffer.c' specifies the
-file `/u2/emacs/src/buffer.c'. To find files in nearby directories,
-use `..'; thus, if you type `../lisp/simple.el', you will get the file
-named `/u2/emacs/lisp/simple.el'. Alternatively, you can kill with
-`M-<DEL>' the directory names you don't want (*note Words::).
+where `Find File: ' is the prompt. Typing `buffer.c' specifies the file
+`/u2/emacs/src/buffer.c'. To find files in nearby directories, use
+`..'; thus, if you type `../lisp/simple.el', the file that you visit
+will be the one named
+`/u2/emacs/lisp/simple.el'. Alternatively, you can use `M-<DEL>' to
+kill directory names you don't want (*note Words::.).
- If you don't want any of the default, you can kill it with `C-a
-C-k'. But you don't need to kill the default; you can simply ignore it.
-Insert an absolute file name, one starting with a slash or a tilde,
-after the default directory. For example, to specify the file
-`/etc/termcap', just insert that name, giving these minibuffer contents:
+ You can also type an absolute file name, one starting with a slash
+or a tilde, ignoring the default directory. For example, to find the
+file `/etc/termcap', just type the name, giving:
Find File: /u2/emacs/src//etc/termcap
-XEmacs gives a special meaning to a double slash (which is not normally
-a useful thing to write): it means, "ignore everything before the
-second slash in the pair." Thus, `/u2/emacs/src/' is ignored in the
-example above, and you get the file `/etc/termcap'.
+Two slashes in a row are not normally meaningful in Unix file names, but
+they are allowed in XEmacs. They mean, "ignore everything before the
+second slash in the pair." Thus, `/u2/emacs/src/' is ignored, and you
+get the file `/etc/termcap'.
If you set `insert-default-directory' to `nil', the default
directory is not inserted in the minibuffer. This way, the minibuffer
Editing in the Minibuffer
=========================
- The minibuffer is an XEmacs buffer (albeit a peculiar one), and the
-usual XEmacs commands are available for editing the text of an argument
+ The minibuffer is an Emacs buffer (albeit a peculiar one), and the
+usual Emacs commands are available for editing the text of an argument
you are entering.
Since <RET> in the minibuffer is defined to exit the minibuffer, you
-can't use it to insert a newline in the minibuffer. To do that, type
-`C-o' or `C-q C-j'. (Recall that a newline is really the character
-control-J.)
+must use `C-o' or `C-q <LFD>' to insert a newline into the minibuffer.
+(Recall that a newline is really the <LFD> character.)
- The minibuffer has its own window which always has space on the
+ The minibuffer has its own window, which always has space on the
screen but acts as if it were not there when the minibuffer is not in
-use. When the minibuffer is in use, its window is just like the
-others; you can switch to another window with `C-x o', edit text in
-other windows and perhaps even visit more files, before returning to the
-minibuffer to submit the argument. You can kill text in another window,
-return to the minibuffer window, and then yank the text to use it in the
-argument. *Note Windows::.
-
- There are some restrictions on the use of the minibuffer window,
-however. You cannot switch buffers in it--the minibuffer and its
-window are permanently attached. Also, you cannot split or kill the
-minibuffer window. But you can make it taller in the normal fashion with
-`C-x ^'.
-
- If while in the minibuffer you issue a command that displays help
-text of any sort in another window, you can use the `C-M-v' command
-while in the minibuffer to scroll the help text. This lasts until you
-exit the minibuffer. This feature is especially useful if a completing
-minibuffer gives you a list of possible completions. *Note Other
-Window::.
+use. The minibuffer window is just like the others; you can switch to
+another window with `C-x o', edit text in other windows, and perhaps
+even visit more files before returning to the minibuffer to submit the
+argument. You can kill text in another window, return to the minibuffer
+window, and then yank the text to use it in the argument. *Note
+Windows::.
+
+ There are, however, some restrictions on the use of the minibuffer
+window. You cannot switch buffers in it--the minibuffer and its window
+are permanently attached. You also cannot split or kill the minibuffer
+window, but you can make it taller with `C-x ^'.
+
+ If you are in the minibuffer and issue a command that displays help
+text in another window, that window will be scrolled if you type
+`M-C-v' while in the minibuffer until you exit the minibuffer. This
+feature is helpful if a completing minibuffer gives you a long list of
+possible completions.
If the variable `minibuffer-confirm-incomplete' is `t', you are
asked for confirmation if there is no known completion for the text you
typed. For example, if you attempted to visit a non-existent file, the
minibuffer might read:
- Find File: chocolate_bar.c [no completions, confirm]
+ Find File:chocolate_bar.c [no completions, confirm]
If you press `Return' again, that confirms the filename. Otherwise,
you can continue editing it.
- XEmacs supports recursive use of the minibuffer. However, it is easy
-to do this by accident (because of autorepeating keyboards, for example)
-and get confused. Therefore, most XEmacs commands that use the
+ Emacs supports recursive use of the minibuffer. However, it is easy
+to do this by accident (because of autorepeating keyboards, for
+example) and get confused. Therefore, most Emacs commands that use the
minibuffer refuse to operate if the minibuffer window is selected. If
the minibuffer is active but you have switched to a different window,
recursive use of the minibuffer is allowed--if you know enough to try
to do this, you probably will not get confused.
- If you set the variable `enable-recursive-minibuffers' to a
+ If you set the variable `enable-recursive-minibuffers' to be
non-`nil', recursive use of the minibuffer is always allowed.
projects / chise / xemacs-chise.git.1 / blobdiff