|
|
1.1 ! root 1: .TH ELVIS v1.4 ! 2: .SH NAME ! 3: elvis, ex, vi, view, input - The editor ! 4: .SH SYNOPSIS ! 5: \fBelvis\fP [\fIflags\fP] [\fB+\fP\fIcmd\fP] [\fIfiles\fP...] ! 6: .SH DESCRIPTION ! 7: \fIElvis\fP is a text editor which emulates \fIvi\fP/\fIex\fP. ! 8: .PP ! 9: On systems which pass the program name as an argument, such as Unix and Minix, ! 10: you may also install \fIelvis\fP under the names "ex", "vi", "view", and "input". ! 11: These extra names would normally be links to elvis; ! 12: see the "ln" shell command. ! 13: .PP ! 14: When \fIelvis\fP is invoked as "vi", ! 15: it behaves exactly as though it was invoked as "elvis". ! 16: However, if you invoke \fIelvis\fP as "view", ! 17: then the readonly option is set as though you had given it the "-R" flag. ! 18: If you invoke \fIelvis\fP as "ex", ! 19: then \fIelvis\fP will start up in the colon command mode ! 20: instead of the visual command mode, ! 21: as though you had given it the "-e" flag. ! 22: If you invoke \fIelvis\fP as "input" or "edit", ! 23: then \fIelvis\fP will start up in input mode, ! 24: as though the "-i" flag was given. ! 25: .SH OPTIONS ! 26: .IP \fB-r\fP ! 27: To the real vi, this flag means that a previous edit should be recovered. ! 28: \fIElvis\fP, though, has a separate program, called \fIvirec(1)\fP, for recovering ! 29: files. ! 30: When you invoke \fIelvis\fP with -r, \fIelvis\fP will tell you to run \fIvirec\fP. ! 31: .IP \fB-R\fP ! 32: This sets the "readonly" option, ! 33: so you won't accidentally overwrite a file. ! 34: .IP "\fB-t\fP \fItag\fP" ! 35: This causes \fIelvis\fP to start editing at the given tag. ! 36: .IP "\fB-m\fP [\fIfile\fP]" ! 37: \fIElvis\fP will search through \fIfile\fP for something that looks like ! 38: an error message from a compiler. ! 39: It will then begin editing the source file that caused the error, ! 40: with the cursor sitting on the line where the error was detected. ! 41: If you don't explicitly name a \fIfile\fP, then "errlist" is assumed. ! 42: .IP \fB-e\fP ! 43: \fIElvis\fP will start up in colon command mode. ! 44: .IP \fB-v\fP ! 45: \fIElvis\fP will start up in visual command mode. ! 46: .IP \fB-i\fP ! 47: \fIElvis\fP will start up in input mode. ! 48: .IP \fB+\fP\fIcommand\fP ! 49: If you use the +\fIcommand\fP parameter, ! 50: then after the first file is loaded ! 51: \fIcommand\fP is executed as an EX command. ! 52: A typical example would be "elvis +237 foo", ! 53: which would cause \fIelvis\fP to start editing foo and ! 54: then move directly to line 237. ! 55: .SH FILES ! 56: .IP /tmp/elv* ! 57: During editing, ! 58: \fIelvis\fP stores text in a temporary file. ! 59: For UNIX, this file will usually be stored in the /tmp directory, ! 60: and the first three characters will be "elv". ! 61: For other systems, the temporary files may be stored someplace else; ! 62: see the version-specific section of the documentation. ! 63: .IP tags ! 64: This is the database used by the \fI:tags\fP command and the \fB-t\fP option. ! 65: It is usually created by the \fIctags(1)\fP program. ! 66: .SH "SEE ALSO" ! 67: ctags(1), ref(1), virec(1) ! 68: .PP ! 69: \fIElvis - A Clone of Vi/Ex\fP, the complete \fIelvis\fP documentation. ! 70: .SH BUGS ! 71: There is no LISP support. ! 72: Certain other features are missing, too. ! 73: .PP ! 74: Auto-indent mode is not quite compatible with the real vi. ! 75: Among other things, 0^D and ^^D don't do what you might expect. ! 76: .PP ! 77: Long lines are displayed differently. ! 78: The real vi wraps long lines onto multiple rows of the screen, ! 79: but \fIelvis\fP scrolls sideways. ! 80: .SH AUTHOR ! 81: .nf ! 82: Steve Kirkendall ! 83: [email protected] ! 84: \&...uunet!tektronix!psueea!eecs!kirkenda ! 85: .fi ! 86: .PP ! 87: Many other people have worked to port \fIelvis\fP to various operating systems. ! 88: To see who deserves credit, run the \fI:version\fP command from within \fIelvis\fP, ! 89: or look in the system-specific section of the complete documentation.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.