> Wondering whether there is a technical reason to have test names
> looking like testN.*? It is already not easy to determine what test
> tests which functionality, and even less easier to find the test if
> you need to add new subtests.
> Names like test_python.*, test_python3.*, init_test_files.vim (!!!
> must not be a test: I am talking about “test” test1.in),
> test_gf.* and so on look much nicer. And unlike error numbers such
> change seems to not introduce compatibility problems.
Historic reasons. For some tests it will be difficult to come up with a
How about making a README file that lists the tests and what's in them?
If "R" is Reverse, how come "D" is FORWARD?
/// Bram Moolenaar -- Bram@...
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
\\\ an exciting new programming language -- http://www.Zimbu.org
\\\ help me help AIDS victims -- http://ICCF-Holland.org
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscribe@...
For more options, visit https://groups.google.com/groups/opt_out.