Fix bug with python3 support crashing Gundo
The recent change that introduced python3 support also made it the default
python version used for Gundo. This caused a problem with certain versions of
vim where upon toggling the Gundo window, we would be greeted with an error
message: "This Vim cannot execute :py3 after using :python"
This commit adds a g:gundo_prefer_python3 variable (default 0) that can be used
to set a preference for python3. By default, python2 will be used.
This also required moving the variable initialization code to the top, since
just evaluating `has('python3')` seems to trigger the vim error.
| author |
Strahinja Markovic <strahinja.markovic@gmail.com> |
| date |
Mon, 29 Aug 2011 14:13:01 +0200 |
| parents |
dbd4f2ec3861 |
| children |
(none) |
This is Gundo's test suite. In case you didn't know, unit testing vim plugins
is a horrible experience.
Gundo bundles Luc Hermitte's [UT][] framework to make the process less painful.
[UT]: http://code.google.com/p/lh-vim/wiki/UT
To run a test, `cd` into the `tests` directory and use:
./run-tests.sh [[some-test.vim] ...]
The script will run the console vim command with its own vimrc and .vim
directory, so none of your other plugins should interfere. The result of the
tests will be shown in the quickfix window of this vim instance.
The `q` key will be remapped to perform `:qa!` so you can close everything
quickly if it all looks good.
The `run-tests.sh` script is still a work in progress. I need to figure out
a good way of collecting results. Suggestions and/or patches are very welcome.