This makes it work in tests. Using `<expr>` instead will not trigger
the expansion of the mapping.
This is likely a bug in vim-vspec; I have tried 1.4.1 (currently pinned)
and 1.6.1.
This adds g:jedi#goto_command, and uses `<Leader>d` by default for it -
the old default for `g:jedi#goto_definitions_command`, which is now
empty.
It will try `script.goto_definitions()` first, and falls back to
`script.goto_assignments()` for builtins.
Closes https://github.com/davidhalter/jedi-vim/pull/407
This adds a visual mode map for renaming, which asks for the new name
via input().
`rename` itself could be changed to use `input()`, too - but I've left
it for now.
- jedi#init_python is used to init the Python environment.
- jedi#setup_py_version is the single point where PythonJedi is
defined, and will configure `PythonJedi` to output an error in case
initialization failed.
- jedi#force_py_version_switch will throw an error when
g:jedi#force_py_version is not handled (e.g. invalid or "auto" and
unresolved).
- When g:jedi#force_py_version is provided, it will be used always.
- Use WarningMsg highlight for errors, which are centralized and
handled through exceptions.
- mapping operator-pending-mode and selection-mode has undesirable
side-effects, and isn't actually used by jedi-vim.
- also, wrap 'for' loops in s:init() functions to avoid polluting the
global namespace ('for key in keys' assigns g:key).
I find the long line that pops up in the command-line whenever I press
`.` a bit distracting, and it would potentially overwrite other useful
information displayed in there. This change silences the dot completion
commands.
