home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
High Voltage Shareware
/
high1.zip
/
high1
/
DIR4
/
PVILE356.ZIP
/
VILE.1
< prev
next >
Wrap
Text File
|
1993-07-30
|
4KB
|
133 lines
VILE(1) VILE(1)
NAME
vile - VI Like Emacs
SYNOPSIS
vile [-hVv] [-spattern] [+/pattern] [-ttag] [-gNNN] [+NNN]
[@cmdfile] [filename]...
DESCRIPTION
vile is a text editor. This man page is fairly terse.
More information can be obtained from the internal help,
available with the -h option or by using the ":help" com-
mand from within vile.
OPTIONS
+NNN and -gNNN
vile will begin the session on the first file at
the specified line number.
+/pattern or -s pattern
In the first file, vile will execute an initial
search for the given pattern.
-t The -t option specifies a "tag". vile will edit
the file containing, and place the cursor at, that
tag. This requires a tagsfile created by the
ctags(1) command.
-h Invokes vile on the helpfile.
-v Invokes vile in "view" mode - no changes are per-
mitted to the buffer in this mode. (This will also
be true if vile is invoked as view.)
-V vile will report its version number.
INVOCATION
vile will edit the files specified on the command line.
If no files are specified, and standard input is not con-
nected to a terminal, then vile will bring up a buffer
containing the output of the pipe it is connected to, and
will re-open /dev/tty for commands. Files (except for the
first) are not actually read into buffers until "visited".
All buffers are kept in memory: machines with not much
memory or swap space may have trouble with this.
SPIRIT
vile retains the "finger-feel", if you will, of vi, while
adding the multiple buffer/multiple window features of
emacs and other editors. It is definitely not a vi clone,
in that some substantial stuff is missing, and the screen
doesn't look quite the same. The things that you tend to
type over and over probably work -- things done less fre-
quently, like configuring a startup file, are quite dif-
ferent. But what matters most is that one's "muscle
1
VILE(1) VILE(1)
memory" does the right thing to the text in front of you,
and that is what vile tries to do for vi users.
COMMANDS
Please refer to the help available within vile for vile-
specific commands. That document, however, assumes famil-
iarity with vi.
Currently, documentation on writing macros using the
internal scripting language is lacking, although the help-
file does contain examples. Current microEmacs documenta-
tion would be helpful here.
STARTUP
vile will read initial commands from a .vilerc file in the
current or home directories. See the help file for exam-
ples of how this can be used.
SEE ALSO
Your favorite vi document, and current microEmacs docu-
ments.
DEBTS and CREDITS
vile was originally built from a copy of microEmacs, so a
large debt of gratitude is due to the developers of that
program. A lot of people have helped with code and bug
reports on vile. Names are named at the bottom of the
help file.
AUTHOR
vile was created by Paul Fox. That's Paul G. Fox.
There's another editor, a clone of BRIEF called crisp,
which was written by a Paul D. Fox. I'm not him.
BUGS
The "VI Like Emacs" joke isn't really funny. It only
sounds that way. :-)
2