On Fri 19-Jan-07 5:13pm -0600, kjcdb8er wrote:
> Thanks for your help. Based on your suggestions I checked
> on the $VIMRUNTIME variable, and it was not set in my
> environment variables. Also, $PATH did not include the vim
> folder (I don't know if that makes a difference or not).
You shouldn't have to define $vimruntime - Gvim will do the
detection from where it is started. I don't have Vim or
Gvim in my PATH - I usually start from my shell (4nt) with
aliases (for the various ways I want to start it).
> After setting these variables, all menus appear to be
> working properly (yay!) and the tests you described
> produced similar results from my command prompt (although
> no file temp\vfile was created; instead, dialog windows
> popped up containing the information described. gvim
> %temp\vfile opened a blank file. )
Hmm, I thought a TEMP variable was always set by Windows.
Of course, you can override it or unset it. I just picked
TEMP because I thought it would be available to you. More
likely is the command:
gvim -u NONE -i NONE -N -V2%temp\vfile "+q"
should be:
gvim -u NONE -i NONE -N -V2%temp%\vfile "+q"
if you are using CMD. Also, review the result with:
gvim %temp%\vfile
Sorry, I rarely use CMD.
> Do you know if file name tab completions need to be
> initialized separately?
It does not. It should work fine right out of the box (i.e.
with gvim -u NONE -i NONE -N). It certainly does here.
You might want to read about related settings such as
'wildignore', 'wildmenu' and 'wildmode' to learn about
enhanced file completion.
BTW. when you ran the code between the equal sign lines -
without setting $vimruntime - what do you see?
--
Best regards,
Bill
