MAN page from RedHat EL 8 vile-9.8t-4.el8.x86_64.rpm
Section: User Commands (1)Index
vile, xvile, uxvile, lxvile - VI L
SYNOPSISvile [@cmdfile] [+command] [-FhIiRVv] [-gNNN] [-kcryptkey] [-spattern] [-ttag] [filename]...
is a text editor.This man page is fairly terse.More information canbe obtained from the internal help,available with the -h
optionor by using the ``:help'' command from withinvile
xvileis the same text editor,built as an X-windows application,with fully integrated mouse support,scrollbars, etc.
uxvileis a wrapper aroundxvilewhich invokes the latter program with the correct locale environmentrequired to use a unicode character set and the ``UXVile'' X resourceclass set.
lxvileis a wrapper aroundxvilewhich invokes the latter program with a font chosen to match the current localeenvironment.
retains the ``finger-feel'' if you will, ofvi
,while adding themultiple buffer and 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 andover probably work.Things done less frequently,like configuring a startup file,are somewhat (or very, depending on how ambitious you are) different.But whatmatters most is that one's ``muscle memory'' does the right thingto the text in front of you, and that is whatvile
tries to do for vi users.
Vile accumulates most options into two temporary buffers [vileinit]
.The former is executed before reading the first file into a buffer.The latter is executed after reading the first file into a buffer.Each is removed after executing (unless an error is detected).
- vilewill begin the session on the first file invoking the given command.Legal commands include many ex-style commands, vile-commands, etc.,subject to shell quoting.This option is used most often with a line number or search pattern.For example
vile -c123 filenamevile -c/pattern filename
- They correspond to ex-style commands on the given file:
- These are more verbose equivalents:
vile -c'123 goto-line' filenamevile -c'search-forward /pattern/' filename
- You can use more than one command, e.g.,
- vile -c'123' -c'10*goto-col' filename
- to put the cursor on column 10 of line 123.The ``*''(or ``:'' separates the repeat count(used by goto-col) from theline- or range-specification used by line-oriented commands.
- vilewill run the specified file as its startup file,and will bypass any normal startup file (i.e..vilerc)or environment variable (i.e.$VILEINIT).This is added to [vileinit].
- tells vile to trace the results of macro execution into the hidden buffer``[Trace]''.
- -e | -E
- Invokesvilein ``noview'' mode - changes are permitted to any buffer whilein this mode (see ``-v''.
- will run the syntax filter that applies to each filename on the command-line,and write the attributed text to the standard output.
- Invokesvileon the helpfile.
- -i | -I
- Tellsvileto usevileinit.rc(which is installed)as the initialization file.If you do not have a .vilerc,vilewill make a short one that sourcesvileinit.rcThis is added to [vileinit].
- -k cryptkey | -K cryptkey
- Specifies an encryption/decryption key.See below for further discussion.This option applies only locally to the buffers named on the command-line,and is not added to [vileopts],since that is executed too late.
- Invokesvilein ``readonly'' mode - no writes are permitted whilein this mode.(This will also be true ifvileis invoked asview,or if ``readonly'' mode is set in the startup file.)
- -s pattern | -S pattern
- In the first file,vilewill execute an initial search for the given pattern.This is not the same as ``-c/pattern''since that positions the cursor tothe line matching the pattern.This option positions the cursor within the line.
- -t tag
vilewill edit the correct file and move the cursor to the location of the tag.This requires a tagsfile created with thectags(1)command.The option -T is equivalent,and can be used when X11 option parsing eats the -t.
- overrides the $system-crlf variable, making new buffers start in dos mode.
- overrides the $system-crlf variable, making new buffers start in nodos mode.
- Invokesvilein ``view'' mode - no changes are permitted to any buffer whilein this mode (see ``-e''.
- vilewill report its version number.
- -25 -43 -50 -60
- On PC systems you may be able to set the initial screen resolution from thecommand line.
- -80 -132
- On VMS systems you may be able to set the initial screen resolution from thecommand line.Seevile.hlpfor details.
xvile-specificcommand-line options are detailed in the help file (see ``Standard X commandline arguments''.The standard ones (e.g., -display, -fn, -geometry, -name,etc.) are all supported.
vile recognizes some options which duplicate the functionality of thePOSIX ``-c'' option:
- This has the same effect as ``-ccommand''
- -g NNN | -G NNN
- This has the same effect as ``-cNNN''vilewill begin the session on the first file jumping to the given line numberNNN.
vile will edit the files specified on the command line.If no filesare specified, and standard input is not connected to a terminal,then vile will bring up a buffer containing the output of the pipe it isconnected to, and will re-open /dev/tty for commands.Files (except forthe first) are not actually read into buffers until ``visited''All buffersare kept in memory: machines with not much memory or swap space mayhave trouble with this.
cmdfileoption is given, then the file given as ``cmdfile''will be run before any files are loaded.If no@
option appears, startup commands will be taken from the user'sVILEINIT
variable, if it is set, from the file.vilerc
in the current directory, if it exists, or from$HOME/.vilerc
,as a last resort.See the help file for examples of what sorts of things might go intothese command files.
Please refer to the help available withinvile
-specificcommands.(That document, however, assumes familiarity with vi.)Short descriptionsof eachvile
command may be obtained with the ``:describe-function'' and``:describe-key'' commands.All commands may be listed with ``:show-commands''
Additional documentation on writing macros using the internal scriptinglanguage can be found in the file macros.doc,distributed with the vile source.
may also be built and installed asxvile
,in which case itbehaves as a native X Windows application, with scrollbars, better mousesupport, etc.
The help file has more information on this in the sectionX Window System specifics.
There is a program distributed with the vile source whichis usually installed asvile-manfilt.It may be used in conjunction withvileorxvile(with the help of the macros in the file manpage.rc)to filter and view system manual pages.xvilewill even(with your font set properly)display certain portions of the manualpage text in bold or italics as appropriate.
See the help file section on Filtering ``man'' pages for details.
Likewise, there are several language filters, e.g.,vile-c-filtfor C,which can embolden, underline, or perform coloring on programsource code.
Again, see the help file section on Syntax Coloring for more information.
Vile is not simply an interactive program.Its macro language and use of environment variables lets itbe useful in scripting.
The syntax filters and vile-manfilt may not be installed whereyou would execute them in your PATH.The vile-libdir-path script looks in the usual places andprints an updated PATH variable which other scriptscan use when executing these programs.
Vile can be used as a pager(typical examples include more and less).This script uses vile-manfilt to preprocessa file which is piped to vile,adding markup which vile displays properly.
Unlike a typical pager, vile-pager handles multi-line color escapesequences, and multiple levels of overstrikes.But unlike a typical pager, vile-pager expects the pipe to beclosed before it starts displaying.
Vile's ``-F'' option makes it act like a smart interface to thecollection of syntax filters.But its output uses vile's internal markup rather than standard escapesequences.Vile's utilities include programs which translate that markup intodifferent formats:
- converts the markup to ANSI escape sequences.
- converts the markup to HTML (with color).
- converts the markup to plain text.
The vile-to-html script uses atr2html to convert a text fileinto HTML using color.
can be used to encrypt/decrypt files using the same algorithm asmicroEmac
'sinternal crypt algorithm.This program, which uses public domain code written by Dana Hoggatt,is no longer used in vile, though it is provided for compatibility.
vilecurrently uses thecrypt(3)function for encryption/decryption, which is available on most Unix systems.This ensures thatvileis able to read and write files compatibly with vi(but not vim, which uses an different algorithm derived from info-zip).The editor's encryption/decryption key can be specified on thecommand line with ``-k key''Text to be encrypted can be specified as filenames on the commandline, or provided as the standard input.
On systems with a getpass()library routine, the user will be prompted for the encryption key if it isnot given on the command line.To accommodate systems (such as linux) wherethe getpass() library routine is not interruptible from the keyboard,entering a crypt-key password which ends in ^C will cause the program toquit.
See the help file for more information onvile'sencryption support, including a discussion of a collection of macros thatinterface with GNU's gpg package.
- Editor initialization commands in lieu of a startup file.These are copied into [vileinit], and executed.
- Override the name of the help file, normally ``vile.hlp''.
- Augment $PATH when searching for a filter program.
- Override the name of the startup file, normally ``.vilerc''(or ``vile.rc'' for non-UNIX systems).
- Override the search path for the startup and help files.
Your favorite vi document, the filemacros.doc
help page, available with the-h
option or as the text filevile.hlp
DEBTS and CREDITSvile
was originally built from a copy of microEmacs, so a large debt of gratitudeis due to the developers of that program.A lot of people have helped withcode and bug reports onvile
.Names are named at the bottom of the help file.
was created by Paul Fox, Tom Dickey, and Kevin Buettner.
The "VI L
macs'' joke isn't really funny.It onlysounds that way. :-)Other suspicious behavior should be reportedvia the project mailing list, or via the web-based bug reportingsystem.Both of these are available here:
- COMMON OPTIONS
- X11 OPTIONS
- OBSOLETE OPTIONS
- RELATED PROGRAMS
- Syntax filters
- UTILITY SCRIPTS
- ENVIRONMENT VARIABLES
- SEE ALSO
- DEBTS and CREDITS
This document was created byman2html,using the manual pages.