Tuesday, July 25, 2006
Bug fix: TextMate mode now works in Linux
The new TextMate mode was not working properly under linux due to some strange behaviour with expand('<cword>'). The new version (uploaded) uses a different search mechanism so all should be better. Bug reports to the usual address.
Could anyone under *nix environments try a little test for me? Open Vim, go to insert and type: AWORD<c-r>=expand('<cword>')<cr>. That is: type AWORD, hit ctrl-r, '=' and 'expand('<cword>')'. Under Windows this will insert AWORD after the first AWORD. Under Linux it does not. Post what you get along with your vim version and environment in the comments. Cheers. ¶ 11:17 am
Could anyone under *nix environments try a little test for me? Open Vim, go to insert and type: AWORD<c-r>=expand('<cword>')<cr>. That is: type AWORD, hit ctrl-r, '=' and 'expand('<cword>')'. Under Windows this will insert AWORD after the first AWORD. Under Linux it does not. Post what you get along with your vim version and environment in the comments. Cheers. ¶ 11:17 am
Comments:
<< Home
That's kind of annoying as that's the Linux set up I'm testing with. Can you double check that only 0.5.4 is present in your plugin directory. Also make sure that g:snip_set_textmate_cp is set to 1: stick 'let g:snip_set_textmate_cp = 1' in your .vimrc. You'll need to set this and restart Vim.
Simple stuff I know but if you're still having trouble then drop me an email.
Simple stuff I know but if you're still having trouble then drop me an email.
I've seen this problem a couple of times. It basically comes from installing the plugin but not having any definitions defined. When you hit tab then the search string won't have been defined (it gets defined when snippets are set) and so you get an error.
I'll look into fixing this in the next version. For now you can define a snippet that you'll never use in your .vimrc (some line noise or similar). This should work as a quick fix.
Post a Comment
I'll look into fixing this in the next version. For now you can define a snippet that you'll never use in your .vimrc (some line noise or similar). This should work as a quick fix.
Subscribe to Post Comments [Atom]
<< Home
