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
Generate plugins with only_config and missing url and path in packer_compiled.lua
(From what I can tell, in my case, this seems to happen when some plugins use "after" a specific plugin, e.g.: some plugins are loaded with after = { "auto-session" },, which seem to result in the following packer_compiled.lua:
(Missing url and path)
2. run :PackerStatus
3. Try to hit <cr> on the plugin name
Actual behaviour
Once you hit <cr> on the plugin name, the first time it will display the information from the plugin above, e.g.:
(Here showing ansible-vim, despite hitting enter on auto-session)
Hitting <cr> again on auto-session will simply make it disapear:
Expected behaviour
Hitting <cr> on the plugin name displays information about the plugin or, if no information is available, either display error or nothing.
Please note that the fact that the plugin is missing url and path from packer_compiled.lua and global variable "packer_plugins"
does not only cause problems with :PackerStatus, but may also cause problems for other plugins using this, for example: 4513ECHO/vim-readme-viewer#2
I am not sure if there is a specific reason for not putting url and path in these scenarios, but it could be helpful to be consistent across the board and always have this information.
nvim --version
:git --version
:git version 2.34.1
alacritty 0.10.0-dev (6d1a63ef)
Steps to reproduce
(From what I can tell, in my case, this seems to happen when some plugins use "after" a specific plugin, e.g.: some plugins are loaded with
after = { "auto-session" },
, which seem to result in the following packer_compiled.lua:(Missing url and path)
2. run
:PackerStatus
3. Try to hit
<cr>
on the plugin nameActual behaviour
Once you hit
<cr>
on the plugin name, the first time it will display the information from the plugin above, e.g.:(Here showing ansible-vim, despite hitting enter on auto-session)
Hitting
<cr>
again on auto-session will simply make it disapear:Expected behaviour
Hitting
<cr>
on the plugin name displays information about the plugin or, if no information is available, either display error or nothing.Please note that the fact that the plugin is missing url and path from packer_compiled.lua and global variable "packer_plugins"
does not only cause problems with
:PackerStatus
, but may also cause problems for other plugins using this, for example: 4513ECHO/vim-readme-viewer#2I am not sure if there is a specific reason for not putting url and path in these scenarios, but it could be helpful to be consistent across the board and always have this information.
packer files
Plugin specification file(s)
Post or link your plugin specification files here, if you aren't able to provide a minimal
reproducer
packer_compiled.lua
Post the contents of ~/.cache/nvim/packer.nvim.log here
No error related to this in logs.
The text was updated successfully, but these errors were encountered: