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

support for pythonx-directory (neovim) #144

btipling opened this issue Oct 29, 2014 · 2 comments


Copy link

commented Oct 29, 2014

In vim, if there are directories in ~/.vim named "python2", "python3" or "pythonx" vim will look through these directories for python scripts and load them.

:he pythonx-directory

If I have a project in ~/.vim/bundle that has any of the above directories, the python scripts in any of them are not being loaded by pathogen. I tried to look through the pathogen source code but nothing was obvious to me.

While I think they are not used much in regular vim, these directories are critical for making python plugins for neovim. It might be the case that neovim's changes here are incompatible with pathogen or perhaps pathogen hadn't supported these directories before? Here is a discussion with details about how neovim and the pythonx directories work (includes an example of snake in nvim):

I should mention that pathogen works great with neovim, all of my vim plugins work seamlessly via pathogen. I have not tried to make use of the pythonx directories in regular vim.


This comment has been minimized.

Copy link

commented Nov 5, 2014

@btipling soon there will be changes to the python plugin infrastructure, and pythonx will no longer be required, so this will no longer be a problem

@tpope tpope closed this Nov 5, 2014


This comment has been minimized.

Copy link

commented Nov 7, 2014

Ok, thank you for the update!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.