Pathogen does not load plugins

Question

The pathogen does not work for me. I follow Adam Low's tips here (and a few others) without any success ...

My vimrc:

filetype off call pathogen#runtime_append_all_bundles() filetype plugin indent on set nocompatible syntax on set tabstop=2 set smarttab set shiftwidth=2 set autoindent set expandtab set number colorscheme darkblue 

The content of .vim is ls .vim/* :

 .vim/autoload: pathogen.vim .vim/bundle: nerdcommenter/ vim-haml/ vim-surround/ vim-endwise/ vim-rails/ vim-vividchalk/ 

All plugins in the kit were installed by cloning them from GitHub to the bundle directory.

I tried with pathogens 1.1 and 1.2 and even the latest from GitHub without any results. Vividchalk, Vim-rails and nerdcommenter do not work. I have very little experience with other connectors, so I am not sure about them, but I believe that they do not work either.

I am using ArchLinux, vim 7.2.385-1 (not the last, because the latter requires the installation of ruby1.9, but still 7.2). It was installed through pacman, the ArchLinux package manager. No vim plugins were installed in any other way than using the pathogen (I even reinstalled the vim package with the /usr/share/vim cleanup).

What am I doing wrong?

EDIT:

• /etc/vimrc http://hpaste.org/fastcgi/hpaste.fcgi/view?id=29685#a29685
• /usr/share/vim/vimfiles/archlinux.vim http://hpaste.org/fastcgi/hpaste.fcgi/view?id=29686#a29686

Answer 1

This is apparently a common problem caused by the vimrc "system" in some settings of the filetype on distribution before installing the pathogen. Thus, turning it off and on again causes the plugins to load correctly:

  call pathogen#runtime_append_all_bundles() filetype off syntax on filetype plugin indent on 

More details here .

Answer 2

I had a similar problem. The pathogen downloaded some of my plugins, not all of them. After some trying and guessing that I discovered (I don’t know if the documentation mentions it), there should be another folder named plugin in each bundle/'plugin_name' folder that contains the * .vim file.

Then, when vim starts to look, not in a pack, but in those folders inside the package that contain the folder called the plugin ... and will create other folders (in each folder of the plugin).

So, if the plugin is just a .vim file, create a folder for it ...

instead:

 ~/.vim/bundle/vimexplorer/vimExplorer.vim 

you need:

 ~/.vim/bundle/vimexplorer/plugin/vimExplorer.vim 

And everything works like a charm.

Answer 3

I am having problems loading certain plugins: in particular, plugins with the plugin subdirectory. For example, on a new installation of MacVim, the plugin in ~/.vim/bundle/surround/plugin/surround.vim not loaded, although ~/.vim/bundle/surround appeared in the output :scriptnames .

The problem was that I was loading Pathogen into .gvimrc and not .vimrc . For any reason, subdirectories in .vim/bundle/*/plugin will not load if you do this, so do it in .vimrc !

I discovered a problem on github - I don’t know if it can be made to work even if it boots from .gvimrc , but at least there should be some warning in the documentation for idiots like me.

Answer 4

If your .vim is based on the git repository and submodules, DO REMEMBER to run git submodule init and git submodule update after cloning the repo. i.e.

 git submodule init git submodule update 

I had the same error, and I tried all of the above, but that didn't work. Until I initialized and updated the git submodules.

Hope this helps anyone who has a similar bug.

Answer 5

Perhaps Arch default vimrc (possibly /etc/vim/vimrc ) does not work well with Pathogen. Try starting Vim without loading the configuration files:

 vim -u NONE 

and then load vimrc from inside vim:

 :so ~/.vimrc 

Do plugins work?

Answer 6

Fixed with (mattn and tpope) after raising the issue via github

 set nocp call pathogen#infect() syntax on filetype plugin indent on call pathogen#infect() 

see https://github.com/tpope/vim-pathogen/issues/50#issuecomment-3137909

Answer 7

My environment is Vim 7.3.35 and Ubuntu 11.04.

I spent some time trying to solve it. I am cloning a project https://github.com:r00k/dotfiles and follow the installation instructions.

When starting vi a received commented

E117: Unknown function: pathogen # runtime_append_all_bundles

and solution:

filetype off

call pathogen # runtime_append_all_bundles ()

filetype on

does not work.

I found a .vim symbolic link in my home directory, where it is not installed properly. The installation of the script made a .vim DIRECTORY with a vim symbolic link inside it, pointing to my .dotfiles / vim . The solution was to remove the .vim directory and create a .vim symbolic link indicating .dotfiles / vim .

A saved the file type off / on in my .vimrc .

Answer 8

 filetype off call pathogen#runtime_append_all_bundles() call pathogen#helptags() 

Answer 9

Try checking your execution path using the command:: install runtimepath? The first entry should be something like ~ / .vim.

My problem with loading plugins / pathogens was that I placed the vim environment in ~ / .dotfiles / vim, where my vimrc and the rest of the stuff (plugins, etc.) live. After creating a symbolic link to ~ / .dotfiles / vim / vimrc in ~ / .vimrc, I forgot to make a second symbolic link ~ / .vim → ~ / .dotfiles / vim /, which made vim get confused because it was looking for material in ~ / .vim (default). After I made the correct symbolic link, everything appeared in the right place.

I hope this helps someone who has forgotten about the second symbolic link, like me -)

Answer 10

Instead of call pathogen#runtime_append_all_bundles() I used call pathogen#infect('~/.vim/bundle') and it worked for me.

Answer 11

I had the same issue with Ubuntu. The magazine was:

 linha 4: executando "/usr/share/vim/vim73/ftoff.vim" Erro detectado ao processar /usr/share/vim/vim73/ftoff.vim: linha 11: E216: Grupo ou evento inexistente: filetypedetect * fim da execução de /usr/share/vim/vim73/ftoff.vim 

The solution was to add "\ n" s to the end from the file / usr / share / vim / vim 73 / ftoff.vim in order to execute it correctly.

Answer 12

 set nocp call pathogen#infect() syntax on filetype plugin indent on call pathogen#infect() 

This helped me fix the problem, I can not leave a comment on other peoples, however, thanks for sending the code above.

Answer 13

I have it like this:

be silent! call pathogen # runtime_append_all_bundles ()

Answer 14

After spending a long time waaaay trying to solve this problem with nerd-commenter / pathogen, I broke down and just used the Debian OS for the nerd-commenter plugin:

 vim-addons install nerd-commenter 

If you work in Debian and need to get back to work, give it a try. You probably need the "vim-addon-manager" and "vim-scripts" packages installed from apt if you don't already have it.

Answer 15

To complete, I will add my solution for this problem.

I just renamed my ~ / .gvimrc file to ~ / .vimrc and all my problems were resolved. I literally copied my .vim and my .gvimrc from linux and made this change, and everything works as expected.

Answer 16

I had the same problem. I tried all possible combinations.

Finally, I found that if I use mksession to save the Vim workspace and load it onto Vim, it caused the pathogen to not load new plugins that I put in the package folder.

After installing a new plugin, I now always delete my session file and run Vim fresh, and each plugin loads normally.

 filetype off set nocompatible set laststatus=2 execute pathogen#infect() syntax on filetype plugin indent on 

Answer 17

In my case, I cloned to the ~ / dotfiles folder, but vun is looking for the ~ / .vim folder, as a result, it did not have any plugins or color schemes to solve the problem, I did this:

 ln -s ~/.dotfiles ~/.vim 

Answer 18

I had the same problem solved by copying this file to ~ / .vim / autoload: https://github.com/sontek/dotfiles/blob/master/_vim/autoload/pathogen.vim

Answer 19

I ran into the same problem, finally after many google searches and setting up the vimrc file I found a solution. Hope the following code snippet solves the problem.

set nocp source /home/ameet/.vim/autoload/pathogen.vim "location of my pathogen.vim call pathogen#infect() call pathogen#helptags()