Re: Associating files with Vim 7

[Eric Arnold]

Search your registry (with regedit or something better) for any
conflicting entries for Vim6 and Vim7.

On 5/16/06, James Eibisch [EMAIL PROTECTED] wrote:

In Windows 2000 I'm having problems associating file extensions with Vim
7.

I've been using Vim 6.2 (GUI version) for a while, and had associated C
and TXT file extensions with it. In both Windows Explorer and a
third-party file manager (WinNavigator 1.96), double-clicking a C or TXT
file launched Vim as it should.

Yesterday I upgraded to Vim 7 (the full, self-installing gvim70.exe). The
installer uninstalled 6.2 before installing 7.

6.2 was installed in ...\vim\vim62 and 7 was installed in ...\vim\vim70.

After installing 7, double-clicking a C file didn't launch Vim. No
surprises there, as the path to gvim.exe had changed. I tried to associate
the C extension with Vim 7 via Explorer | Tools | Folder Options | File
Types, but Vim wasn't listed in the available programs - it was as if Vim
hadn't registered itself with Windows while installing.

I chose Other and navigated to vim70\gvim.exe, but when I clicked OK,
the association hadn't stuck. In the 'Registered file types' box, the C
extension said Opens with: but then a blank space - no program name. And
Vim still wasn't listed in the available programs.

However, double-clicking a C file in Windows Explorer did then launch Vim,
but clicking a C file in WinNavigator didn't launch Vim - nothing
happened.

I associated C files with another editor, EditPlus, and that did stick,
and did work in Explorer and WinNavigator. Tried associating with gvim
again, and the same problem.

Then I associated C files with the console version, vim70\vim.exe, and
that did work - the association stuck, Vim was listed in the available
programs, and files launched in console Vim in both file managers. Tried
gvim again and still no joy.

Has anyone got any ideas? I'm not sure if it's a Vim, Windows, or
WinNavigator problem :-\

Thanks.

Re: Associating files with Vim 7

[James Eibisch]

I wrote:
 In Windows 2000 I'm having problems associating file extensions
 with Vim 7.
-

Eric replied:
 Search your registry (with regedit or something better) for any
 conflicting entries for Vim6 and Vim7.
-

I've not done much with the registry before but below are some of the 
related keys. There are some 6.2 keys left in there (numbers 4, 8, 12 plus 
some others I didn't list).

Do you think it would be safe just to change all instances in the registry 
of 'vim62' with 'vim70' as a try-it-and-see solution?

1. HKEY_CLASSES_ROOT\*\OpenWithList\gvim.exe\(value not set)
2. HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers\gvim\a hex string
3. 
HKEY_CLASSES_ROOT\Applications\gvim.exe\shell\edit\command\..\vim\vim70\gvim.exe
 
%1
4. 
HKEY_CLASSES_ROOT\Applications\gvim.exe\open\edit\command\..\vim\vim62\gvim.exe
 
%1
5. HKEY_CLASSES_ROOT\CLSID\{long hex 
string}\LocalServer32\..\vim\vim70\gvim.exe
6. HKEY_CLASSES_ROOT\CLSID\{long hex 
string}\InProcServer32\..\vim\vim70\gvimext.dl
7. HKEY_CLASSES_ROOT\TypeLib\{long hex 
string}\1.1\0\win32\..\vim\vim70\gvim.exe
8. HKEY_CLASSES_ROOT\Unknown\shell\open\command\..\vim\vim62\gvim.exe 
%1
9. 
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Exploreer\FileExts\.C\gvim.exe
10. HKEY_LOCAL_MACHINE\SOFTWARE\Classes\*\OpenWithList\gvim.exe
11. 
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Applications\gvim.exe\shell\edit\command\..\vim\vim70\gvim.exe
 
%1
12. 
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Applications\gvim.exe\shell\open\command\..\vim\vim62\gvim.exe
 
%1
13. 
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Applications\vim.exe\shell\open\command\..\vim\vim70\vim.exe
 
%1