-
-
Notifications
You must be signed in to change notification settings - Fork 372
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
Add install instruction for plain Vim 8 #1042
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -79,12 +79,17 @@ You need a VIM version that was compiled with Python 2.7 or later | |
|
||
Manual installation | ||
------------------- | ||
The plugin uses `git` submodules to fetch the vendored versions of Jedi. | ||
|
||
You might want to use `pathogen <https://github.com/tpope/vim-pathogen>`_ or | ||
`Vundle <https://github.com/gmarik/vundle>`_ to install jedi-vim. | ||
To install using standard Vim 8 plugin system: | ||
|
||
.. code-block:: sh | ||
|
||
The first thing you need after that is an up-to-date version of Jedi. Install | ||
``git submodule update --init --recursive`` in your jedi-vim repository. | ||
mkdir -p ~/.vim/pack/git-plugins/start | ||
git clone --recursive https://github.com/davidhalter/jedi-vim.git ~/.vim/pack/git-plugins/start/jedi-vim | ||
|
||
Or you might want to use `pathogen <https://github.com/tpope/vim-pathogen>`_ or | ||
`Vundle <https://github.com/gmarik/vundle>`_ to install jedi-vim. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We can merge this with the rest to only include instructions for vim-plug then. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @abitrolly what do you think? Should I/we go ahead and do so here? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I am not a user of |
||
|
||
Example installation command using Pathogen: | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
btw: do you know if there is a preferred/recommended way to update Vim packages?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no :D
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@abitrolly do you know? How do you keep them updated?
(as for me: I am using vim-plug basically, but given the amount of local changes I still update them manually in general, i.e. by updating/merging into the Git checkout)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I update with plain
git
.