cmds.doc

早期freebsd实现

This deletes the text in the region and saves it on the kill ring.
Commands that delete text but save it on the kill ring all have the
word "kill" in their names.  Type "C-Y" to yank back the most recent
kill.

:entry "kill-s-expression" "Command"
This kills the text from point to the end of the current or next s-
expression.

:entry "kill-some-buffers" "Command"
This goes through all the existing buffers and asks whether or not to
kill them.  If you decide to kill a buffer, and it turns out that the
buffer is modified, JOVE will offer to save it first.  This is useful
for when JOVE runs out of memory to store lines (this only happens on
PDP-11's) and you have lots of buffers that you are no longer using.

:entry "kill-to-beginning-of-sentence" "Command"
This kills from point to the beginning of the current or previous
sentence.

:entry "kill-to-end-of-line" "Command"
This kills from point to the end of the current line.  When point is
at the end of the line the line separator is deleted and the next line
is joined with current one.  If a numeric argument is supplied that
many lines are killed; if the argument is negative that many lines
"before" point are killed; if the argument is zero the text from point
to the beginning of the line is killed.

:entry "kill-to-end-of-sentence" "Command"
This kills from point to the end of the current or next sentence.  If
a negative numeric argument is supplied it kills from point to the
beginning of the current or previous sentence.

:entry "left-margin" "Variable"
This is how far lines should be indented when auto-indent mode is on,
or when the "newline-and-indent" command is run (usually by typing
LineFeed).  It is also used by fill-paragraph and auto-fill mode.  If
the value is zero (the default) then the left margin is determined
from the surrounding lines.

:entry "left-margin-here" "Command"
This sets the "left-margin" variable to the current position of point.
This is an easy way to say, "Make the left margin begin here," without
having to count the number of spaces over it actually is.

:entry "lisp-mode" "Command"
This turns on Lisp mode.  Lisp mode is one of four mutually exclusive
major modes: Fundamental, Text, C, and Lisp.  In Lisp mode, the
characters Tab and ) are treated specially, similar to the way they
are treated in C mode.  Also, Auto Indent mode is affected, and
handled specially.

:entry "list-buffers" "Command"
This types out a list containing various information about each
buffer.  Right now that list looks like this:

      (* means the buffer needs saving)
      NO  Lines Type        Name           File
      --  ----- ----        ----           ----
      1   1     File        Main           [No file]
      2   1     Scratch   * Minibuf        [No file]
      3   519   File      * commands.doc   commands.doc

The first column lists the buffer's number.  When JOVE prompts for a
buffer name you can either type in the full name, or you can simply
type the buffer's number.  The second column is the number of lines in
the buffer.  The third says what type of buffer.  There are four
types: "File", "Scratch", "Process", "I-Process".  "File" is simply a
buffer that holds a file; "Scratch" is for buffers that JOVE uses
internally; "Process" is one that holds the output from a UNIX
command; "I-Process" is one that has an interactive process attached
to it.  The next column contains the name of the buffer.  And the last
column is the name of the file that's attached to the buffer.  In this
case, both Minibuf and commands.doc have been changed but not yet
saved.  In fact Minibuf won't be saved since it's an internal JOVE
buffer that I don't even care about.

:entry "list-processes" "Command"
This makes a list somewhat like "list-buffers" does, except its list
consists of the current interactive processes.  Right now the list
looks like this:

      Buffer           Status           Pid    Command
      ------           ------           ---    -------
      *shell*          Running          18415shell
      fgrep            Done             18512   fgrep -n Buffer *.c

The first column has the name of the buffer to which the process is
attached.  The second has the status of the process; if a process has
exited normally the status is "Done" as in fgrep; if the process
exited with an error the status is "Exit N" where N is the value of
the exit code; if the process was killed by some signal the status is
the name of the signal that was used; otherwise the process is
running.  The last column is the name of the command that is being
run.

:entry "macify" "Variable"
When this variable is on, JOVE will use the standard Macintosh file-
selector dialog in place of the traditional JOVE minibuffer. (Mac
version only)

:entry "mail-check-frequency" "Variable"
This is how often (in seconds) JOVE should check your mailbox for
incoming mail.  If you set this to ZERO JOVE won't check for new mail.
See also the "mailbox" and "disable-biff" variables.

:entry "mailbox" "Variable"
Set this to the full pathname of your mailbox.  JOVE will look here to
decide whether or not you have any unread mail.  This defaults to
/usr/spool/mail/$USER, where $USER is set to your login name.

:entry "make-backup-files" "Variable"
If this variable is set, then whenever JOVE writes out a file, it will
move the previous version of the file (if there was one) to
"#filename".  This is often convenient if you save a file by accident.
The default value of this variable is "off".  "Note:" this is an
optional part of JOVE, and your guru may not have it enabled, so it
may not work.

:entry "make-buffer-unmodified" "Command"
This makes JOVE think the selected buffer hasn't been changed even if
it has.  Use this when you accidentally change the buffer but don't
want it considered changed.  Watch the mode line to see the *
disappear when you use this command.

:entry "make-keymap" "Command"
This creates an empty keymap with a name you supply.  That name can be
used to reference the keymap in other commands, such as bind-keymap-
to-key.

:entry "make-macro-interactive" "Command"
This command is meaningful only while you are defining a keyboard
macro, and when you are in the minibuffer.  Ordinarily, when a command
in a macro definition requires a trailing text argument (file name,
search string, etc.), the argument you supply becomes part of the
macro definition.  If you want to be able to supply a different
argument each time the macro is used, then while you are defining it,
you should give the make-macro-interactive command just before typing
the argument which will be used during the definition process.  Note:
you must bind this command to a key in order to use it; you can't say
"ESC X make-macro-interactive".

:entry "mark-threshold" "Variable"
This variable contains the number of lines point may move by before
the mark is set.  If, in a search or something, point moves by more
than this many lines, the mark is set so that you may return easily.
The default value of this variable is 22 (one screenful, on most
terminals).

:entry "marks-should-float" "Variable"
When this variable is "off", the position of a mark is remembered as a
line number within the buffer and a character number within the line.
If you add or delete text before the mark, it will no longer point to
the text you marked originally because that text is no longer at the
same line and character number.  When this variable is "on", the
position of a mark is adjusted to compensate for each insertion and
deletion.  This makes marks much more sensible to use, at the cost of
slowing down insertion and deletion somewhat.  The default value is
"on".

:entry "match-regular-expressions" "Variable"
When set, JOVE will match regular expressions in search patterns.
This makes special the characters ., *, [, ], ^, and $, and the two-
character sequences \<, \>, \{, \} and \|.  See the "ed(1)" manual
page, the tutorial "Advanced Editing in UNIX", and the section above
"Searching with Regular Expressions" for more information.

:entry "meta-key" "Variable"
You should set this variable to "on" if your terminal has a real Meta
key.  If your terminal has such a key, then a key sequence like ESC Y
can be entered by holding down Meta and typing Y.  NOTE:  In some
systems, this disables interrupting noninteractive shell commands.

:entry "mode-line" "Variable"
The format of the mode line can be determined by setting this
variable.  The items in the line are specified using a format similar
to that used by printf(3), with the special things being marked as
"%x".  Digits may be used between the 'x' may be:

          C    check for new mail, and displays "[New mail]" if there
               is any (see also the mail-check-interval and disable-biff
               variables)
          F    the current file name, with leading path stripped
          M    the current list of major and minor modes
          b    the current buffer name
          c    the fill character (-)
          d    the current directory
          e    extra space in modeline is distributed evenly
               among the places %e is used (used for justifying,
               separating, or centering parts of the modeline)
          f    the current file name
          l    the current load average (updated automatically)
          mxy  x, when the buffer is modified or y, when not
          n    the current buffer number
          p    interactive process status for process windows
          s    space, but only if previous character is not a space
          t    the current time (updated automatically)
          w    a '>' for windows which are scrolled left
          [ ]  the square brackets printed when in a recursive edit
          ( )  items enclosed in %( ... %) will only be printed on
               the bottom mode line, rather than copied when the
               window is split

In addition, any other character is simply copied into the mode line.
Characters may be escaped with a backslash.  To get a feel for all
this, try typing "ESC X print mode-line" and compare the result with
your current mode line.

:entry "mode-line-color" "Variable"
This specifies the color of the modeline (PC version only).  Its
default value is 0, and in that case it is drawn in reverse video.  If
it has any other value, this value is used as the attribute in the
Bios calls.

:entry "mode-line-should-standout" "Variable"
If set, the mode line will be printed in reverse video, if your
terminal supports it.  The default for this variable is "off".

:entry "name-kbd-macro" "Command"
This copies the keyboard macro and gives it a name freeing up the
keyboard macro so you can define some more.  Keyboard macros with
their own names can be bound to keys just like built in commands can.
See the "define-macro," "source" and "write-macros-to-file" commands.

:entry "newline" "Command"
This divides the current line at point moving all the text to the
right of point down onto the newly created line.  Point moves down to
the beginning of the new line.

:entry "newline-and-backup" "Command"
This divides the current line at point moving all the text to the
right of point down onto the newly created line.  The difference
between this and "newline" is that point does not move down to the
beginning of the new line.

:entry "newline-and-indent" "Command"
This behaves the same was as Return does when in Auto Indent mode.
This makes Auto Indent mode obsolete but it remains in the name of
backward compatibility.

:entry "next-error" "Command"
This moves to the next error in the list of errors that were parsed
with "parse-errors."  In one window the list of errors is shown with
the current one always at the top.  In another window is the file that
contains the error.  Point is positioned in this window on the line
where the error occurred.

:entry "next-line" "Command"
This moves down to the next line.

:entry "next-page" "Command"
This displays the next page of the buffer by taking the bottom line of
the window and redrawing the window with it at the top.  If there
isn't another page in the buffer JOVE rings the bell.  If a numeric
argument is supplied the screen is scrolled up that many lines; if the
argument is negative the screen is scrolled down.

:entry "next-window" "Command"
This moves into the next window.  Windows live in a circular list so
when you're in the bottom window and you try to move to the next one
you are moved to the top window.  It is an error to use this command
with only one window.

:entry "number-lines-in-window" "Command"
This displays the line numbers for each line in the buffer being
displayed.  The number isn't actually part of the text; it's just
printed before the actual buffer line is.  To turn this off you run
the command again; it toggles.

:entry "over-write-mode" "Command"
This turns Over Write mode on (or off if it's currently on) in the
selected buffer.  When on, this mode changes the way the self-
inserting characters work.  Instead of inserting themselves and
pushing the rest of the line over to the right, they replace or over-
write the existing character.  Also, DEL replaces the character before
point with a space instead of deleting it.  When Over Write mode is on
"OvrWt" is displayed on the mode line.

:entry "page-next-window" "Command"
This displays the next page in the next window.  This is exactly the
same as "C-X N C-V C-X P".

:entry "paren-flash" "Command"