.\" Copyright (c) 1980 Regents of the University of California.
.\" All rights reserved. The Berkeley software License Agreement
.\" specifies the terms and conditions for redistribution.
.\" @(#)ex.1 6.4 (Berkeley) %G%
is the root of a family of editors:
with the most notable extension being a display editing facility.
Display based editing is the focus of
or are a casual user, you will find that the editor
It avoids some of the complexities of
used mostly by systems programmers and persons very familiar with
If you have a \s-2CRT\s0 terminal, you may wish to use a display
based editor; in this case
which is a command which focuses on the display editing portion of
(USD:14) provides a comprehensive introduction to
assuming no previous knowledge of computers or the \s-2UNIX\s0 system.
.I "Ex Reference Manual \- Version 3.7"
is a comprehensive and complete manual for the command mode features
but you cannot learn to use the editor by reading it.
more advanced forms of editing using the command mode of
see the editing documents written by Brian Kernighan for the editor
the material in the introductory and advanced documents works also with
.I "An Introduction to Display Editing with Vi"
introduces the display editor
and provides reference material on
card summarizes the commands
in a useful, functional way, and is useful with the
/usr/lib/ex?.?strings error messages
/usr/lib/ex?.?recover recover command
/usr/lib/ex?.?preserve preserve command
/etc/termcap describes capabilities of terminals
~/.exrc editor startup file
/tmp/Ex\fInnnnn\fR editor temporary
/tmp/Rx\fInnnnn\fR named buffer temporary
/usr/preserve preservation directory
awk(1), ed(1), grep(1), sed(1), grep(1), vi(1), termcap(5), environ(7)
Originally written by William Joy
Mark Horton has maintained the editor since version 2.7, adding macros,
support for many unusual terminals,
and other features such as word abbreviation mode.
command causes all marks to be lost on lines changed and then restored
if the marked lines were changed.
never clears the buffer modified condition.
command prints a number of logical rather than physical lines.
More than a screen full of output may result if long lines are present.
File input/output errors don't print a name if the command line \fB`\-'\fR
There is no easy way to do a single scan ignoring case.
The editor does not warn if text is placed in named buffers and not used
before exiting the editor.
Null characters are discarded in input files, and cannot appear in resultant