Skip to content

Commit ead0dca

Browse files
doc: fix Indentation and underline length #454
Building the docs raised errors previously
1 parent fbf0ec1 commit ead0dca

File tree

2 files changed

+16
-14
lines changed

2 files changed

+16
-14
lines changed

docs/usage/python-plugin-api.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ The API extensions are accessible no matter if the traditional ``:python`` inter
77
as discussed on :doc:`remote-plugins`.
88

99
Nvim API methods: ``vim.api``
10-
-----------
10+
-----------------------------
1111

1212
Exposes Neovim API methods.
1313
For instance to call ``nvim_strwidth``:
@@ -38,7 +38,7 @@ same way, but python will not wait for it to finish, so the return value is
3838
unavailable.
3939

4040
Vimscript functions: ``vim.funcs``
41-
-------------
41+
----------------------------------
4242

4343
Exposes vimscript functions (both builtin and global user defined functions) as a python namespace.
4444
For instance to set the value of a register:
@@ -51,7 +51,7 @@ These functions can also take the ``async_=True`` keyword argument, just like AP
5151
methods.
5252

5353
Lua integration
54-
-----------
54+
---------------
5555

5656
Python plugins can define and invoke lua code in Nvim's in-process lua
5757
interpreter. This is especially useful in asynchronous contexts, where an async

docs/usage/remote-plugins.rst

Lines changed: 13 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -75,23 +75,25 @@ find your plugin. You can now invoke Neovim:
7575
7676
Then run ``:UpdateRemotePlugins`` and your plugin should be activated.
7777

78-
In case you run into some issues, you can list loaded plugins:
78+
In case you run into some issues, you can list your loaded plugins from inside
79+
Neovim by running ``:scriptnames`` like so.:
7980

80-
.. code-block:: console
81+
.. code-block:: vim
8182
8283
:scriptnames
83-
1: ~/path/to/your/plugin-git-repo/vimrc
84-
2: /usr/share/nvim/runtime/filetype.vim
85-
...
86-
25: /usr/share/nvim/runtime/plugin/zipPlugin.vim
87-
26: ~/path/to/your/plugin-git-repo/plugin/lucid.vim
84+
1: ~/path/to/your/plugin-git-repo/vimrc
85+
2: /usr/share/nvim/runtime/filetype.vim
86+
...
87+
25: /usr/share/nvim/runtime/plugin/zipPlugin.vim
88+
26: ~/path/to/your/plugin-git-repo/plugin/lucid.vim
8889
89-
You can also inspect the ``runtimepath`` like this:
90+
You can also inspect the ``&runtimepath`` like this:
9091

91-
.. code-block:: console
92+
.. code-block:: vim
9293
9394
:set runtimepath
94-
runtimepath=~/.config/nvim,/etc/xdg/nvim,~/.local/share/nvim/site,...,
95+
runtimepath=~/.config/nvim,/etc/xdg/nvim,~/.local/share/nvim/site,...,
9596
,~/g/path/to/your/plugin-git-repo
9697
97-
98+
" Or alternatively
99+
:echo &rtp

0 commit comments

Comments
 (0)