aboutsummaryrefslogtreecommitdiff
path: root/lua/plugins.lua
diff options
context:
space:
mode:
authorjdhao <jdhao@hotmail.com>2021-07-09 01:33:09 +0800
committerjdhao <jdhao@hotmail.com>2021-07-09 01:49:17 +0800
commit6b3e41419a68e1294e1e33bc295d652df62208a5 (patch)
treee8b14ef3a94688e44808c8d53cf255065a07c5ab /lua/plugins.lua
parent51264eab77e9bddbc9f20ccecc95623cb94f9e6e (diff)
Ppdate packer settings for Semshi
If Semshi is set to opt plugin, when we run PackerUpdate, the command `: UpdateRemotePlugins` will be run. At this time, Semshi is not in the runtimepath, so its manifest will not be generated in rplugin.vim (located under ~/.local/share/nvim/rplugin.vim). So when we open a Python file afterwards, although Semshi is in runtimepath, but its manifest is missing, so we see error that command `Semshi enable` is not found. So after loading this plugin, i.e., when we open a Python source file, we need to run UpdateRemotePlugins so that semshi can work correctly.
Diffstat (limited to 'lua/plugins.lua')
-rw-r--r--lua/plugins.lua2
1 files changed, 1 insertions, 1 deletions
diff --git a/lua/plugins.lua b/lua/plugins.lua
index 393c88a..e58655b 100644
--- a/lua/plugins.lua
+++ b/lua/plugins.lua
@@ -34,7 +34,7 @@ require('packer').startup(
-- Python syntax highlighting and more
if (vim.g.is_mac == 1) or (vim.g.is_win == 1) then
- use {'numirias/semshi', run = ':UpdateRemotePlugins', ft = 'python'}
+ use {'numirias/semshi', ft = 'python', config = 'vim.cmd [[UpdateRemotePlugins]]'}
end
-- Python indent (follows the PEP8 style)