I've been trying to get the tests to run cleanly (host and target: Windows
7 x64), but I'm not having much luck with some of them.  Are they
up-to-date and expected to run cleanly?

I've been assuming that any issues I'm finding are due to my own
environment, of course.  But test 73, for example, isn't cooperating.  It
tests autocompletion for the :find command, and several of its tests set
the '**' wildchar in the path option, e.g.

    set path=Xfind/**

It's not working right.  When troubleshooting I found this note at the end
of editing.txt:

    Note that completion for ":find", ":sfind", and ":tabfind" commands do
not
    currently work with 'path' items that contain a url or use the double
star
    (/usr/**2) or upward search (;) notations. >

Is the doc accurate?  If so, what does that mean for the test?

Since I've encountered a handful of other tests that seem to exhibit a
little "bit rot" (my own environment may still be the culprit, of course),
I figured now would be a good time to ask whether they're expected to run
on Windows 7, before I continue digging in.  I've already been running
under the debugger and I have a clue to what's going on, but the find-files
code is a lot to digest.

----
David Pope

-- 
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

Raspunde prin e-mail lui