Vim 6.0 has been in alpha testing for quite a while. Although it appears to
work well, it needs to be tested before we can say it is really stable.
Expect to run into a few problems.

What is Vim?
------------

Vim is an almost 100% compatible version of the UNIX editor Vi. Many new
features have been added: Multi level undo, syntax highlighting, command line
history, filename completion, block operations, etc. Those who don't know Vi
can probably skip this message, unless you are prepared to learn something new
and useful. Vim is especially recommended for editing programs.

Folding - momentarily hide part of the text
Vertically split windows - mixed with horizontal splits
Diff mode - show and remove differences between files
Easy Vim: click-and-type - for those who really don't like two modes
User manual - learn to use Vim, reads like a book
Flexible indenting - automatic indenting for any language
Extended search patterns - more regexp power than you will need
UTF-8 support - Unicode allows editing nearly all languages
Multi-language support - translated messages and menus
Plugin support - drop a script in a directory and you can use it
Filetype plugins - an easy way to setup for editing a type of file
File browser - browse directories, also on a terminal
Editing files over a network - read and write a remote files directly
command-line editing window - use any Vim command to edit an Ex command
Debugging mode - debug your Vim functions and scripts
Cursor in virtual position - edit tables and draw ASCII pictures
Debugger interface - use Vim with Sun Visual Workshop
Communication between Vims - let one Vim tell another Vim what to do
Printing - print with syntax colors (MS-Windows only)
Quickfix extended - see error messages in a window and jump there
Writing files improved - rename or copy to make a backup file
Argument list - select groups of files to work on
Restore a View - save the looks of a window and restore it later
Color schemes - quickly switch between different color setups

Send them to <bugs@...>. Please describe the problem precisely. All the
time spent on answering mail is subtracted from the time that is spent on
improving Vim! Always give a reproducable example and try to find out which
settings or other things influence the appearance of the bug. Try starting
without your own vimrc file: "vim -u NONE -U NONE". Try different machines if
possible. See ":help bugs" in Vim. Send me patches if you can!

If something needs discussing with other developers, send a message to the
vim-dev mailing list. You need to subscribe first.