Mercurial > hg > xemacs-beta
view man/xemacs/basic.texi @ 2367:ecf1ebac70d8
[xemacs-hg @ 2004-11-04 23:05:23 by ben]
commit mega-patch
configure.in: Turn off -Winline and -Wchar-subscripts.
Use the right set of cflags when compiling modules.
Rewrite ldap configuration to separate the inclusion of lber
(needed in recent Cygwin) from the basic checks for the
needed libraries.
add a function for MAKE_JUNK_C; initially code was added to
generate xemacs.def using this, but it will need to be rewritten.
add an rm -f for junk.c to avoid weird Cygwin bug with cp -f onto
an existing file.
Sort list of auto-detected functions and eliminate unused checks for
stpcpy, setlocale and getwd.
Add autodetection of Cygwin scanf problems
BETA: Rewrite section on configure to indicate what flags are important
and what not.
digest-doc.c, make-dump-id.c, profile.c, sorted-doc.c: Add proper decls for main().
make-msgfile.c: Document that this is old junk.
Move proposal to text.c.
make-msgfile.lex: Move proposal to text.c.
make-mswin-unicode.pl: Convert error-generating code so that the entire message will
be seen as a single unrecognized token.
mule/mule-ccl.el: Update docs.
lispref/mule.texi: Update CCL docs.
ldap/eldap.c: Mule-ize.
Use EXTERNAL_LIST_LOOP_2 instead of deleted EXTERNAL_LIST_LOOP.
* XEmacs 21.5.18 "chestnut" is released.
---------------------------------------------------------------
MULE-RELATED WORK:
---------------------------------------------------------------
---------------------------
byte-char conversion
---------------------------
buffer.c, buffer.h, insdel.c, text.c: Port FSF algorithm for byte-char conversion, replacing broken
previous version. Track the char position of the gap. Add
functions to do char-byte conversion downwards as well as upwards.
Move comments about algorithm workings to internals manual.
---------------------------
work on types
---------------------------
alloc.c, console-x-impl.h, dump-data.c, dump-data.h, dumper.c, dialog-msw.c, dired-msw.c, doc.c, editfns.c, esd.c, event-gtk.h, event-msw.c, events.c, file-coding.c, file-coding.h, fns.c, glyphs-eimage.c, glyphs-gtk.c, glyphs-msw.c, glyphs-shared.c, glyphs-x.c, glyphs.c, glyphs.h, gui.c, hpplay.c, imgproc.c, intl-win32.c, lrecord.h, lstream.c, keymap.c, lisp.h, libsst.c, linuxplay.c, miscplay.c, miscplay.h, mule-coding.c, nas.c, nt.c, ntheap.c, ntplay.c, objects-msw.c, objects-tty.c, objects-x.c, print.c, process-nt.c, process.c, redisplay.h, select-common.h, select-gtk.c, select-x.c, sgiplay.c, sound.c, sound.h, sunplay.c, sysfile.h, sysdep.c, syswindows.h, text.c, unexnt.c, win32.c, xgccache.c: Further work on types. This creates a full set of types for all
the basic semantics of `char' that I have so far identified, so that
its semantics can always be identified for the purposes of proper
Mule-safe code, and the raw use of `char' always avoided.
(1) More type renaming, for consistency of naming.
Char_ASCII -> Ascbyte
UChar_ASCII -> UAscbyte
Char_Binary -> CBinbyte
UChar_Binary -> Binbyte
SChar_Binary -> SBinbyte
(2) Introduce Rawbyte, CRawbyte, Boolbyte, Chbyte, UChbyte, and
Bitbyte and use them.
(3) New types Itext, Wexttext and Textcount for separating out
the concepts of bytes and textual units (different under UTF-16
and UTF-32, which are potential internal encodings).
(4) qxestr*_c -> qxestr*_ascii.
lisp.h: New; goes with other qxe() functions. #### Maybe goes in a
different section.
lisp.h: Group generic int-type defs together with EMACS_INT defs.
lisp.h: * lisp.h (WEXTTEXT_IS_WIDE)
New defns.
lisp.h: New type to replace places where int occurs as a boolean.
It's signed because occasionally people may want to use -1 as
an error value, and because unsigned ints are viral -- see comments
in the internals manual against using them.
dynarr.c: int -> Bytecount.
---------------------------
Mule-izing
---------------------------
device-x.c: Partially Mule-ize.
dumper.c, dumper.h: Mule-ize. Use Rawbyte. Use stderr_out not printf. Use wext_*().
sysdep.c, syswindows.h, text.c: New Wexttext API for manipulation of external text that may be
Unicode (e.g. startup code under Windows).
emacs.c: Mule-ize. Properly deal with argv in external encoding.
Use wext_*() and Wexttext. Use Rawbyte.
#if 0 some old junk on SCO that is unlikely to be correct.
Rewrite allocation code in run-temacs.
emacs.c, symsinit.h, win32.c: Rename win32 init function and call it even earlier, to
initialize mswindows_9x_p even earlier, for use in startup code
(XEUNICODE_P).
process.c: Use _wenviron not environ under Windows, to get Unicode environment
variables.
event-Xt.c: Mule-ize drag-n-drop related stuff.
dragdrop.c, dragdrop.h, frame-x.c: Mule-ize.
text.h: Add some more stand-in defines for particular kinds of conversion;
use in Mule-ization work in frame-x.c etc.
---------------------------
Freshening
---------------------------
intl-auto-encap-win32.c, intl-auto-encap-win32.h: Regenerate.
---------------------------
Unicode-work
---------------------------
intl-win32.c, syswindows.h: Factor out common options to MultiByteToWideChar and
WideCharToMultiByte. Add convert_unicode_to_multibyte_malloc()
and convert_unicode_to_multibyte_dynarr() and use. Add stuff for
alloca() conversion of multibyte/unicode.
alloc.c: Use dfc_external_data_len() in case of unicode coding system.
alloc.c, mule-charset.c: Don't zero out and reinit charset Unicode tables. This fucks up
dump-time loading. Anyway, either we load them at dump time or
run time, never both.
unicode.c: Dump the blank tables as well.
---------------------------------------------------------------
DOCUMENTATION, MOSTLY MULE-RELATED:
---------------------------------------------------------------
EmacsFrame.c, emodules.c, event-Xt.c, fileio.c, input-method-xlib.c, mule-wnnfns.c, redisplay-gtk.c, redisplay-tty.c, redisplay-x.c, regex.c, sysdep.c: Add comment about Mule work needed.
text.h: Add more documentation describing why DFC routines were not written
to return their value. Add some other DFC documentation.
console-msw.c, console-msw.h: Add pointer to docs in win32.c.
emacs.c: Add comments on sources of doc info.
text.c, charset.h, unicode.c, intl-win32.c, intl-encap-win32.c, text.h, file-coding.c, mule-coding.c: Collect background comments and related to text matters and
internationalization, and proposals for work to be done, in text.c
or Internals manual, stuff related to specific textual API's in
text.h, and stuff related to internal implementation of Unicode
conversion in unicode.c. Put lots of pointers to the comments to
make them easier to find.
s/mingw32.h, s/win32-common.h, s/win32-native.h, s/windowsnt.h, win32.c: Add bunches of new documentation on the different kinds of
builds and environments under Windows and how they work.
Collect this info in win32.c. Add pointers to these docs in
the relevant s/* files.
emacs.c: Document places with long comments.
Remove comment about exiting, move to internals manual, put
in pointer.
event-stream.c: Move docs about event queues and focus to internals manual, put
in pointer.
events.h: Move docs about event stream callbacks to internals manual, put
in pointer.
profile.c, redisplay.c, signal.c: Move documentation to the Internals manual.
process-nt.c: Add pointer to comment in win32-native.el.
lisp.h: Add comments about some comment conventions.
lisp.h: Add comment about the second argument.
device-msw.c, redisplay-msw.c: @@#### comments are out-of-date.
---------------------------------------------------------------
PDUMP WORK (MOTIVATED BY UNICODE CHANGES)
---------------------------------------------------------------
alloc.c, buffer.c, bytecode.c, console-impl.h, console.c, device.c, dumper.c, lrecord.h, elhash.c, emodules.h, events.c, extents.c, frame.c, glyphs.c, glyphs.h, mule-charset.c, mule-coding.c, objects.c, profile.c, rangetab.c, redisplay.c, specifier.c, specifier.h, window.c, lstream.c, file-coding.h, file-coding.c: PDUMP:
Properly implement dump_add_root_block(), which never worked before,
and is necessary for dumping Unicode tables.
Pdump name changes for accuracy:
XD_STRUCT_PTR -> XD_BLOCK_PTR.
XD_STRUCT_ARRAY -> XD_BLOCK_ARRAY.
XD_C_STRING -> XD_ASCII_STRING.
*_structure_* -> *_block_*.
lrecord.h: some comments added about
dump_add_root_block() vs dump_add_root_block_ptr().
extents.c: remove incorrect comment about pdump problems with gap array.
---------------------------------------------------------------
ALLOCATION
---------------------------------------------------------------
abbrev.c, alloc.c, bytecode.c, casefiddle.c, device-msw.c, device-x.c, dired-msw.c, doc.c, doprnt.c, dragdrop.c, editfns.c, emodules.c, file-coding.c, fileio.c, filelock.c, fns.c, glyphs-eimage.c, glyphs-gtk.c, glyphs-msw.c, glyphs-x.c, gui-msw.c, gui-x.c, imgproc.c, intl-win32.c, lread.c, menubar-gtk.c, menubar.c, nt.c, objects-msw.c, objects-x.c, print.c, process-nt.c, process-unix.c, process.c, realpath.c, redisplay.c, search.c, select-common.c, symbols.c, sysdep.c, syswindows.h, text.c, text.h, ui-byhand.c: New macros {alloca,xnew}_{itext,{i,ext,raw,bin,asc}bytes} for
more convenient allocation of these commonly requested items.
Modify functions to use alloca_ibytes, alloca_array, alloca_extbytes,
xnew_ibytes, etc. also XREALLOC_ARRAY, xnew.
alloc.c: Rewrite the allocation functions to factor out repeated code.
Add assertions for freeing dumped data.
lisp.h: Moved down and consolidated with other allocation stuff.
lisp.h, dynarr.c: New functions for allocation that's very efficient when mostly in
LIFO order.
lisp.h, text.c, text.h: Factor out some stuff for general use by alloca()-conversion funs.
text.h, lisp.h: Fill out convenience routines for allocating various kinds of
bytes and put them in lisp.h. Use them in place of xmalloc(),
ALLOCA().
text.h: Fill out the convenience functions so the _MALLOC() kinds match
the alloca() kinds.
---------------------------------------------------------------
ERROR-CHECKING
---------------------------------------------------------------
text.h: Create ASSERT_ASCTEXT_ASCII() and ASSERT_ASCTEXT_ASCII_LEN()
from similar Eistring checkers and change the Eistring checkers to
use them instead.
---------------------------------------------------------------
MACROS IN LISP.H
---------------------------------------------------------------
lisp.h: Redo GCPRO declarations. Create a "base" set of functions that can
be used to generate any kind of gcpro sets -- regular, ngcpro,
nngcpro, private ones used in GC_EXTERNAL_LIST_LOOP_2.
buffer.c, callint.c, chartab.c, console-msw.c, device-x.c, dialog-msw.c, dired.c, extents.c, ui-gtk.c, rangetab.c, nt.c, mule-coding.c, minibuf.c, menubar-msw.c, menubar.c, menubar-gtk.c, lread.c, lisp.h, gutter.c, glyphs.c, glyphs-widget.c, fns.c, fileio.c, file-coding.c, specifier.c: Eliminate EXTERNAL_LIST_LOOP, which does not check for circularities.
Use EXTERNAL_LIST_LOOP_2 instead or EXTERNAL_LIST_LOOP_3
or EXTERNAL_PROPERTY_LIST_LOOP_3 or GC_EXTERNAL_LIST_LOOP_2
(new macro). Removed/redid comments on EXTERNAL_LIST_LOOP.
---------------------------------------------------------------
SPACING FIXES
---------------------------------------------------------------
callint.c, hftctl.c, number-gmp.c, process-unix.c: Spacing fixes.
---------------------------------------------------------------
FIX FOR GEOMETRY PROBLEM IN FIRST FRAME
---------------------------------------------------------------
unicode.c: Add workaround for newlib bug in sscanf() [should be fixed by
release 1.5.12 of Cygwin].
toolbar.c: bug fix for problem of initial frame being 77 chars wide on Windows.
will be overridden by my other ws.
---------------------------------------------------------------
FIX FOR LEAKING PROCESS HANDLES:
---------------------------------------------------------------
process-nt.c: Fixes for leaking handles. Inspired by work done by Adrian Aichner
<adrian@xemacs.org>.
---------------------------------------------------------------
FIX FOR CYGWIN BUG (Unicode-related):
---------------------------------------------------------------
unicode.c: Add workaround for newlib bug in sscanf() [should be fixed by
release 1.5.12 of Cygwin].
---------------------------------------------------------------
WARNING FIXES:
---------------------------------------------------------------
console-stream.c: `reinit' is unused.
compiler.h, event-msw.c, frame-msw.c, intl-encap-win32.c, text.h: Add stuff to deal with ANSI-aliasing warnings I got.
regex.c: Gather includes together to avoid warning.
---------------------------------------------------------------
CHANGES TO INITIALIZATION ROUTINES:
---------------------------------------------------------------
buffer.c, emacs.c, console.c, debug.c, device-x.c, device.c, dragdrop.c, emodules.c, eval.c, event-Xt.c, event-gtk.c, event-msw.c, event-stream.c, event-tty.c, events.c, extents.c, faces.c, file-coding.c, fileio.c, font-lock.c, frame-msw.c, glyphs-widget.c, glyphs.c, gui-x.c, insdel.c, lread.c, lstream.c, menubar-gtk.c, menubar-x.c, minibuf.c, mule-wnnfns.c, objects-msw.c, objects.c, print.c, scrollbar-x.c, search.c, select-x.c, text.c, undo.c, unicode.c, window.c, symsinit.h: Call reinit_*() functions directly from emacs.c, for clarity.
Factor out some redundant init code. Move disallowed stuff
that had crept into vars_of_glyphs() into complex_vars_of_glyphs().
Call init_eval_semi_early() from eval.c not in the middle of
vars_of_() in emacs.c since there should be no order dependency
in the latter calls.
---------------------------------------------------------------
ARMAGEDDON:
---------------------------------------------------------------
alloc.c, emacs.c, lisp.h, print.c: Rename inhibit_non_essential_printing_operations to
inhibit_non_essential_conversion_operations.
text.c: Assert on !inhibit_non_essential_conversion_operations.
console-msw.c, print.c: Don't do conversion in SetConsoleTitle or FindWindow to avoid
problems during armageddon. Put #errors for NON_ASCII_INTERNAL_FORMAT
in places where problems would arise.
---------------------------------------------------------------
CHANGES TO THE BUILD PROCEDURE:
---------------------------------------------------------------
config.h.in, s/cxux.h, s/usg5-4-2.h, m/powerpc.h: Add comment about correct ordering of this file.
Rearrange everything to follow this -- put all #undefs together
and before the s&m files. Add undefs for HAVE_ALLOCA, C_ALLOCA,
BROKEN_ALLOCA_IN_FUNCTION_CALLS, STACK_DIRECTION. Remove unused
HAVE_STPCPY, HAVE_GETWD, HAVE_SETLOCALE.
m/gec63.h: Deleted; totally broken, not used at all, not in FSF.
m/7300.h, m/acorn.h, m/alliant-2800.h, m/alliant.h, m/altos.h, m/amdahl.h, m/apollo.h, m/att3b.h, m/aviion.h, m/celerity.h, m/clipper.h, m/cnvrgnt.h, m/convex.h, m/cydra5.h, m/delta.h, m/delta88k.h, m/dpx2.h, m/elxsi.h, m/ews4800r.h, m/gould.h, m/hp300bsd.h, m/hp800.h, m/hp9000s300.h, m/i860.h, m/ibmps2-aix.h, m/ibmrs6000.h, m/ibmrt-aix.h, m/ibmrt.h, m/intel386.h, m/iris4d.h, m/iris5d.h, m/iris6d.h, m/irist.h, m/isi-ov.h, m/luna88k.h, m/m68k.h, m/masscomp.h, m/mg1.h, m/mips-nec.h, m/mips-siemens.h, m/mips.h, m/news.h, m/nh3000.h, m/nh4000.h, m/ns32000.h, m/orion105.h, m/pfa50.h, m/plexus.h, m/pmax.h, m/powerpc.h, m/pyrmips.h, m/sequent-ptx.h, m/sequent.h, m/sgi-challenge.h, m/symmetry.h, m/tad68k.h, m/tahoe.h, m/targon31.h, m/tekxd88.h, m/template.h, m/tower32.h, m/tower32v3.h, m/ustation.h, m/vax.h, m/wicat.h, m/xps100.h: Delete C_ALLOCA, HAVE_ALLOCA, STACK_DIRECTION,
BROKEN_ALLOCA_IN_FUNCTION_CALLS. All of this is auto-detected.
When in doubt, I followed recent FSF sources, which also have
these things deleted.
author | ben |
---|---|
date | Thu, 04 Nov 2004 23:08:28 +0000 |
parents | 576fb035e263 |
children |
line wrap: on
line source
@c This is part of the XEmacs manual. @c Copyright (C) 1985, 86, 87, 93, 94, 95, 1997 Free Software Foundation, Inc. @c See file xemacs.texi for copying conditions. @node Basic, Undo, Packages, Top @chapter Basic Editing Commands @kindex C-h t @findex help-with-tutorial We now give the basics of how to enter text, make corrections, and save the text in a file. If this material is new to you, you might learn it more easily by running the Emacs learn-by-doing tutorial. To use the tutorial, run Emacs and type @kbd{Control-h t} (@code{help-with-tutorial}). You can also use @b{Tutorials} item from the @b{Help} menu. XEmacs comes with many translations of tutorial. If your XEmacs is with MULE and you set up language environment correctly, XEmacs chooses right tutorial when available (@pxref{Language Environments}). If you want specific translation, give @kbd{C-h t} a prefix argument, like @kbd{C-u C-h t}. To clear the screen and redisplay, type @kbd{C-l} (@code{recenter}). @menu * Inserting Text:: Inserting text by simply typing it. * Moving Point:: How to move the cursor to the place where you want to change something. * Erasing:: Deleting and killing text. * Files: Basic Files. Visiting, creating, and saving files. * Help: Basic Help. Asking what a character does. * Blank Lines:: Commands to make or delete blank lines. * Continuation Lines:: Lines too wide for the screen. * Position Info:: What page, line, row, or column is point on? * Arguments:: Numeric arguments for repeating a command. @c * Repeating:: A short-cut for repeating the previous command. @end menu @node Inserting Text, Moving Point, , Basic @section Inserting Text @cindex insertion @cindex point @cindex cursor @cindex graphic characters To insert printing characters into the text you are editing, just type them. This inserts the characters you type into the buffer at the cursor (that is, at @dfn{point}; @pxref{Point}). The cursor moves forward, and any text after the cursor moves forward too. If the text in the buffer is @samp{FOOBAR}, with the cursor before the @samp{B}, then if you type @kbd{XX}, you get @samp{FOOXXBAR}, with the cursor still before the @samp{B}. @kindex BS @cindex deletion To @dfn{delete} text you have just inserted, use @key{BS}. @key{BS} deletes the character @emph{before} the cursor (not the one that the cursor is on top of or under; that is the character @var{after} the cursor). The cursor and all characters after it move backwards. Therefore, if you type a printing character and then type @key{BS}, they cancel out. @kindex RET @cindex newline To end a line and start typing a new one, type @key{RET}. This inserts a newline character in the buffer. If point is in the middle of a line, @key{RET} splits the line. Typing @key{DEL} when the cursor is at the beginning of a line deletes the preceding newline, thus joining the line with the preceding line. Emacs can split lines automatically when they become too long, if you turn on a special minor mode called @dfn{Auto Fill} mode. @xref{Filling}, for how to use Auto Fill mode. If you prefer to have text characters replace (overwrite) existing text rather than shove it to the right, you can enable Overwrite mode, a minor mode. @xref{Minor Modes}. @cindex quoting @kindex C-q @findex quoted-insert Direct insertion works for printing characters and @key{SPC}, but other characters act as editing commands and do not insert themselves. If you need to insert a control character or a character whose code is above 200 octal, you must @dfn{quote} it by typing the character @kbd{Control-q} (@code{quoted-insert}) first. (This character's name is normally written @kbd{C-q} for short.) There are two ways to use @kbd{C-q}: @itemize @bullet @item @kbd{C-q} followed by any non-graphic character (even @kbd{C-g}) inserts that character. @item @kbd{C-q} followed by a sequence of octal digits inserts the character with the specified octal character code. You can use any number of octal digits; any non-digit terminates the sequence. If the terminating character is @key{RET}, it serves only to terminate the sequence; any other non-digit is itself used as input after terminating the sequence. (The use of octal sequences is disabled in ordinary non-binary Overwrite mode, to give you a convenient way to insert a digit instead of overwriting with it.) @end itemize @noindent A numeric argument to @kbd{C-q} specifies how many copies of the quoted character should be inserted (@pxref{Arguments}). @findex backward-or-forward-delete-char @findex newline @findex self-insert Customization information: @key{DEL}, in most modes, runs the command @code{backward-or-forward-delete-char}; @key{RET} runs the command @code{newline}, and self-inserting printing characters run the command @code{self-insert}, which inserts whatever character was typed to invoke it. Some major modes rebind @key{DEL} to other commands. @node Moving Point, Erasing, Inserting Text, Basic @section Changing the Location of Point @cindex arrow keys @kindex LEFT @kindex RIGHT @kindex UP @kindex DOWN @cindex moving point @cindex movement @cindex cursor motion @cindex moving the cursor To do more than insert characters, you have to know how to move point (@pxref{Point}). The simplest way to do this is with arrow keys, or by clicking the left mouse button where you want to move to. NOTE: Many of the following commands have two versions, one that uses the function keys (e.g. @key{LEFT} or @key{END}) and one that doesn't. The former versions may only be available on X terminals (i.e. not on TTY's), but the latter are available on all terminals. @kindex C-a @kindex C-e @kindex C-f @kindex C-b @kindex C-n @kindex C-p @kindex C-l @kindex C-t @kindex C-v @kindex M-v @kindex M-> @kindex M-< @kindex M-r @kindex LEFT @kindex RIGHT @kindex UP @kindex DOWN @kindex HOME @kindex END @kindex PGUP @kindex PGDN @kindex C-LEFT @kindex C-RIGHT @kindex C-HOME @kindex C-END @findex beginning-of-line @findex end-of-line @findex forward-char @findex backward-char @findex next-line @findex previous-line @findex recenter @findex transpose-chars @findex beginning-of-buffer @findex end-of-buffer @findex goto-char @findex goto-line @findex move-to-window-line @table @kbd @item C-a @itemx HOME Move to the beginning of the line (@code{beginning-of-line}). @item C-e @itemx END Move to the end of the line (@code{end-of-line}). @item C-f @itemx RIGHT Move forward one character (@code{forward-char}). @item C-b @itemx LEFT Move backward one character (@code{backward-char}). @item M-f @itemx C-RIGHT Move forward one word (@code{forward-word}). @item M-b @itemx C-LEFT Move backward one word (@code{backward-word}). @item C-n @itemx DOWN Move down one line, vertically (@code{next-line}). This command attempts to keep the horizontal position unchanged, so if you start in the middle of one line, you end in the middle of the next. When on the last line of text, @kbd{C-n} creates a new line and moves onto it. @item C-p @itemx UP Move up one line, vertically (@code{previous-line}). @item C-v @itemx PGDN Move down one page, vertically (@code{scroll-up}). @item M-v @itemx PGUP Move up one page, vertically (@code{scroll-down}). @item C-l Clear the frame and reprint everything (@code{recenter}). Text moves on the frame to bring point to the center of the window. @item M-r Move point to left margin, vertically centered in the window (@code{move-to-window-line}). Text does not move on the screen. A numeric argument says which screen line to place point on. It counts screen lines down from the top of the window (zero for the top line). A negative argument counts lines from the bottom (@minus{}1 for the bottom line). @item C-t Transpose two characters, the ones before and after the cursor (@code{transpose-chars}). @item M-< @itemx C-HOME Move to the top of the buffer (@code{beginning-of-buffer}). With numeric argument @var{n}, move to @var{n}/10 of the way from the top. @xref{Arguments}, for more information on numeric arguments.@refill @item M-> @itemx C-END Move to the end of the buffer (@code{end-of-buffer}). @item M-x goto-char Read a number @var{n} and move point to buffer position @var{n}. Position 1 is the beginning of the buffer. @item M-g Read a number @var{n} and move point to line number @var{n} (@code{goto-line}). Line 1 is the beginning of the buffer. @c @item C-x C-n @item M-x set-goal-column @findex set-goal-column Use the current column of point as the @dfn{semi-permanent goal column} for @kbd{C-n} and @kbd{C-p} (@code{set-goal-column}). Henceforth, those commands always move to this column in each line moved into, or as close as possible given the contents of the line. This goal column remains in effect until canceled. @c @item C-u C-x C-n @item C-u M-x set-goal-column Cancel the goal column. Henceforth, @kbd{C-n} and @kbd{C-p} once again try to avoid changing the horizontal position, as usual. @end table @vindex track-eol If you set the variable @code{track-eol} to a non-@code{nil} value, then @kbd{C-n} and @kbd{C-p} when at the end of the starting line move to the end of another line. Normally, @code{track-eol} is @code{nil}. @xref{Variables}, for how to set variables such as @code{track-eol}. @vindex next-line-add-newlines Normally, @kbd{C-n} on the last line of a buffer appends a newline to it. If the variable @code{next-line-add-newlines} is @code{nil}, then @kbd{C-n} gets an error instead (like @kbd{C-p} on the first line). @node Erasing, Basic Files, Moving Point, Basic @section Erasing Text @table @kbd @item @key{DEL} Delete the character before or after point (@code{backward-or-forward-delete-char}). You can customize this behavior by setting the variable @code{delete-key-deletes-forward}. @item C-d Delete the character after point (@code{delete-char}). @item C-k Kill to the end of the line (@code{kill-line}). @item M-d Kill forward to the end of the next word (@code{kill-word}). @item M-@key{DEL} Kill back to the beginning of the previous word (@code{backward-kill-word}). @end table @cindex killing characters and lines @cindex deleting characters and lines @cindex erasing characters and lines You already know about the @key{DEL} key which deletes the character before point (that is, before the cursor). Another key, @kbd{Control-d} (@kbd{C-d} for short), deletes the character after point (that is, the character that the cursor is on). This shifts the rest of the text on the line to the left. If you type @kbd{C-d} at the end of a line, it joins together that line and the next line. To erase a larger amount of text, use the @kbd{C-k} key, which kills a line at a time. If you type @kbd{C-k} at the beginning or middle of a line, it kills all the text up to the end of the line. If you type @kbd{C-k} at the end of a line, it joins that line and the next line. @xref{Killing}, for more flexible ways of killing text. @node Basic Files, Basic Help, Erasing, Basic @section Files @cindex files The commands described above are sufficient for creating and altering text in an Emacs buffer; the more advanced Emacs commands just make things easier. But to keep any text permanently you must put it in a @dfn{file}. Files are named units of text which are stored by the operating system for you to retrieve later by name. To look at or use the contents of a file in any way, including editing the file with Emacs, you must specify the file name. Consider a file named @file{/usr/rms/foo.c}. To begin editing this file from Emacs, type: @example C-x C-f /usr/rms/foo.c @key{RET} @end example @noindent Here the file name is given as an @dfn{argument} to the command @kbd{C-x C-f} (@code{find-file}). That command uses the @dfn{minibuffer} to read the argument, and you type @key{RET} to terminate the argument (@pxref{Minibuffer}). You can also use the @b{Open...} menu item from the @b{File} menu, then type the name of the file to the prompt. Emacs obeys the command by @dfn{visiting} the file: creating a buffer, copying the contents of the file into the buffer, and then displaying the buffer for you to edit. If you alter the text, you can @dfn{save} the new text in the file by typing @kbd{C-x C-s} (@code{save-buffer}) or choosing @b{Save Buffer} from the @b{File} menu. This makes the changes permanent by copying the altered buffer contents back into the file @file{/usr/rms/foo.c}. Until you save, the changes exist only inside Emacs, and the file @file{foo.c} is unaltered. To create a file, visit the file with @kbd{C-x C-f} as if it already existed or choose @b{Open...} from the @b{File} menu and provide the name for the new file. Emacs will create an empty buffer in which you can insert the text you want to put in the file. When you save the buffer with @kbd{C-x C-s}, or by choosing @b{Save Buffer} from the @b{File} menu, the file is created. To learn more about using files, @xref{Files}. @node Basic Help, Blank Lines, Basic Files, Basic @section Help @cindex getting help with keys If you forget what a key does, you can find out with the Help character, which is @kbd{C-h} (or @key{F1}, which is an alias for @kbd{C-h}). Type @kbd{C-h k} followed by the key you want to know about; for example, @kbd{C-h k C-n} tells you all about what @kbd{C-n} does. @kbd{C-h} is a prefix key; @kbd{C-h k} is just one of its subcommands (the command @code{describe-key}). The other subcommands of @kbd{C-h} provide different kinds of help. Type @kbd{C-h} twice to get a description of all the help facilities. @xref{Help}. @node Blank Lines, Continuation Lines, Basic Help, Basic @section Blank Lines @cindex inserting blank lines @cindex deleting blank lines Here are special commands and techniques for putting in and taking out blank lines. @c widecommands @table @kbd @item C-o Insert one or more blank lines after the cursor (@code{open-line}). @item C-x C-o Delete all but one of many consecutive blank lines (@code{delete-blank-lines}). @end table @kindex C-o @kindex C-x C-o @cindex blank lines @findex open-line @findex delete-blank-lines When you want to insert a new line of text before an existing line, you can do it by typing the new line of text, followed by @key{RET}. However, it may be easier to see what you are doing if you first make a blank line and then insert the desired text into it. This is easy to do using the key @kbd{C-o} (@code{open-line}), which inserts a newline after point but leaves point in front of the newline. After @kbd{C-o}, type the text for the new line. @kbd{C-o F O O} has the same effect as @w{@kbd{F O O @key{RET}}}, except for the final location of point. You can make several blank lines by typing @kbd{C-o} several times, or by giving it a numeric argument to tell it how many blank lines to make. @xref{Arguments}, for how. If you have a fill prefix, then @kbd{C-o} command inserts the fill prefix on the new line, when you use it at the beginning of a line. @xref{Fill Prefix}. The easy way to get rid of extra blank lines is with the command @kbd{C-x C-o} (@code{delete-blank-lines}). @kbd{C-x C-o} in a run of several blank lines deletes all but one of them. @kbd{C-x C-o} on a solitary blank line deletes that blank line. When point is on a nonblank line, @kbd{C-x C-o} deletes any blank lines following that nonblank line. @node Continuation Lines, Position Info, Blank Lines, Basic @section Continuation Lines @cindex continuation line @cindex wrapping @cindex line wrapping If you add too many characters to one line without breaking it with @key{RET}, the line will grow to occupy two (or more) lines on the screen, with a curved arrow at the extreme right margin of all but the last of them. The curved arrow says that the following screen line is not really a distinct line in the text, but just the @dfn{continuation} of a line too long to fit the screen. Continuation is also called @dfn{line wrapping}. Sometimes it is nice to have Emacs insert newlines automatically when a line gets too long. Continuation on the screen does not do that. Use Auto Fill mode (@pxref{Filling}) if that's what you want. @vindex truncate-lines @cindex truncation Instead of continuation, long lines can be displayed by @dfn{truncation}. This means that all the characters that do not fit in the width of the frame or window do not appear at all. They remain in the buffer, temporarily invisible. Right arrow in the last column (instead of the curved arrow) inform you that truncation is in effect. Truncation instead of continuation happens whenever horizontal scrolling is in use, and optionally in all side-by-side windows (@pxref{Windows}). You can enable truncation for a particular buffer by setting the variable @code{truncate-lines} to non-@code{nil} in that buffer. (@xref{Variables}.) Altering the value of @code{truncate-lines} makes it local to the current buffer; until that time, the default value is in effect. The default is initially @code{nil}. @xref{Locals}. @xref{Display Vars}, for additional variables that affect how text is displayed. @node Position Info, Arguments, Continuation Lines, Basic @section Cursor Position Information If you are accustomed to other display editors, you may be surprised that Emacs does not always display the page number or line number of point in the mode line. In Emacs, this information is only rarely needed, and a number of commands are available to compute and print it. Since text is stored in a way that makes it difficult to compute the information, it is not displayed all the time. @table @kbd @item M-x what-page Print page number of point, and line number within page. @item M-x what-line Print line number of point in the buffer. @item M-x line-number-mode Toggle automatic display of current line number. @item M-= Print number of lines and characters in the current region (@code{count-lines-region}). @xref{Mark}, for information about the region. @item C-x = Print character code of character after point, character position of point, and column of point (@code{what-cursor-position}). @end table @findex what-page @findex what-line @cindex line number @cindex page number @kindex M-= @findex count-lines-region There are several commands for printing line numbers: @itemize @bullet @item @kbd{M-x what-line} counts lines from the beginning of the file and prints the line number point is on. The first line of the file is line number 1. You can use these numbers as arguments to @kbd{M-x goto-line}. @item @kbd{M-x what-page} counts pages from the beginning of the file, and counts lines within the page, printing both of them. @xref{Pages}, for the command @kbd{C-x l}, which counts the lines in the current page. @item @kbd{M-=} (@code{count-lines-region}) prints the number of lines in the region (@pxref{Mark}). @xref{Pages}, for the command @kbd{C-x l} which counts the lines in the @end itemize @kindex C-x = @findex what-cursor-position The command @kbd{C-x =} (@code{what-cursor-position}) can be used to find out the column that the cursor is in, and other miscellaneous information about point. It prints a line in the echo area that looks like this: @example Char: c (0143, 99, 0x63) point=18862 of 24800(76%) column 53 @end example @noindent (In fact, this is the output produced when point is before @samp{column 53} in the example.) The four values after @samp{Char:} describe the character that follows point, first by showing it and then by giving its character code in octal, decimal and hex. @samp{point=} is followed by the position of point expressed as a character count. The front of the buffer counts as position 1, one character later as 2, and so on. The next, larger number is the total number of characters in the buffer. Afterward in parentheses comes the position expressed as a percentage of the total size. @samp{column} is followed by the horizontal position of point, in columns from the left edge of the window. If the buffer has been narrowed, making some of the text at the beginning and the end temporarily invisible, @kbd{C-x =} prints additional text describing the current visible range. For example, it might say: @smallexample Char: c (0143, 99, 0x63) point=19674 of 24575(80%) <19591 - 19703> column 69 @end smallexample @noindent where the two extra numbers give the smallest and largest character position that point is allowed to assume. The characters between those two positions are the visible ones. @xref{Narrowing}. If point is at the end of the buffer (or the end of the visible part), @kbd{C-x =} omits any description of the character after point. The output looks like @smallexample point=563026 of 563025(100%) column 0 @end smallexample @node Arguments,, Position Info, Basic @section Numeric Arguments @cindex numeric arguments In mathematics and computer usage, the word @dfn{argument} means ``data provided to a function or operation.'' Any Emacs command can be given a @dfn{numeric argument} (also called a @dfn{prefix argument}). Some commands interpret the argument as a repetition count. For example, giving an argument of ten to the key @kbd{C-f} (the command @code{forward-char}, move forward one character) moves forward ten characters. With these commands, no argument is equivalent to an argument of one. Negative arguments are allowed. Often they tell a command to move or act in the opposite direction. @kindex M-1 @kindex M-@t{-} @findex digit-argument @findex negative-argument If your keyboard has a @key{META} key (labelled with a diamond on Sun-type keyboards and labelled @samp{Alt} on some other keyboards), the easiest way to specify a numeric argument is to type digits and/or a minus sign while holding down the @key{META} key. For example, @example M-5 C-n @end example @noindent would move down five lines. The characters @kbd{Meta-1}, @kbd{Meta-2}, and so on, as well as @kbd{Meta--}, do this because they are keys bound to commands (@code{digit-argument} and @code{negative-argument}) that are defined to contribute to an argument for the next command. Digits and @kbd{-} modified with Control, or Control and Meta, also specify numeric arguments. @kindex C-u @findex universal-argument Another way of specifying an argument is to use the @kbd{C-u} (@code{universal-argument}) command followed by the digits of the argument. With @kbd{C-u}, you can type the argument digits without holding down modifier keys; @kbd{C-u} works on all terminals. To type a negative argument, type a minus sign after @kbd{C-u}. Just a minus sign without digits normally means @minus{}1. @kbd{C-u} followed by a character which is neither a digit nor a minus sign has the special meaning of ``multiply by four''. It multiplies the argument for the next command by four. @kbd{C-u} twice multiplies it by sixteen. Thus, @kbd{C-u C-u C-f} moves forward sixteen characters. This is a good way to move forward ``fast'', since it moves about 1/5 of a line in the usual size frame. Other useful combinations are @kbd{C-u C-n}, @kbd{C-u C-u C-n} (move down a good fraction of a frame), @kbd{C-u C-u C-o} (make ``a lot'' of blank lines), and @kbd{C-u C-k} (kill four lines). Some commands care only about whether there is an argument and not about its value. For example, the command @kbd{M-q} (@code{fill-paragraph}) with no argument fills text; with an argument, it justifies the text as well. (@xref{Filling}, for more information on @kbd{M-q}.) Just @kbd{C-u} is a handy way of providing an argument for such commands. Some commands use the value of the argument as a repeat count, but do something peculiar when there is no argument. For example, the command @kbd{C-k} (@code{kill-line}) with argument @var{n} kills @var{n} lines, including their terminating newlines. But @kbd{C-k} with no argument is special: it kills the text up to the next newline, or, if point is right at the end of the line, it kills the newline itself. Thus, two @kbd{C-k} commands with no arguments can kill a non-blank line, just like @kbd{C-k} with an argument of one. (@xref{Killing}, for more information on @kbd{C-k}.) A few commands treat a plain @kbd{C-u} differently from an ordinary argument. A few others may treat an argument of just a minus sign differently from an argument of @minus{}1. These unusual cases are described when they come up; they are always for reasons of convenience of use of the individual command. You can use a numeric argument to insert multiple copies of a character. This is straightforward unless the character is a digit; for example, @kbd{C-u 6 4 a} inserts 64 copies of the character @samp{a}. But this does not work for inserting digits; @kbd{C-u 6 4 1} specifies an argument of 641, rather than inserting anything. To separate the digit to insert from the argument, type another @kbd{C-u}; for example, @kbd{C-u 6 4 C-u 1} does insert 64 copies of the character @samp{1}. We use the term ``prefix argument'' as well as ``numeric argument'' to emphasize that you type the argument before the command, and to distinguish these arguments from minibuffer arguments that come after the command. @ignore @node Repeating @section Repeating a Command @cindex repeating a command @kindex C-x z @findex repeat The command @kbd{C-x z} (@code{repeat}) provides another way to repeat an Emacs command many times. This command repeats the previous Emacs command, whatever that was. Repeating a command uses the same arguments that were used before; it does not read new arguments each time. To repeat the command more than once, type additional @kbd{z}'s: each @kbd{z} repeats the command one more time. Repetition ends when you type a character other than @kbd{z}, or press a mouse button. For example, suppose you type @kbd{C-u 2 0 C-d} to delete 20 characters. You can repeat that command (including its argument) three additional times, to delete a total of 80 characters, by typing @kbd{C-x z z z}. The first @kbd{C-x z} repeats the command once, and each subsequent @kbd{z} repeats it once again. @end ignore