* Test-case "drivers" can be generated locally with the example test-case data
(currently C++ only).
+Build Status
+------------
+
+[![Build Status](https://travis-ci.org/chazmcgarvey/vimcoder.svg?branch=master)](https://travis-ci.org/chazmcgarvey/vimcoder)
+
License
-------
directory, you may also want to actually move the directory to the new
location so that VimCoder can find the work you've already done.
-Beginning with VimCoder 1.3.5, there is a new option for an alternative
+Beginning with VimCoder 0.3.5, there is a new option for an alternative
directory structure. It is not enabled by default, but it may be in the
future. Rather than having directories named after problem identifiers, the
new structure uses two levels of directories. On the first level, directories
You may use an absolute path to your vim executable, such as
`/usr/local/bin/gvim` or `C:\Program Files\Vim\vim73\gvim.exe`
or wherever your actual Vim executable is. You may also invoke vim through
-some other command (e.g. `xterm -e vim`).
+some other command (e.g. `xterm -e vim` or `gnome-terminal -e vim --`).
The xterm example above demonstrates using Vim without the GUI, running in
a terminal emulator. You can enter any elaborate command you want as long as