Hi there. Thank you for creating packer.nvim. I am a former user of vim-plug, and just finished migrating to packer, and for the most part have really enjoyed the experience.
While migrating, some of my packages failed to install correctly. Here is the information the installation log sidebar presents to me, after expanding the relevant nodes using <CR>:
I have a few problems with this user experience:
No information presented about what went wrong:
Did we fail to pull the source code of the plugin? Does the result not look like a plugin? Did the evaluation of run or config hook(s) fail? What (if any) error messages were emitted?
It would be ideal if this information could be presented to the user alongside the URL and commit metadata.
Retry appears to do nothing:
At the bottom, I am presented with the message "Press 'R' to retry failed operations". However, pressing R appears to do nothing. I am not sure if there really is nothing happening, or if there is some kind of silent retry attempt going on behind the scenes, or if the retry attempt is so fast that I can't observe any change in the UI.
More immediate feedback about what is happening would be useful (assuming the feature is working correctly in my setup and anything is happening at all).
Installation is non-transactional:
If at this point I close the editor, reopen it, and run :PackerStatus, the plugin appears to be under the impression that everything is fine. Running :PackerInstall or :PackerSync now appears to be a no-op (I don't know if anything is actually happening behind the scenes), and will not visibly reattempt to install the packages that failed on the prior attempt.
Assuming the setup hook for a package limits itself to modifying the content of the plugin directory, it would be ideal if a failed attempt to install a package had no effect on my system. This means that the contents of a package that failed to install correctly should be deleted from disk, and any leftover side effects should be limited to those explicitly introduced in a post-install hook. It also means that when I close the editor, reopen it, and attempt to run :PackerInstall, it should attempt to install any packages whose installation failed on a prior attempt, as if I had never attempted to install them at all.
I am not sure if it's best to create separate issues for these problems, didn't want to spam the tracker, but I can do so if you feel this is appropriate.
Hi there. Thank you for creating packer.nvim. I am a former user of vim-plug, and just finished migrating to packer, and for the most part have really enjoyed the experience.
While migrating, some of my packages failed to install correctly. Here is the information the installation log sidebar presents to me, after expanding the relevant nodes using
<CR>:I have a few problems with this user experience:
No information presented about what went wrong:
Did we fail to pull the source code of the plugin? Does the result not look like a plugin? Did the evaluation of
runorconfighook(s) fail? What (if any) error messages were emitted?It would be ideal if this information could be presented to the user alongside the URL and commit metadata.
Retry appears to do nothing:
At the bottom, I am presented with the message "Press 'R' to retry failed operations". However, pressing R appears to do nothing. I am not sure if there really is nothing happening, or if there is some kind of silent retry attempt going on behind the scenes, or if the retry attempt is so fast that I can't observe any change in the UI.
More immediate feedback about what is happening would be useful (assuming the feature is working correctly in my setup and anything is happening at all).
Installation is non-transactional:
If at this point I close the editor, reopen it, and run
:PackerStatus, the plugin appears to be under the impression that everything is fine. Running:PackerInstallor:PackerSyncnow appears to be a no-op (I don't know if anything is actually happening behind the scenes), and will not visibly reattempt to install the packages that failed on the prior attempt.Assuming the setup hook for a package limits itself to modifying the content of the plugin directory, it would be ideal if a failed attempt to install a package had no effect on my system. This means that the contents of a package that failed to install correctly should be deleted from disk, and any leftover side effects should be limited to those explicitly introduced in a post-install hook. It also means that when I close the editor, reopen it, and attempt to run
:PackerInstall, it should attempt to install any packages whose installation failed on a prior attempt, as if I had never attempted to install them at all.I am not sure if it's best to create separate issues for these problems, didn't want to spam the tracker, but I can do so if you feel this is appropriate.