Daniel Hahler
Daniel Hahler
Yeah, having all the different options of installment are a recurring issue with READMEs across (Neo)Vim plugins. I think people in general should be aware how to install a plugin...
It works for me as expected: ```python import os from os import pathsep as some_alias os.path os.pathsep some_alias() ``` => ``` import os from os import pathsep as asdf os.path...
> observe that instances of `some_library.some_symbol` are also renamed. Please elaborate. Do you mean they are replaced in the `some_library` module / code?
Yeah, that would likely be even better to use. Neovim has it also (had it before, and Vim uses a different API again...).
Started playing with using Neovim's floating windows. Based on https://github.com/davidhalter/jedi-vim/pull/652.
> Syntax highlighting signatures maybe? It still uses the existing concealing (but in a separate window, not messing with the current buffer anymore, which might interfere with indenting etc).
Note: textprop is used for usages already: https://github.com/blueyed/jedi-vim/blob/6ca603ffdf989cfc7426485252a77529951ea47e/pythonx/jedi_vim.py#L658-L669
@davidhalter This is WIP, but quite usable already. You can use `let g:jedi#environment_paths = [$HOME . '/.pyenv/versions]'` to get all pyenv version in the completion for `:JediUseEnvironment`.. :) (a bit...
Updated to use https://github.com/davidhalter/jedi/pull/1176.
@davidhalter Would appreciate some feedback on this early stage for the next iteration.