[support] filetype off

[comboy]

May I ask what's the reason for this "filetype off" before calling vundle?

I have a problem that when it is called, then even though there is "filetype plugin indent on" at the end of file, it still won't load my system syntax files (e.g. gitcommit.vim).

But when I remove this "filetype off" before vundle then vim-coffee-script is not recognizing files properly.

I use workaround with autocmd for *.coffee, but it's all a bit mysterious to me why are these things happening. Any help would be very appreciated.

[jdevera]

There was a bug in Vim's file detection that used to cause this weird behaviour, it has been fixed in Vim 7.3.430. I your version is newer, please disregard this comment.

[jasonkuhrt]

@jdevera How does one check their vesion of vim (I know of :version etc. but that only states 7.3).

And if > 7.3.430 is an edge build how do I attain it?

Cheers

[johannish]

@jasonkuhrt (And for future readers) The final number is the "patch version" visible on the second line of the :version output:

VIM - Vi IMproved 7.3 (2010 Aug 15, compiled May 4 2012 04:21:49)
Included patches: 1-429

So my version is 7.3.429

[sudar]

So if we have vim version > 7.3.430 can we remove filetype off from the first line of .vimrc file and replace it with filetype on?

[jdevera]

The answer is no, as I just found out from my little experiment. However, what seemed to work was to do

filetype off
filetype plugin indent on

After the bundles block. File type detection must be enabled after the Bundles block because the runtime path is updated by every Bundle command and that could potentially bring new file types or more plugins for specific file types. It also appears that turning it on, when it's on, does nothing, so it must be turned off before.

If you are reluctant to turn it off because it affects some file type detection, please try a newer vim version, with the 430th patch (quite unluckily, Ubuntu picked up only up to the patch right before that one.)

[sudar]

@jdevera Thanks for the reply.

I will try to update my vim to > 7.3.430

[bor]

thanks guys, the topic is helpful

[sheerun]

That's the answer I needed :)

[ackalker]

@jdevera @gmarik
Could one of you please update the comment after filetype off in the example .vimrc in https://github.com/gmarik/vundle/blob/master/README.md with documentation as to when and where it applies?
This will spare a lot of users a spelunking trip to the issues section or the Git history to find out whether or not they need to apply it.
Even after reading all the comments in this issue, I'm not sure if I need to put filetype off (I'd rather not :-) ), and if so, if and where I can safely re-enable it.
I'm a relatively new (>2 years) Vim user, using vim 7.4.135 package on Arch Linux.

Thanks!

[lucc]

@ackalker
looking at the last message from @jdevera above I would say it always applies. You have vim 7.4 so all this version details do not apply for you (they only apply for 7.3). This means you can put

filetype off
filetype on

after loading your last Bundle.

I think the comment should stay in the README file a little longer as many people still might have a version <7.3.430 (the relatively new OSX Maverics ships with vim 7.3 and no patches as far as I can tell)

[ackalker]

Thanks for your quick reply :-)
I've added this to my .vimrc as you suggested and it works well.

[Shougo]

It is not bug. It is Vim's feature.
Vim makes cache for filetype plugins from runtimepath. So if vundle changes runtimepath, it must reset before calling.
But Vundle can reset filetype by :filetype off internally. It is policy problem. neobundle does it.

[ackalker]

Ah I see. Thanks for pointing this out.
I've added the off / on switches before and after my Bundle definitions, and all is working well (except for one plugin, but that's a problem with that plugin, not Vundle :-) )

[Shougo]

I think this issue should be closed.

[starcraftman]

This probably should have been closed a while ago. Maybe we'll revisit if NeoVim makes nice changes and becomes stable.