Open kiryph opened 8 years ago
I'll have to look into this in more detail, but it does sound like you've figured out the issue. If you can put a PR together that fixes this, I will merge it.
Long ago I put a TODO
in here:
https://github.com/cjrh/vim-conda/blob/master/plugin/vim-conda.vim#L161
Perhaps that is what you need after all? (or something similar. The details are complicated, I'll need to think about it more.)
Thanks for your feedback. Right now I do not have the time to create a PR. For now I will stick to the hardcoded solution in my vimrc:
let s:custom_sys_paths = system('~/miniconda-py2/bin/python -c "import sys;print sys.path"')
python import vim;import sys; import ast; sys.path.extend(ast.literal_eval(vim.eval("s:custom_sys_paths")))
No problem. Thanks again for the report 👍
I am using MacVim on OSX 10.10.5 and I have installed miniconda to
$HOME/miniconda-py2
. I also have adjusted$PATH
so thatI would like to enable the default root environment of miniconda in vim for jedi autocompletion.
My vim configuration is following:
Jedi-Completion
does not list anything and returns:
-- Omni completion (^O^N^P) Pattern not found
UPDATE
Adding to vimrc:
python sys.path.append("/Users/kiryph/miniconda-py2/lib/python2.7/site-packages/")
resolves it.import numpy.
opens now a completion menu.However, I think the purpose of your plugin is to automate this and in particular setting the
sys.path
identical to the desired python interpreter./usr/bin/python -c "import sys;print sys.path"
and/Users/kiryph/miniconda-py2/bin/python -c "import sys;print sys.path"
do not have many entries in common.I was trying the following, but I prefer much more changing it with your plugin.
I think choosing
root
should not mean to deactivate but set it to the root environment of conda and deactivate means using the defaults identical to those as ifvim-conda
would not be installed.