Open Popkornium18 opened 3 years ago
The way Topgrade checks for failure is by checking the program's exit code, as it does for Vim too. If you're not seeing an error it means that Vim returned 0 dispite the failure. this is the Vim script used to upgrade packages. I'm not a Vim expert in any way. Does anyone know of a way to fix the script to cause Vim to return non-zero exist code on errors?
I am not sure why this sometimes fails. When I run topgrade --only vim
it works but when I run it all together it doesn't.
I don't think the vim upgrade is failing but something is calling a git log (git log --pretty=format:%h HEAD...HEAD@{1}
) which opens a prompt or an pager which is not closed. I can press y to retry as much as I want but no new processes are created but when I press once enter topgrade just continues.
@r-darwish to exit with a non 0 exit status, use cq
(see :help cq
in vim), also, please see #756 for fixing issues with Packer specifically)
EDIT: @wbthomason #756 doesn't actually fix Packer (not for me at least).
@Corey-Keller Can you elaborate (maybe over at #756)?
@wbthomason can done!
I just realized that topgrade never upgraded my neovim plugins but still reported that everything went fine. It just says:
However if I dry run topgrade and manually run the command (on Arch) this happens:
Additional details:
On Ubuntu:
On Arch: