When vim is compiled with `-python` and `+python3`, jedi-vim generates
errors because of two points in the code which are not compatible with
Python 3 (because of the `str`/`unicode` vs. `bytes`/`str` thing).
Calling `syntax on` will override existing syntax rules with default
ones. This ends up adding a bunch of syntax rules that users have
disabled.
See `:help syntax` for this snippet:
The ":syntax enable" command will keep your current color settings. This
allows using ":highlight" commands to set your preferred colors before or
after using this command. If you want Vim to overrule your settings with
the defaults, use: `:syntax on`
Calling `:syntax enable` doesn't appear to work either. It does the same thing
as `:syntax on`. So the solution implemented here is to conditionally set the
filetype and syntax rules when they aren't already set.
- Replace all occurences of Jedi-Vim/Jedi with jedi-vim/jedi
- Capitalize first letter on bullet points
- oh god how do i english
- Fix wrong description of g:jedi#auto_close_doc option
The usage section feels sort of superfluous. I don't know. >:(
The distinction between jedi#goto() and jedi#fund_definition() was a bit
unclear, so I expanded it a bit.
For now, this is just the README.rst file with appropriate sections. The
content of the file itself is completely unchanged.
Section name suggestions are taken from Steve Losh's Learn Vimscript the
Hard Way [1]. Formatting suggestions are taken from Vim's own
documentation on writing help files (:help help-writing).
The spiffy header was created using the figlet program [2] and the
starwars.flf font found in the figlet fonts database [3].
[1] http://learnvimscriptthehardway.stevelosh.com/chapters/54.html
[2] http://www.figlet.org
[3] http://www.figlet.org/fonts/starwars.flf
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.
David Halter