Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FTDetect files not getting sourced #16

Closed
ghost opened this issue Apr 22, 2011 · 10 comments
Closed

FTDetect files not getting sourced #16

ghost opened this issue Apr 22, 2011 · 10 comments
Labels

Comments

@ghost
Copy link

ghost commented Apr 22, 2011

I am using my vim-slim plugin with vundle.

When I just use it with vundle, it ignores the ftdetect (It appears since the highlighting does not kick in) but when I manually run the commands out of the ftdetect file (IE :autocmd BufNewFile,BufRead *.slim set filetype=slim) and then open the slim files it loads the syntax highlighting.

Is there any reason that vundle would be ignoring the ftdetect directory?

@gmarik
Copy link
Contributor

gmarik commented Apr 22, 2011

Ok, that's the case when you Vundle configuration should look like this

filetype off
" vundle configuration here
" ...
filetype plugin indent on

Please let me know if it works for you..

PS: i couldn't reproduce this issue before... I'll update the docs
Thank you!

@gmarik
Copy link
Contributor

gmarik commented Apr 22, 2011

Docs updated!

@gmarik gmarik closed this as completed Apr 22, 2011
@ghost
Copy link
Author

ghost commented Apr 23, 2011

Thanks much. That did it.

@jassinm
Copy link

jassinm commented Feb 15, 2012

Having problems with this for some plugins like VimClojure or Bundle 'acustodioo/vim-tmux' which use ftdetect.
i do have filetype off and filetype plugin indent on
myvimrc is @ https://github.com/locojay/locovim/blob/master/vimrc.
Thanks for helping

@fritzblue
Copy link

As seen above, lots of UltiSnips users end up running into filetype-related issues if they configure this incorrectly (e.g. when using the UltiSnipsEdit command). For me, it was important to have the entire block of Vundle configuration in one piece, with the two filetype calls immediately above and below it (as shown by @gmarik above). Hopefully this helps someone who comes across this in the future.

tyru added a commit to tyru/config that referenced this issue Jul 10, 2014
@johntyree
Copy link

@user453584 worked for me as well. Finally! I was getting really tired of this one. Thanks!

@sharat87
Copy link

sharat87 commented Apr 2, 2015

This might help someone later...

If moving filetype plugin indent on to after vundle#end doesn't fix it for you, try moving syntax on also to after the call to vundle#end. All the vundle configuration doesn't have to be in one place if you move both filetype plugin indent on and syntax on below vundle#end.

@pelodelfuego
Copy link

+1 on sharat87 solution.
It is related to a lot on utliSnip issues.
Maybe the Readme.md should be updated to remove any doubt ?

supercow added a commit to supercow/puppet-vim that referenced this issue Aug 5, 2015
This is to fix an issue where plugins don't load properly by ftdetect.
VundleVim/Vundle.vim#16
@elrrrrrrr
Copy link

+1 on sharat87 solution.

@johntyree
Copy link

@elrrrrrrr please don't add +1 comments on issues unless you have new information that people should read. A lot of emails get sent every time someone makes a comment.

matthiasvegh added a commit to matthiasvegh/dotfiles that referenced this issue May 31, 2016
As mentioned in VundleVim/Vundle.vim#16 filetype plugin indent on has
be called after `call vundle#end()`
fno2010 added a commit to fno2010/vimrc that referenced this issue Dec 27, 2016
Also fix some issues:
- Bind ,s for import vimscript from current buffer
- Fix vundle ftdetect issue based on VundleVim/Vundle.vim#16

Signed-off-by: jensenzhang <jingxuan.n.zhang@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants