search

tpope / vim-pathogen

pathogen.vim: manage your runtimepath
http://www.vim.org/scripts/script.php?script_id=2332
Vim License
12.12k stars 1.16k forks source link

Pluginbundle not actually working for some plugins #187

Closed frioux closed 7 years ago

frioux commented 7 years ago

I am sure this is something I am doing wrong, but I'm at my wits end here.

I sometimes use sessions as a way to have settings for a given project. For example for our salt repo at work my session is:

call pathogen#infect('/home/frew/code/vim-salt-plugins/{}')

source /home/frew/.vvar/sessions/_salt

And the latter is an Obsession built session. It works perfectly fine. Until I try to add a plugin that adds a file to the plugin subdirectory. So for example syntax and and ftplugins work fine in the vim-salt-plugins directory, but if I add Eunuch to the bundle, the command (like :Remove) do not get added.

Here is the &rtp, to be clear:

/home/frew/code/vim-salt-plugins/eunuch,/home/frew/code/vim-salt-plugins/salt-vim,/home/frew/code/vim-salt-plugins/vim
-jinja,/home/frew/.vim,/home/frew/.vim/bundle-lua/neocomplete,/home/frew/.vim/bundle-python/editorconfig,/home/frew/.v
im/bundle-python/ultisnips,/home/frew/.vim/bundle/FastFold,/home/frew/.vim/bundle/IndentAnything,/home/frew/.vim/bundl
e/airline,/home/frew/.vim/bundle/better-whitespace,/home/frew/.vim/bundle/colors-solarized,/home/frew/.vim/bundle/comm
entary,/home/frew/.vim/bundle/csv,/home/frew/.vim/bundle/ctrlp,/home/frew/.vim/bundle/denite,/home/frew/.vim/bundle/ex
change,/home/frew/.vim/bundle/fugitive,/home/frew/.vim/bundle/fugitive-gitlab,/home/frew/.vim/bundle/gitgutter,/home/f
rew/.vim/bundle/go,/home/frew/.vim/bundle/goyo,/home/frew/.vim/bundle/inkpot,/home/frew/.vim/bundle/l9,/home/frew/.vim
/bundle/lastplace,/home/frew/.vim/bundle/lost,/home/frew/.vim/bundle/matchit,/home/frew/.vim/bundle/matchmaker,/home/f
rew/.vim/bundle/obsession,/home/frew/.vim/bundle/pathogen,/home/frew/.vim/bundle/perl,/home/frew/.vim/bundle/projectio
nist,/home/frew/.vim/bundle/python,/home/frew/.vim/bundle/quick-scope,/home/frew/.vim/bundle/repeat,/home/frew/.vim/bu
ndle/sleuth,/home/frew/.vim/bundle/splitjoin,/home/frew/.vim/bundle/surround,/home/frew/.vim/bundle/tabular,/home/frew
/.vim/bundle/terminus,/home/frew/.vim/bundle/textobj-between,/home/frew/.vim/bundle/textobj-entire,/home/frew/.vim/bun
dle/textobj-underscore,/home/frew/.vim/bundle/textobj-user,/home/frew/.vim/bundle/unimpaired,/home/frew/.vim/bundle/vi
negar,/home/frew/.vim/bundle/visual-star-search,/home/frew/.vim/bundle/wipeout,/var/lib/vim/addons,/usr/share/vim/vimf
iles,/usr/share/vim/vim80,/usr/share/vim/vimfiles/after,/var/lib/vim/addons/after,/home/frew/.vim/bundle/tabular/after
,/home/frew/.vim/bundle-python/ultisnips/after,/home/frew/.vim/after

I did put set sessionoptions-=options in my vimrc based on the README to pathogen and even looked through the actual session file in question to see if rtp/runtimepath was there, but it's not.

Any ideas?

tpope commented 7 years ago

Sessions load after plugins are already active, so changing 'runtimepath' in one will have no effect on what plugins are loaded.

frioux commented 7 years ago

Thanks.

-- Sent from a telephone. Pardon my brevity.

On May 20, 2017 9:25 AM, "Tim Pope" notifications@github.com wrote:

Closed #187 https://github.com/tpope/vim-pathogen/issues/187.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tpope/vim-pathogen/issues/187#event-1090585267, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAf4_qi0Zc3RH_wEJDjJGc85qCFbIfsks5r7xQAgaJpZM4NhUDc .