- I install gvim72.exe with default settings on Windows XP SP3 ENG.
- Unpack snipMate.zip in vim's folder (D:/vim/vim72/).
- Create new empty file and type: date<TAB>
- "date" not replace to current date.
On Ubuntu this script work.
Comment #1
Posted on Jul 11, 2009 by Happy ElephantI have the same problem, it seems that vim cannot load $VIMRUNTIME/after/plugin/snipMate.vim automatically
After I have added: source $VIMRUNTIME/after/plugin/snipMate.vim in my .gvimrc, everything is okay.
Comment #2
Posted on Jul 11, 2009 by Grumpy KangarooDo you have "filetype plugin on" in your .vimrc?
Comment #3
Posted on Jul 14, 2009 by Massive PandaI have the same problem too. I need to execute ":so $VIMRUNTIME/after/plugin/snipMate.vim" and ":call GetSnippet(, )" to make snipMate work.
I do have "filetype plugin on" in my .vimrc.
Comment #4
Posted on Jul 26, 2009 by Happy OxDoesn't work for me, either. It works with the cygwin version in x-windows, and works on Ubuntu. All are configured about the same.
Funny thing is, I'm getting confused about where initialization files go (although I've tried all possible places). For example, for my Windows version, it definitely reads .vimrc/.gvimrc from my home directory, same as cygwin. It also seems like it might read _vimrc from the $VIM directory if .vimrc is not available.
Comment #5
Posted on Jul 26, 2009 by Happy OxAfter trying everything, I upgraded from version 7.0 to 7.2, after uninstalling 7.0. I also installed on a different drive, just to really be sure everything reset.
After that, the plugin worked with no problems.
Comment #6
Posted on Sep 29, 2009 by Happy RhinoComment deleted
Comment #7
Posted on Sep 29, 2009 by Happy RhinoSee :help 'runtimepath'.
The directory $VIMRUNTIME/after is never sourced. You should unzip snipMate.zip inside $VIM/vimfiles (typically C:\Program Files\vim\vimfiles)
So delete all files under vim72\ that were inserted there by snipmate.zip, and re-unzip the plugin there.
Comment #8
Posted on Oct 24, 2009 by Swift OxI would like to thank everyone. I solved this problem.
First of all, in oder to made full independent installation of Vim on Windows, I used Portable version of vim and changed its directories according to this Tip:http://vim.wikia.com/wiki/Version_independent_installation_of_Vim_on_Windows. Then I little bit changed file GVimPortable.ini and put it in root directory of GVimPortable.
As a result, I have full independent and portable installation of Vim with runnable SnipMate plugin. This version of GVimPortable is attached to this topic.
- vim_monthly.7z 4.46MB
Comment #9
Posted on Dec 11, 2009 by Massive MonkeyI'm having the same issue as well. Filetype plugin on, Vim 7.2. mortgat's suggestion did not help.
Comment #10
Posted on Jan 15, 2010 by Swift HorseYou need to change your runtime path. This is how mine lokos like: set runtimepath=~/vim_local,~/vim_local/after,$VIMRUNTIME
Regards, amix
Comment #11
Posted on Jun 29, 2010 by Happy MonkeyComment deleted
Comment #12
Posted on Jun 29, 2010 by Happy MonkeyThere was something in my .vimrc which collided with the extension, so I threw all stuff out and started with a completely empty configuration which fixed it. I didn't even need the proposed runtimepath setting.
Comment #13
Posted on Oct 17, 2010 by Happy HippoI tried everything i can think of to make it work.
reinstalled vim 7.3 from scratch installed snipMate into the appropriate vim73 folders added the "filetype plugin on" to my _vimrc tested, fails to do anything when I hit tab
added source $VIMRUNTIME\after\plugin\snipMate.vim to _vimrc, tried both slashes checked the keymappings (and they look right, :snoremap, :inoremap) checked that the scripts loaded with ":scriptnames" and they are listed. cleared my _vimrc file tested on html and .c files, still fails
Added "set runtimepath=~/vim_local,~/vim_local/after,$VIMRUNTIME" to _vimrc tested, still fails
changed the mapped key to control-J, tested, fails
Out of ideas now, so I'm ready to assume it's just broken for vim73 and win7(64) unless someone else has it working.
Comment #14
Posted on Oct 26, 2010 by Swift CamelAdd this line:
source $VIMRUNTIME/after/plugin/snipMate.vim
at the end of file C:\Program Files\Vim\vim73\plugin\snipMate.vim It`s work for me.
Comment #15
Posted on Oct 29, 2010 by Swift MonkeyThe solution by NickLasos works for me. It would be nice to have this fixed for real though. I suppose it's a bug with gvim for windows though...
Comment #16
Posted on Nov 6, 2010 by Quick BearMortgat's suggestion works! Just make sure you set your filetype to the file you're working on. I made the mistake of trying html snippets while I was on a php file. A simple ":set filetype=html.php" worked after mortgat's advice.
Cheers!
Comment #17
Posted on Nov 11, 2010 by Grumpy CamelIn WinXP sp3 NickLasos solution worked just fine for me, thanks :D
Comment #18
Posted on Dec 27, 2010 by Helpful RabbitIn addition to "after" issue I find that more than one snippets folder kills plugin, also i will not recommend copy plugin on more than one source folder, just in case
Comment #19
Posted on Jul 3, 2013 by Massive RhinoI solved this on my system by setting the g:snippets_dir variable: g:snippets_dir="C:/Vim/vimfiles/snippets" <-- here -- As I already had some config below from a previous setup I forgot about: source C:/Vim/vimfiles/snippets/support_functions.vim source C:\Vim\vimfiles\after\plugin\SnipMate.vim autocmd vimenter * call ExtractSnips("C:/Vim/vimfiles/snippets/html", "eruby") autocmd vimenter * call ExtractSnips("C:/Vim/vimfiles/snippets/html", "python")
Status: New
Labels:
Type-Defect
Priority-Medium