| Age | Commit message (Collapse) | Author |
|---|
|
Problem: When startup test fails it's not easy to find out why.
GUI test fails with Gnome.
Solution: Add the help entry matches to a list an assert that.
Set $HOME for Gnome to create .gnome2 directory.
|
|
Problem: Reading from stdin test fails on MS-Windows.
Solution: Strip the extra space.
|
|
Problem: No test for reading from stdin.
Solution: Add a test.
|
|
Problem: No testing for -C and -N command line flags, file arguments,
startuptime.
Solution: Add tests.
|
|
Problem: Can't test help on MS-Windows.
Solution: Skip the test.
|
|
Problem: No test for "vim --help".
Solution: Add a test.
|
|
Problem: Startup test gets stuck on MS-Windows.
Solution: Use double quotes.
|
|
Problem: Small build can't run startup test.
Solution: Skip the test.
|
|
Problem: Startup test fails on MS-Windows.
Solution: Don't check output if RunVim() returns zero.
|
|
Problem: It is not possible to use plugins in an "after" directory to tune
the behavior of a package.
Solution: First load plugins from non-after directories, then packages and
finally plugins in after directories.
Reset 'loadplugins' before executing --cmd arguments.
|
|
Problem: Loading defaults.vim with -C argument.
Solution: Don't load the defaults script with -C argument. Test sourcing
the defaults script. Set 'display' to "truncate".
|
