@c This is part of the Emacs manual.
-@c Copyright (C) 1985,86,87,93,94,95,97,2000,2001, 2002, 2004
-@c Free Software Foundation, Inc.
+@c Copyright (C) 1985, 1986, 1987, 1993, 1994, 1995, 1997, 2000, 2001,
+@c 2002, 2003, 2004, 2005 Free Software Foundation, Inc.
@c See file emacs.texi for copying conditions.
@node Text, Programs, Indentation, Top
@chapter Commands for Human Languages
The commands @kbd{M-a} and @kbd{M-e} (@code{backward-sentence} and
@code{forward-sentence}) move to the beginning and end of the current
sentence, respectively. They were chosen to resemble @kbd{C-a} and
-@kbd{C-e}, which move to the beginning and end of a line. Unlike them,
-@kbd{M-a} and @kbd{M-e} if repeated or given numeric arguments move over
-successive sentences.
+@kbd{C-e}, which move to the beginning and end of a line. Unlike
+them, @kbd{M-a} and @kbd{M-e} move over successive sentences if
+repeated.
Moving backward over a sentence places point just before the first
character of the sentence; moving forward places point right after the
@end example
@noindent
-This example is explained in the section on regexps. @xref{Regexps}.
+This example is explained in the section on regexps. @xref{Regexp Example}.
If you want to use just one space between sentences, you should
set @code{sentence-end} to this value:
@end example
@noindent
-You should also set the variable @code{sentence-end-double-space} to
-@code{nil} so that the fill commands expect and leave just one space at
-the end of a sentence. Note that this makes it impossible to
-distinguish between periods that end sentences and those that indicate
-abbreviations.
+This is what setting the variable @code{sentence-end-double-space} to
+@code{nil} automatically does. But note that this makes it impossible
+to distinguish between periods that end sentences and those that
+indicate abbreviations.
@node Paragraphs
@section Paragraphs
@kbd{M-@{} moves to the beginning of the current or previous
paragraph, while @kbd{M-@}} moves to the end of the current or next
paragraph. Blank lines and text-formatter command lines separate
-paragraphs and are not considered part of any paragraph. In Indented
-Text mode, but not in Text mode, an indented line also starts a new
-paragraph. (If a paragraph is preceded by a blank line, these
-commands treat that blank line as the beginning of the paragraph.)
+paragraphs and are not considered part of any paragraph. In
+Paragraph-Indent Text mode, but not in Text mode, an indented line
+also starts a new paragraph. If there is a blank line before the
+paragraph, @kbd{M-@{} moves to the blank line, because that is
+convenient in practice.
In major modes for programs, paragraphs begin and end only at blank
lines. This makes the paragraph commands continue to be useful even
* Fill Prefix:: Filling paragraphs that are indented
or in a comment, etc.
* Adaptive Fill:: How Emacs can determine the fill prefix automatically.
+* Longlines:: Editing text with very long lines.
@end menu
@node Auto Fill
@subsection Auto Fill Mode
@cindex Auto Fill mode
@cindex mode, Auto Fill
-@cindex word wrap
@dfn{Auto Fill} mode is a minor mode in which lines are broken
automatically when they become too wide. Breaking happens only when
to typical word processor behavior. This works by running a
paragraph-filling command at suitable times.
- When you are typing text, only characters which normally trigger
-auto filling, like the space character, will trigger refilling. This
-is to avoid making it too slow. Apart from self-inserting characters,
-other commands which modify the text cause refilling.
-
- The current implementation is preliminary and probably not robust.
-We expect to improve on it.
-
To toggle the use of Refill mode in the current buffer, type
-@kbd{M-x refill-mode}.
+@kbd{M-x refill-mode}. When you are typing text, only characters
+which normally trigger auto filling, like the space character, will
+trigger refilling. This is to avoid making it too slow. Apart from
+self-inserting characters, other commands which modify the text cause
+refilling.
+
+ The current implementation is preliminary and not robust. You can
+get better ``line wrapping'' behavior using Longlines mode.
+@xref{Longlines}. However, Longlines mode has an important
+side-effect: the newlines that it inserts for you are not saved to
+disk, so the files that you make with Longlines mode will appear to be
+completely unfilled if you edit them without Longlines mode.
@node Fill Commands
@subsection Explicit Fill Commands
When a fill prefix is in effect, the fill commands remove the fill
prefix from each line before filling and insert it on each line after
-filling. Auto Fill mode also inserts the fill prefix automatically when
-it makes a new line. The @kbd{C-o} command inserts the fill prefix on
-new lines it creates, when you use it at the beginning of a line
-(@pxref{Blank Lines}). Conversely, the command @kbd{M-^} deletes the
-prefix (if it occurs) after the newline that it deletes
-(@pxref{Indentation}).
+filling. (The beginning of the first line is left unchanged, since
+often that is intentionally different.) Auto Fill mode also inserts
+the fill prefix automatically when it makes a new line. The @kbd{C-o}
+command inserts the fill prefix on new lines it creates, when you use
+it at the beginning of a line (@pxref{Blank Lines}). Conversely, the
+command @kbd{M-^} deletes the prefix (if it occurs) after the newline
+that it deletes (@pxref{Indentation}).
For example, if @code{fill-column} is 40 and you set the fill prefix
to @samp{;; }, then @kbd{M-q} in the following text
automatically by setting the variable @code{adaptive-fill-function} to a
function. This function is called with point after the left margin of a
line, and it should return the appropriate fill prefix based on that
-line. If it returns @code{nil}, that means it sees no fill prefix in
-that line.
+line. If it returns @code{nil}, @code{adaptive-fill-regexp} gets
+a chance to find a prefix.
+
+@node Longlines
+@subsection Long Lines Mode
+@cindex refilling text, word processor style
+@cindex modes, Long Lines
+@cindex word wrap
+@cindex Long Lines minor mode
+
+ Long Lines mode is a minor mode for @dfn{word wrapping}; it lets you
+edit ``unfilled'' text files, which Emacs would normally display as a
+bunch of extremely long lines. Many text editors, such as those built
+into many web browsers, normally do word wrapping.
+
+@findex longlines-mode
+ To enable Long Lines mode, type @kbd{M-x longlines-mode}. If the
+text is full of long lines, this will ``wrap'' them
+immediately---i.e., break up to fit in the window. As you edit the
+text, Long Lines mode automatically re-wraps lines by inserting or
+deleting @dfn{soft newlines} as necessary (@pxref{Hard and Soft
+Newlines}.) These soft newlines won't show up when you save the
+buffer into a file, or when you copy the text into the kill ring,
+clipboard, or a register.
+
+@findex longlines-auto-wrap
+ Word wrapping is @emph{not} the same as ordinary filling
+(@pxref{Fill Commands}). It does not contract multiple spaces into a
+single space, recognize fill prefixes (@pxref{Fill Prefix}), or
+perform adaptive filling (@pxref{Adaptive Fill}). The reason for this
+is that a wrapped line is still, conceptually, a single line. Each
+soft newline is equivalent to exactly one space in that long line, and
+vice versa. However, you can still call filling functions such as
+@kbd{M-q}, and these will work as expected, inserting soft newlines
+that won't show up on disk or when the text is copied. You can even
+rely entirely on the normal fill commands by turning off automatic
+line wrapping, with @kbd{C-u M-x longlines-auto-wrap}. To turn
+automatic line wrapping back on, type @kbd{M-x longlines-auto-wrap}.
+
+@findex longlines-show-hard-newlines
+ Whenever you type @kbd{RET}, you are inserting a hard newline. If
+you want to see where all the hard newlines are, type @kbd{M-x
+longlines-show-hard-newlines}. This will mark each hard newline with
+a special symbol. The same command with a prefix argument turns this
+display off.
+
+ Long Lines mode does not change normal text files that are already
+filled, since the existing newlines are considered hard newlines.
+Before Long Lines can do anything, you need to transform each
+paragraph into a long line. One way is to set @code{fill-column} to a
+large number (e.g., @kbd{C-u 9999 C-x f}), re-fill all the paragraphs,
+and then set @code{fill-column} back to its original value.
@node Case
@section Case Conversion Commands
instance during mail composition.
@kindex M-TAB @r{(Text mode)}
- Text mode, and all the modes based on it, define @kbd{M-@key{TAB}} as
-the command @code{ispell-complete-word}, which performs completion of
-the partial word in the buffer before point, using the spelling
-dictionary as the space of possible words. @xref{Spelling}.
+ Text mode, and all the modes based on it, define @kbd{M-@key{TAB}}
+as the command @code{ispell-complete-word}, which performs completion
+of the partial word in the buffer before point, using the spelling
+dictionary as the space of possible words. @xref{Spelling}. If your
+window manager defines @kbd{M-@key{TAB}} to switch windows, you can
+type @kbd{@key{ESC} @key{TAB}} or @kbd{C-M-i}.
@vindex text-mode-hook
Entering Text mode runs the hook @code{text-mode-hook}. Other major
outline-mode} to switch to Outline mode as the major mode of the current
buffer.
- When Outline mode makes a line invisible, the line does not appear on
-the screen. The screen appears exactly as if the invisible line were
-deleted, except that an ellipsis (three periods in a row) appears at the
-end of the previous visible line (only one ellipsis no matter how many
-invisible lines follow).
+ When Outline mode makes a line invisible, the line does not appear
+on the screen. The screen appears exactly as if the invisible line
+were deleted, except that an ellipsis (three periods in a row) appears
+at the end of the previous visible line. (Multiple consecutive
+invisible lines produce just one ellipsis.)
Editing commands that operate on lines, such as @kbd{C-n} and
@kbd{C-p}, treat the text of the invisible line as part of the previous
outlines.
* Visibility: Outline Visibility. Commands to control what is visible.
* Views: Outline Views. Outlines and multiple views.
-* Foldout:: Folding editing.
+* Foldout:: Folding means zooming in on outlines.
@end menu
@node Outline Format
you can undo right past them. Making lines visible or invisible is simply
not recorded by the undo mechanism.
+ Many of these commands act on the ``current'' heading line. If
+point is on a heading line, that is the current heading line; if point
+is on a body line, the current heading line is the nearest preceding
+header line.
+
@table @kbd
-@item C-c C-t
-Make all body lines in the buffer invisible (@code{hide-body}).
-@item C-c C-a
-Make all lines in the buffer visible (@code{show-all}).
+@item C-c C-c
+Make the current heading line's body invisible (@code{hide-entry}).
+@item C-c C-e
+Make the current heading line's body visible (@code{show-entry}).
@item C-c C-d
-Make everything under this heading invisible, not including this
+Make everything under the current heading invisible, not including the
heading itself (@code{hide-subtree}).
@item C-c C-s
-Make everything under this heading visible, including body,
+Make everything under the current heading visible, including body,
subheadings, and their bodies (@code{show-subtree}).
@item C-c C-l
-Make the body of this heading line, and of all its subheadings,
+Make the body of the current heading line, and of all its subheadings,
invisible (@code{hide-leaves}).
@item C-c C-k
-Make all subheadings of this heading line, at all levels, visible
-(@code{show-branches}).
+Make all subheadings of the current heading line, at all levels,
+visible (@code{show-branches}).
@item C-c C-i
-Make immediate subheadings (one level down) of this heading line
-visible (@code{show-children}).
-@item C-c C-c
-Make this heading line's body invisible (@code{hide-entry}).
-@item C-c C-e
-Make this heading line's body visible (@code{show-entry}).
+Make immediate subheadings (one level down) of the current heading
+line visible (@code{show-children}).
+@item C-c C-t
+Make all body lines in the buffer invisible (@code{hide-body}).
+@item C-c C-a
+Make all lines in the buffer visible (@code{show-all}).
@item C-c C-q
Hide everything except the top @var{n} levels of heading lines
(@code{hide-sublevels}).
@kindex C-c C-c @r{(Outline mode)}
@kindex C-c C-e @r{(Outline mode)}
Two commands that are exact opposites are @kbd{C-c C-c}
-(@code{hide-entry}) and @kbd{C-c C-e} (@code{show-entry}). They are
-used with point on a heading line, and apply only to the body lines of
-that heading. Subheadings and their bodies are not affected.
+(@code{hide-entry}) and @kbd{C-c C-e} (@code{show-entry}). They apply
+to the body lines directly following the current heading line.
+Subheadings and their bodies are not affected.
@findex hide-subtree
@findex show-subtree
@kindex C-c C-s @r{(Outline mode)}
@kindex C-c C-d @r{(Outline mode)}
@cindex subtree (Outline mode)
- Two more powerful opposites are @kbd{C-c C-d} (@code{hide-subtree}) and
-@kbd{C-c C-s} (@code{show-subtree}). Both expect to be used when point is
-on a heading line, and both apply to all the lines of that heading's
-@dfn{subtree}: its body, all its subheadings, both direct and indirect, and
-all of their bodies. In other words, the subtree contains everything
-following this heading line, up to and not including the next heading of
-the same or higher rank.@refill
+ Two more powerful opposites are @kbd{C-c C-d} (@code{hide-subtree})
+and @kbd{C-c C-s} (@code{show-subtree}). Both apply to the current
+heading line's @dfn{subtree}: its body, all its subheadings, both
+direct and indirect, and all of their bodies. In other words, the
+subtree contains everything following the current heading line, up to
+and not including the next heading of the same or higher rank.@refill
@findex hide-leaves
@findex show-branches
@kindex C-c C-a @r{(Outline mode)}
Two commands have a blanket effect on the whole file. @kbd{C-c C-t}
(@code{hide-body}) makes all body lines invisible, so that you see just
-the outline structure. @kbd{C-c C-a} (@code{show-all}) makes all lines
-visible. These commands can be thought of as a pair of opposites even
-though @kbd{C-c C-a} applies to more than just body lines.
+the outline structure (as a special exception, it will not hide lines
+at the top of the file, preceding the first header line, even though
+these are technically body lines). @kbd{C-c C-a} (@code{show-all})
+makes all lines visible. These commands can be thought of as a pair
+of opposites even though @kbd{C-c C-a} applies to more than just body
+lines.
@findex hide-sublevels
@kindex C-c C-q @r{(Outline mode)}
@cindex @TeX{} mode
@cindex La@TeX{} mode
@cindex Sli@TeX{} mode
+@cindex Doc@TeX{} mode
@cindex mode, @TeX{}
@cindex mode, La@TeX{}
@cindex mode, Sli@TeX{}
+@cindex mode, Doc@TeX{}
@findex tex-mode
@findex plain-tex-mode
@findex latex-mode
@findex slitex-mode
+@findex doctex-mode
@TeX{} is a powerful text formatter written by Donald Knuth; it is also
free, like GNU Emacs. La@TeX{} is a simplified input format for @TeX{},
implemented by @TeX{} macros; it comes with @TeX{}. Sli@TeX{} is a special
form of La@TeX{}.@footnote{Sli@TeX{} is obsoleted by the @samp{slides}
-document class in recent La@TeX{} versions.}
+document class in recent La@TeX{} versions.} Doc@TeX{} (@file{.dtx})
+is a special file format in which the La@TeX{} sources are written,
+combining sources with documentation.
Emacs has a special @TeX{} mode for editing @TeX{} input files.
It provides facilities for checking the balance of delimiters and for
invoking @TeX{} on all or part of the file.
@vindex tex-default-mode
- @TeX{} mode has three variants, Plain @TeX{} mode, La@TeX{} mode, and
-Sli@TeX{} mode (these three distinct major modes differ only slightly).
-They are designed for editing the three different formats. The command
-@kbd{M-x tex-mode} looks at the contents of the buffer to determine
-whether the contents appear to be either La@TeX{} input or Sli@TeX{}
-input; if so, it selects the appropriate mode. If the file contents do
-not appear to be La@TeX{} or Sli@TeX{}, it selects Plain @TeX{} mode.
-If the contents are insufficient to determine this, the variable
+ @TeX{} mode has four variants: Plain @TeX{} mode, La@TeX{} mode,
+Sli@TeX{} mode, and Doc@TeX{} mode (these distinct major modes differ
+only slightly). They are designed for editing the four different
+formats. The command @kbd{M-x tex-mode} looks at the contents of the
+buffer to determine whether the contents appear to be either La@TeX{}
+input, Sli@TeX{}, or Doc@TeX{} input; if so, it selects the
+appropriate mode. If the file contents do not appear to be La@TeX{},
+Sli@TeX{} or Doc@TeX{}, it selects Plain @TeX{} mode. If the contents
+are insufficient to determine this, the variable
@code{tex-default-mode} controls which mode is used.
When @kbd{M-x tex-mode} does not guess right, you can use the commands
-@kbd{M-x plain-tex-mode}, @kbd{M-x latex-mode}, and @kbd{M-x
-slitex-mode} to select explicitly the particular variants of @TeX{}
-mode.
+@kbd{M-x plain-tex-mode}, @kbd{M-x latex-mode}, @kbd{M-x slitex-mode},
+and @kbd{doctex-mode} to select explicitly the particular variants of
+@TeX{} mode.
@menu
* Editing: TeX Editing. Special commands for editing in TeX mode.
C-f} command (@code{tex-view}).
@item C-c C-q
Show the printer queue (@code{tex-show-print-queue}).
+@item C-c C-c
+Invoke some other compilation command on the entire current buffer
+(@code{tex-compile}).
@end table
@findex tex-buffer
For La@TeX{} files, you can use Bib@TeX{} to process the auxiliary
file for the current buffer's file. Bib@TeX{} looks up bibliographic
citations in a data base and prepares the cited references for the
-bibliography section. The command @kbd{C-c TAB}
+bibliography section. The command @kbd{C-c @key{TAB}}
(@code{tex-bibtex-file}) runs the shell command
(@code{tex-bibtex-command}) to produce a @samp{.bbl} file for the
current buffer's file. Generally, you need to do @kbd{C-c C-f}
(@code{tex-file}) once to generate the @samp{.aux} file, then do
-@kbd{C-c TAB} (@code{tex-bibtex-file}), and then repeat @kbd{C-c C-f}
+@kbd{C-c @key{TAB}} (@code{tex-bibtex-file}), and then repeat @kbd{C-c C-f}
(@code{tex-file}) twice more to get the cross-references correct.
+@findex tex-compile
+@kindex C-c C-c @r{(@TeX{} mode)}
+ To invoke some other compilation program on the current @TeX{}
+buffer, type @kbd{C-c C-c} (@code{tex-compile}). This command knows
+how to pass arguments to many common programs, including
+@file{pdflatex}, @file{yap}, @file{xdvi}, and @file{dvips}. You can
+select your desired compilation program using the standard completion
+keys (@pxref{Completion}).
+
@node TeX Misc
@subsection @TeX{} Mode Miscellany
@cindex soft newline
@cindex newlines, hard and soft
+@cindex use-hard-newlines
In formatted text, Emacs distinguishes between two different kinds of
-newlines, @dfn{hard} newlines and @dfn{soft} newlines.
+newlines, @dfn{hard} newlines and @dfn{soft} newlines. (You can enable
+or disable this feature separately in any buffer with the command
+@code{use-hard-newlines}.)
Hard newlines are used to separate paragraphs, or items in a list, or
anywhere that there should always be a line break regardless of the
with these keyboard commands:
@table @kbd
-@kindex M-g d @r{(Enriched mode)}
+@kindex M-o d @r{(Enriched mode)}
@findex facemenu-set-default
-@item M-g d
+@item M-o d
Set the region, or the next inserted character, to the @code{default} face
(@code{facemenu-set-default}).
-@kindex M-g b @r{(Enriched mode)}
+@kindex M-o b @r{(Enriched mode)}
@findex facemenu-set-bold
-@item M-g b
+@item M-o b
Set the region, or the next inserted character, to the @code{bold} face
(@code{facemenu-set-bold}).
-@kindex M-g i @r{(Enriched mode)}
+@kindex M-o i @r{(Enriched mode)}
@findex facemenu-set-italic
-@item M-g i
+@item M-o i
Set the region, or the next inserted character, to the @code{italic} face
(@code{facemenu-set-italic}).
-@kindex M-g l @r{(Enriched mode)}
+@kindex M-o l @r{(Enriched mode)}
@findex facemenu-set-bold-italic
-@item M-g l
+@item M-o l
Set the region, or the next inserted character, to the @code{bold-italic} face
(@code{facemenu-set-bold-italic}).
-@kindex M-g u @r{(Enriched mode)}
+@kindex M-o u @r{(Enriched mode)}
@findex facemenu-set-underline
-@item M-g u
+@item M-o u
Set the region, or the next inserted character, to the @code{underline} face
(@code{facemenu-set-underline}).
-@kindex M-g o @r{(Enriched mode)}
+@kindex M-o o @r{(Enriched mode)}
@findex facemenu-set-face
-@item M-g o @var{face} @key{RET}
+@item M-o o @var{face} @key{RET}
Set the region, or the next inserted character, to the face @var{face}
(@code{facemenu-set-face}).
@end table
Table Mode allows the contents of the table such as this one to be
easily manipulated by inserting or deleting characters inside a cell.
A cell is effectively a localized rectangular edit region and edits to
-a cell do not affect the contets of the surrounding cells. If the
+a cell do not affect the contents of the surrounding cells. If the
contents do not fit into a cell, then the cell is automatically
expanded in the vertical and/or horizontal directions and the rest of
the table is restructured and reformatted in accordance with the
@item
Nested cells are not allowed.
@item
-Overlapped cells or nonrectangular cells are not allowed.
+Overlapped cells or non-rectangular cells are not allowed.
@item
-The border must be rectanglular.
+The border must be rectangular.
@item
Cells must have a minimum width/height of one character.
@item
used to remove the special text properties and revert the buffer back
to plain text.
- An optional numeric prefix argument can preceed the
+ An optional numeric prefix argument can precede the
@code{table-recognize} command. If the argument is negative, tables
in the buffer become inactive. This is equivalent to invoking
@code{table-unrecognize}.
justification, this command sets the justification only to the current
cell. Selecting column or row justification set the justification to
all the cells within a column or row respectively. The command then
-requsts the user to enter which justification to apply: @code{left},
+requests the user to enter which justification to apply: @code{left},
@code{center}, @code{right}, @code{top}, @code{middle}, @code{bottom},
or @code{none}. The options @code{left}, @code{center}, and
@code{right} specify horizontal justification while the options
convenience feature (turned on by default). During table recognition,
the contents of a cell are examined to determine which justification
was originally applied to the cell and then applies this justification
-to the the cell. This is a speculative algorithm and is therefore not
+to the cell. This is a speculative algorithm and is therefore not
perfect, however, the justification is deduced correctly most of the
time. If you desire to disable this feature, customize the variable
@code{table-detect-cell-alignment} to set it to @code{nil}.
following one.
@c The first line's right-hand frame in the following two examples
-@c sticks out to accomodate for the removal of @samp in the
+@c sticks out to accommodate for the removal of @samp in the
@c produced output!!
@example
+-----------------------------------------------------------------+