Termcap update, replacing elvis by nvi.
Removing elvis, importing nvi, ctags, updating libedit. Change-Id: I881eb04d2dc64cf112facd992de1114e1a59107f
This commit is contained in:
@@ -1,11 +1,11 @@
|
||||
MAN= ash.1 at.1 banner.1 basename.1 \
|
||||
bsfilt.1 cal.1 cawf.1 chgrp.1 \
|
||||
chmod.1 clear.1 cmp.1 comm.1 compress.1 \
|
||||
cp.1 crc.1 crontab.1 ctags.1 dd.1 \
|
||||
cp.1 crc.1 crontab.1 dd.1 \
|
||||
df.1 dhrystone.1 dosdir.1 dosread.1 doswrite.1 \
|
||||
dumpcore.1 echo.1 eject.1 elvis.1 elvrec.1 \
|
||||
dumpcore.1 echo.1 eject.1 \
|
||||
env.1 expand.1 expr.1 factor.1 \
|
||||
finger.1 flexdoc.1 fmt.1 fold.1 format.1 fortune.1 \
|
||||
finger.1 flexdoc.1 fold.1 format.1 fortune.1 \
|
||||
fsck.mfs.1 head.1 host.1 hostaddr.1 ifdef.1 \
|
||||
isodir.1 isoinfo.1 isoread.1 kill.1 \
|
||||
last.1 loadfont.1 loadkeys.1 logger.1 \
|
||||
@@ -14,7 +14,7 @@ MAN= ash.1 at.1 banner.1 basename.1 \
|
||||
mkproto.1 mount.1 mt.1 nice.1 nm.1 nohup.1 od.1 \
|
||||
paste.1 ping.1 playwave.1 pr.1 prep.1 \
|
||||
profile.1 ps.1 pwd.1 rcp.1 recwave.1 \
|
||||
ref.1 remsync.1 rget.1 rlogin.1 rsh.1 rz.1 \
|
||||
remsync.1 rget.1 rlogin.1 rsh.1 rz.1 \
|
||||
shar.1 acksize.1 sleep.1 spell.1 \
|
||||
split.1 stty.1 svc.1 svrctl.1 \
|
||||
synctree.1 sysenv.1 sz.1 tail.1 tee.1 telnet.1 template.1 \
|
||||
@@ -54,7 +54,6 @@ MLINKS += compress.1 uncompress.1
|
||||
MLINKS += cp.1 mv.1
|
||||
MLINKS += cp.1 ln.1
|
||||
MLINKS += cp.1 cpdir.1
|
||||
MLINKS += elvis.1 ex.1
|
||||
MLINKS += expr.1 test.1
|
||||
MLINKS += expr.1 [.1
|
||||
MLINKS += svc.1 ci.1
|
||||
|
||||
@@ -1,84 +0,0 @@
|
||||
.TH CTAGS 1
|
||||
.SH NAME
|
||||
ctags - Generates "tags" and (optionally) "refs" files
|
||||
.SH SYNOPSIS
|
||||
\fBctags\fP [\fB-stvra\fP] \fIfilesnames\fP...
|
||||
.SH DESCRIPTION
|
||||
\fIctags\fP generates the "tags" and "refs" files
|
||||
from a group of C source files.
|
||||
The "tags" file is used by Elvis' ":tag" command,
|
||||
control-] command,
|
||||
and -t option.
|
||||
The "refs" file is sometimes used by the \fIref(1)\fP program.
|
||||
.PP
|
||||
Each C source file is scanned for #define statements and
|
||||
global function definitions.
|
||||
The name of the macro or function becomes the name of a tag.
|
||||
For each tag, a line is added to the "tags" file which contains:
|
||||
.RS
|
||||
.nf
|
||||
- the name of the tag
|
||||
- a tab character
|
||||
- the name of the file containing the tag
|
||||
- a tab character
|
||||
- a way to find the particular line within the file.
|
||||
.RE
|
||||
.fi
|
||||
.PP
|
||||
The filenames list will typically be the names of all C source
|
||||
files in the current directory, like this:
|
||||
.RS
|
||||
.nf
|
||||
$ ctags -stv *.[ch]
|
||||
.RE
|
||||
.fi
|
||||
.SH OPTIONS
|
||||
.IP \fB-t\fR
|
||||
Include typedefs.
|
||||
A tag will be generated for each user-defined type.
|
||||
Also tags will be generated for struct and enum names.
|
||||
Types are considered to be global if they are defined in a header file,
|
||||
and static if they are defined in a C source file.
|
||||
.IP \fB-v\fR
|
||||
Include variable declarations.
|
||||
A tag will be generated for each variable, except for those that are declared
|
||||
inside the body of a function.
|
||||
.IP \fB-s\fR
|
||||
Include static tags.
|
||||
\fICtags\fR will normally put global tags in the "tags" file, and silently ignore
|
||||
the static tags.
|
||||
This flag causes both global and static tags to be added.
|
||||
The name of a static tag is generated by prefixing the name of the declared
|
||||
item with the name of the file where it is defined, with a colon in between.
|
||||
For example, "static foo(){}" in "bar.c" results in a tag named "bar.c:foo".
|
||||
.IP \fB-r\fP
|
||||
This causes \fIctags\fP to generate both "tags" and "refs".
|
||||
Without \fB-r\fP, it would only generate "tags".
|
||||
.IP \fB-a\fR
|
||||
Append to "tags", and maybe "refs".
|
||||
Normally, \fIctags\fR overwrites these files each time it is invoked.
|
||||
This flag is useful when you have to many files in the current directory
|
||||
for you to list them on a single command-line;
|
||||
it allows you to split the arguments among several invocations.
|
||||
.SH FILES
|
||||
.IP tags
|
||||
A cross-reference that lists each tag name, the name of the source file that
|
||||
contains it, and a way to locate a particular line in the source file.
|
||||
.IP refs
|
||||
The "refs" file contains the definitions for each tag in the "tags" file,
|
||||
and very little else.
|
||||
This file can be useful, for example, when licensing restrictions prevent
|
||||
you from making the source code to the standard C library readable by everybody,
|
||||
but you still everybody to know what arguments the library functions need.
|
||||
.SH BUGS
|
||||
.PP
|
||||
\fIctags\fR is sensitive to indenting and line breaks.
|
||||
Consequently, it might not discover all of the tags in a file that
|
||||
is formatted in an unusual way.
|
||||
.SH "SEE ALSO"
|
||||
elvis(1), refs(1)
|
||||
.SH AUTHOR
|
||||
.nf
|
||||
Steve Kirkendall
|
||||
kirkenda@cs.pdx.edu
|
||||
.fi
|
||||
101
man/man1/elvis.1
101
man/man1/elvis.1
@@ -1,101 +0,0 @@
|
||||
.TH ELVIS 1
|
||||
.SH NAME
|
||||
elvis, ex, vi \- The editor
|
||||
.SH SYNOPSIS
|
||||
\fBelvis\fP [\fIflags\fP] [\fB+\fP\fIcmd\fP] [\fIfiles\fP...]
|
||||
.SH DESCRIPTION
|
||||
\fBElvis\fP is a text editor which emulates \fBvi\fP/\fBex\fP.
|
||||
.PP
|
||||
On systems which pass the program name as an argument, such as UNIX and MINIX 3,
|
||||
you may also install \fBelvis\fP under the names "ex", "vi", "view", and "input".
|
||||
These extra names would normally be links to elvis;
|
||||
see the "ln" shell command.
|
||||
.PP
|
||||
When \fBelvis\fP is invoked as "vi",
|
||||
it behaves exactly as though it was invoked as "elvis".
|
||||
However, if you invoke \fBelvis\fP as "view",
|
||||
then the readonly option is set as though you had given it the "-R" flag.
|
||||
If you invoke \fBelvis\fP as "ex",
|
||||
then \fBelvis\fP will start up in the colon command mode
|
||||
instead of the visual command mode,
|
||||
as though you had given it the "-e" flag.
|
||||
If you invoke \fBelvis\fP as "input" or "edit",
|
||||
then \fBelvis\fP will start up in input mode,
|
||||
as though the "-i" flag was given.
|
||||
.SH OPTIONS
|
||||
.IP \fB-r\fP
|
||||
To the real vi, this flag means that a previous edit should be recovered.
|
||||
\fBElvis\fP, though, has a separate program, called \fIelvrec\fP(1), for recovering
|
||||
files.
|
||||
When you invoke \fBelvis\fP with -r, \fBelvis\fP will tell you to run \fBelvrec\fP.
|
||||
.IP \fB-R\fP
|
||||
This sets the "readonly" option,
|
||||
so you won't accidentally overwrite a file.
|
||||
.IP "\fB-t\fP \fItag\fP"
|
||||
This causes \fBelvis\fP to start editing at the given tag.
|
||||
.IP "\fB-m\fP [\fIfile\fP]"
|
||||
\fBElvis\fP will search through \fIfile\fP for something that looks like
|
||||
an error message from a compiler.
|
||||
It will then begin editing the source file that caused the error,
|
||||
with the cursor sitting on the line where the error was detected.
|
||||
If you don't explicitly name a \fIfile\fP, then "errlist" is assumed.
|
||||
.IP \fB-e\fP
|
||||
\fBElvis\fP will start up in colon command mode.
|
||||
.IP \fB-v\fP
|
||||
\fBElvis\fP will start up in visual command mode.
|
||||
.IP \fB-i\fP
|
||||
\fBElvis\fP will start up in input mode.
|
||||
.IP "\fB-w\fR \fIwinsize\fR"
|
||||
Sets the "window" option's value to \fIwinsize\fR.
|
||||
.IP "\fB+\fP\fIcommand\fP or \fB-c\fP \fIcommand\fP"
|
||||
If you use the +\fIcommand\fP parameter,
|
||||
then after the first file is loaded
|
||||
\fIcommand\fP is executed as an EX command.
|
||||
A typical example would be "elvis +237 foo",
|
||||
which would cause \fBelvis\fP to start editing foo and
|
||||
then move directly to line 237.
|
||||
The "-c \fIcommand\fP" variant was added for UNIX SysV compatibility.
|
||||
.SH FILES
|
||||
.IP /tmp/elv*
|
||||
During editing,
|
||||
\fBelvis\fP stores text in a temporary file.
|
||||
For UNIX, this file will usually be stored in the /tmp directory,
|
||||
and the first three characters will be "elv".
|
||||
For other systems, the temporary files may be stored someplace else;
|
||||
see the version-specific section of the documentation.
|
||||
.IP tags
|
||||
This is the database used by the \fB:tags\fP command and the \fB-t\fP option.
|
||||
It is usually created by the \fBctags\fP(1) program.
|
||||
.IP ".exrc or elvis.rc"
|
||||
On UNIX-like systems, a file called ".exrc" in your home directory
|
||||
is executed as a series of \fBex\fR commands.
|
||||
A file by the same name may be executed in the current directory, too.
|
||||
On non-UNIX systems, ".exrc" is usually an invalid file name;
|
||||
there, the initialization file is called "elvis.rc" instead.
|
||||
.SH "SEE ALSO"
|
||||
.BR ctags (1),
|
||||
.BR ref (1),
|
||||
.BR elvrec (1),
|
||||
.BR elvis (1x).
|
||||
.PP
|
||||
\fIElvis - A Clone of Vi/Ex\fP, the complete \fBelvis\fP documentation.
|
||||
.SH BUGS
|
||||
There is no LISP support.
|
||||
Certain other features are missing, too.
|
||||
.PP
|
||||
Auto-indent mode is not quite compatible with the real vi.
|
||||
Among other things, 0^D and ^^D don't do what you might expect.
|
||||
.PP
|
||||
Long lines are displayed differently.
|
||||
The real vi wraps long lines onto multiple rows of the screen,
|
||||
but \fBelvis\fP scrolls sideways.
|
||||
.SH AUTHOR
|
||||
.nf
|
||||
Steve Kirkendall
|
||||
kirkenda@cs.pdx.edu
|
||||
.fi
|
||||
.PP
|
||||
Many other people have worked to port \fBelvis\fP to various operating systems.
|
||||
To see who deserves credit, run the \fB:version\fP command from within \fBelvis\fP,
|
||||
or look in the system-specific section of the complete documentation.
|
||||
.\" ref to virec chnaged to elvrec -- ASW 2004-12-13
|
||||
@@ -1,47 +0,0 @@
|
||||
.TH ELVREC 1
|
||||
.SH NAME
|
||||
elvrec - Recover the modified version of a file after a crash
|
||||
.SH SYNOPSIS
|
||||
.nf
|
||||
\fBelvrec\fP [\fIpreservedfile\fP [\fInewfile\fR]]
|
||||
.fi
|
||||
.SH DESCRIPTION
|
||||
.PP
|
||||
If you're editing a file when \fIelvis\fP dies, the system crashes, or power fails,
|
||||
the most recent version of your text will be preserved.
|
||||
The preserved text is stored in a special directory; it does NOT overwrite
|
||||
your text file automatically.
|
||||
.PP
|
||||
The \fIelvrec\fP program locates the preserved version of a given file,
|
||||
and writes it over the top of your text file -- or to a new file, if you prefer.
|
||||
The recovered file will have nearly all of your changes.
|
||||
.PP
|
||||
To see a list of all recoverable files, run \fIelvrec\fP with no arguments.
|
||||
.SH FILES
|
||||
.IP /usr/preserve/p*
|
||||
The text that was preserved when \fIelvis\fP died.
|
||||
.IP /usr/preserve/Index
|
||||
A text file which lists the names of all preserved files, and the names
|
||||
of the /usr/preserve/p* files which contain their preserved text.
|
||||
.SH BUGS
|
||||
.PP
|
||||
\fIelvrec\fP is very picky about filenames.
|
||||
You must tell it to recover the file using exactly the same pathname as
|
||||
when you were editing it.
|
||||
The simplest way to do this is to go into the same directory that you were
|
||||
editing, and invoke \fIelvrec\fP with the same filename as \fIelvis\fP.
|
||||
If that doesn't work, then try running \fIelvrec\fP with no arguments,
|
||||
to see exactly which pathname it is using for the desired file.
|
||||
.PP
|
||||
Due to the permissions on the /usr/preserve directory, on UNIX systems
|
||||
\fIelvrec\fP must be run as superuser.
|
||||
This is accomplished by making the \fIelvrec\fP executable be owned by "root"
|
||||
and setting its "set user id" bit.
|
||||
.PP
|
||||
If you're editing a nameless buffer when \fIelvis\fP dies, then \fIelvrec\fP
|
||||
will pretend that the file was named "foo".
|
||||
.SH AUTHOR
|
||||
.nf
|
||||
Steve Kirkendall
|
||||
kirkenda@cs.pdx.edu
|
||||
.fi
|
||||
@@ -1,26 +0,0 @@
|
||||
.TH FMT 1
|
||||
.SH NAME
|
||||
fmt - adjust line-length for paragraphs of text
|
||||
.SH SYNOPSIS
|
||||
\fBfmt\fP [\-\fIwidth\fP] [\fIfiles\fP]...
|
||||
.SH DESCRIPTION
|
||||
\fIfmt\fR is a simple text formatter.
|
||||
It inserts or deletes newlines, as necessary, to make all lines in a
|
||||
paragraph be approximately the same width.
|
||||
It preserves indentation and word spacing.
|
||||
.PP
|
||||
The default line width is 72 characters.
|
||||
You can override this with the \-\fIwidth\fR flag.
|
||||
If you don't name any files on the command line,
|
||||
then \fIfmt\fR will read from stdin.
|
||||
.PP
|
||||
It is typically used from within \fIvi\fR to adjust the line breaks
|
||||
in a single paragraph.
|
||||
To do this, move the cursor to the top of the paragraph,
|
||||
type "!}fmt", and
|
||||
hit <Return>.
|
||||
.SH AUTHOR
|
||||
.nf
|
||||
Steve Kirkendall
|
||||
kirkenda@cs.pdx.edu
|
||||
.fi
|
||||
@@ -1,88 +0,0 @@
|
||||
.TH REF 1
|
||||
.SH NAME
|
||||
ref - Display a C function header
|
||||
.SH SYNOPSIS
|
||||
\fBref\fR [-t] [-c \fIclass\fR]... [-f \fIfile\fR]... \fItag\fR
|
||||
.SH DESCRIPTION
|
||||
\fIref\fP quickly locates and displays the header of a function.
|
||||
To do this, \fIref\fR
|
||||
looks in the "tags" file for the line that describes the function, and then
|
||||
scans the source file for the function.
|
||||
When it locates the function, it displays an introductory comment
|
||||
(if there is one), the function's declaration, and the declarations of all
|
||||
arguments.
|
||||
.SH "SEARCH METHOD"
|
||||
.PP
|
||||
\fIref\fR uses a fairly sophisticated tag look-up algorithm.
|
||||
If you supply a filename via \fB-f\fR \fIfile\fR, then elvis first scans
|
||||
the tags file for a static tag from that file.
|
||||
This search is limited to the tags file in the current directory.
|
||||
.PP
|
||||
If you supply a classname via \fB-c\fR \fIclass\fR, then elvis searches
|
||||
for a tag from that class.
|
||||
This search is not limited to the current directory;
|
||||
You can supply a list of directories in the environment variable \fITAGPATH\fR,
|
||||
and \fIref\fR will search through the "tags" file in each directory until it finds
|
||||
a tag in the desired class.
|
||||
.PP
|
||||
If that fails, \fIref\fR will then try to look up an ordinary global tag.
|
||||
This search checks all of the directories listed in \fITAGPATH\fR, too.
|
||||
.PP
|
||||
If you've given the \fB-t\fR flag, then \fIref\fR will simply output the tag line that
|
||||
it found, and then exit.
|
||||
Without \fB-t\fR, though, \fIref\fR will search for the tag line.
|
||||
It will try to open the source file, which should be in the same directory
|
||||
as the tags file where the tag was discovered.
|
||||
If the source file doesn't exist, or is unreadable, then \fIref\fR will try to open
|
||||
a file called "\fIrefs\fR" in that directory.
|
||||
Either way, \fIref\fR will try to locate the tag, and display whatever it finds.
|
||||
.SH "INTERACTION WITH ELVIS"
|
||||
.PP
|
||||
\fIref\fP is used by \fIelvis\fR' shift-K command.
|
||||
If the cursor is located on a word such as "splat", in the file "foo.c",
|
||||
then \fIelvis\fR will invoke \fIref\fR with the command "ref -f foo.c splat".
|
||||
.PP
|
||||
If \fIelvis\fR has been compiled with the -DEXTERNAL_TAGS flag, then \fIelvis\fR will
|
||||
use \fIref\fR \fB\fRto scan the tags files.
|
||||
This is slower than the built-in tag searching, but it allows \fIelvis\fR to access
|
||||
the more sophisticated tag lookup provided by \fIref\fR.
|
||||
Other than that, external tags should act exactly like internal tags.
|
||||
.SH OPTIONS
|
||||
.IP \fB-t\fR
|
||||
Output tag info, instead of the function header.
|
||||
.IP "\fB-f\fR \fIfile\fR"
|
||||
The tag might be a static function in \fIfile\fR.
|
||||
You can use several -f flags to have \fIref\fR consider static tags from more than one file.
|
||||
.IP "\fB-c\fR \fIclass\fR"
|
||||
The tag might be a member of class \fIclass\fR.
|
||||
You can use several -c flags to have \fIref\fR consider tags from more than one class.
|
||||
.SH FILES
|
||||
.IP \fBtags\fR
|
||||
List of function names and their locations, generated by \fIctags\fR.
|
||||
.IP \fBrefs\fR
|
||||
Function headers extracted from source files (optional).
|
||||
.SH ENVIRONMENT
|
||||
.IP \fBTAGPATH\fR
|
||||
List of directories to be searched.
|
||||
The elements in the list are separated by either
|
||||
semicolons (for MS-DOS, Atari TOS, and AmigaDos), or
|
||||
by colons (every other operating system).
|
||||
For each operating system, \fIref\fR has a built-in default which is probably
|
||||
adequate.
|
||||
.SH NOTES
|
||||
.PP
|
||||
You might want to generate a "tags" file the directory that contains the
|
||||
source code for standard C library on your system.
|
||||
If licensing restrictions prevent you from making the library source readable
|
||||
by everybody, then you can have \fIctags\fR generate a "refs" file,
|
||||
and make "refs" readable by everybody.
|
||||
.PP
|
||||
If your system doesn't come with the library source code, then perhaps you
|
||||
can produce something workable from the \fIlint\fR libraries.
|
||||
.SH "SEE ALSO"
|
||||
elvis(1), ctags(1)
|
||||
.SH AUTHOR
|
||||
.nf
|
||||
Steve Kirkendall
|
||||
kirkenda@cs.pdx.edu
|
||||
.fi
|
||||
@@ -1,4 +1,4 @@
|
||||
MAN= awk.1x elvis.1x kermit.1x \
|
||||
MAN= awk.1x kermit.1x \
|
||||
macros.1x mined.1x
|
||||
|
||||
.include <bsd.man.mk>
|
||||
|
||||
1272
man/man1x/elvis.1x
1272
man/man1x/elvis.1x
File diff suppressed because it is too large
Load Diff
@@ -1,6 +1,6 @@
|
||||
MAN= add_route.8 backup.8 boot.8 btrace.8 \
|
||||
cdprobe.8 chown.8 cleantmp.8 config.8 cron.8 \
|
||||
dhcpd.8 diskctl.8 elvprsv.8 fbdctl.8 fdisk.8 fingerd.8 \
|
||||
dhcpd.8 diskctl.8 fbdctl.8 fdisk.8 fingerd.8 \
|
||||
getty.8 halt.8 hgfs.8 httpd.8 ifconfig.8 inet.8 init.8 \
|
||||
intr.8 irdpd.8 loadramdisk.8 MAKEDEV.8 \
|
||||
netconf.8 newroot.8 nonamed.8 \
|
||||
|
||||
@@ -1,54 +0,0 @@
|
||||
.TH ELVPRSV 8
|
||||
.SH NAME
|
||||
elvprsv - Preserve the the modified version of a file after a crash.
|
||||
.SH SYNOPSIS
|
||||
.nf
|
||||
\fB\fBelvprsv\fP ["-\fIwhy elvis died\fP"] /tmp/\fIfilename\fP...
|
||||
\fB\fBelvprsv\fP -R /tmp/\fIfilename\fP...
|
||||
.fi
|
||||
.SH DESCRIPTION
|
||||
.PP
|
||||
\fIelvprsv\fP preserves your edited text after \fIelvis\fP dies.
|
||||
The text can be recovered later, via the \fIelvprsv\fP program.
|
||||
.PP
|
||||
For UNIX-like systems,
|
||||
you should never need to run this program from the command line.
|
||||
It is run automatically when \fIelvis\fP is about to die,
|
||||
and it should be run (via /etc/rc) when the computer is booted.
|
||||
THAT'S ALL!
|
||||
.PP
|
||||
For non-UNIX systems such as MS-DOS, you can either use \fIelvprsv\fP
|
||||
the same way as under UNIX systems (by running it from your AUTOEXEC.BAT file),
|
||||
or you can run it separately with the "-R" flag to recover the files
|
||||
in one step.
|
||||
.PP
|
||||
If you're editing a file when \fIelvis\fP dies
|
||||
(due to a bug, system crash, power failure, etc.)
|
||||
then \fIelvprsv\fP will preserve the most recent version of your text.
|
||||
The preserved text is stored in a special directory; it does NOT overwrite
|
||||
your text file automatically.
|
||||
.PP
|
||||
\fIelvprsv\fP will send mail to any user whose work it preserves,
|
||||
if your operating system normally supports mail.
|
||||
.SH FILES
|
||||
.IP /tmp/elv*
|
||||
The temporary file that \fIelvis\fP was using when it died.
|
||||
.IP /usr/preserve/p*
|
||||
The text that is preserved by \fIelvprsv\fP.
|
||||
.IP /usr/preserve/Index
|
||||
A text file which lists the names of all preserved files, and the names
|
||||
of the /usr/preserve/p* files which contain their preserved text.
|
||||
.SH BUGS
|
||||
.PP
|
||||
Due to the permissions on the /usr/preserve directory, on UNIX systems
|
||||
\fIelvprsv\fP must be run as superuser.
|
||||
This is accomplished by making the \fIelvprsv\fP executable be owned by "root"
|
||||
and turning on its "set user id" bit.
|
||||
.PP
|
||||
If you're editing a nameless buffer when \fIelvis\fP dies, then \fIelvprsv\fP will pretend
|
||||
that the file was named "foo".
|
||||
.SH AUTHOR
|
||||
.nf
|
||||
Steve Kirkendall
|
||||
kirkenda@cs.pdx.edu
|
||||
.fi
|
||||
Reference in New Issue
Block a user