You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have opt packages that I only packadd to vim when loading specific filetypes (e.g. I have the line vim.cmd "packadd emmet-vim" in ftplugin/html.lua). While I can do :help emmet after loading an HTML file into a buffer, I can't find the same doc with :CocList helptags.
I'm adding this to this repo because the problem I'm experiencing is related to the helptags list. Based on a couple of quick greps, I think the problem might be that coc.nvim's workspace.env doesn't update, so workspace.env.runtimepath doesn't reflect changes to &rtp. Do I have that right?
The text was updated successfully, but these errors were encountered:
Ok, interesting. I can see that the OptionSet autocmd gets triggered when using :packadd from the command line, but not if it's being called within a ftplugin/*.lua or ftplugin/*.vim file. I don't know if this is a bug with neovim or what is supposed to happen.
Hi,
I have opt packages that I only
packadd
to vim when loading specific filetypes (e.g. I have the linevim.cmd "packadd emmet-vim"
inftplugin/html.lua
). While I can do:help emmet
after loading an HTML file into a buffer, I can't find the same doc with:CocList helptags
.I'm adding this to this repo because the problem I'm experiencing is related to the helptags list. Based on a couple of quick
grep
s, I think the problem might be that coc.nvim'sworkspace.env
doesn't update, soworkspace.env.runtimepath
doesn't reflect changes to&rtp
. Do I have that right?The text was updated successfully, but these errors were encountered: