aboutsummaryrefslogtreecommitdiff
path: root/runtime/ftplugin/python.vim
diff options
context:
space:
mode:
authorEvgeni Chasnovski <evgeni.chasnovski@gmail.com>2025-12-28 18:07:32 +0200
committerEvgeni Chasnovski <evgeni.chasnovski@gmail.com>2025-12-28 18:39:26 +0200
commitc339b83a4ab99d170776b01c4e4ca4e550f45bba (patch)
tree0318ee32fd6a248e143e21cb2165b442efbad6ef /runtime/ftplugin/python.vim
parentf5707a9c42a6f0efd0d7abaa1e5caf62eab21aea (diff)
downloadrneovim-c339b83a4ab99d170776b01c4e4ca4e550f45bba.tar.gz
rneovim-c339b83a4ab99d170776b01c4e4ca4e550f45bba.tar.bz2
rneovim-c339b83a4ab99d170776b01c4e4ca4e550f45bba.zip
feat(pack): hint in confirmation buffer that plugin is not active
Problem: After `vim.pack.update()` it is not clear if plugin is active or not. This can be useful to detect cases when plugin was removed from 'init.lua' but there was no `vim.pack.del()`. Solution: Add ` (not active)` suffix with distinctive highlighting to header of plugins that are not active. It will also be shown in in-process LSP document symbols to have quick reference about which plugins are not active.
Diffstat (limited to 'runtime/ftplugin/python.vim')
0 files changed, 0 insertions, 0 deletions