Thanks for your reply. I can run Vim from the Start -> Run
menu and also by using the context menu and selecting 'Edit
with Vim'. In both cases Vim starts up with the -C file
created.
I presume you mean you actually ran the fully-qualified-path to
Vim....if not, you might have accidentally run some batch file
somewhere. Or you can browse there with explorer.exe and run
gvim.exe directly from that directory.
My next suggestion would be to try Start -> Run
"c:\program files\vim\vim70\gvim.exe" -u NONE
to see if it's something startup related. If this comes up
without the "-C" problems, then some startup file has gone off
the deep end.
In a problematic run of vim/gvim (not the above "-u NONE" run), issue
:scriptnames
to see what files are being loaded (and the order in which they
were loaded). I'd be interested in the results of this (you can
use the ":redir" command to capture its output if you
need...learning more at ":help :redir" if you need it)
Just a few more ideas,
-tim
