Echo informative messages when a Packer* command is finished
For the first point, now packer are capable to:
automatically generate snapshot files on sync/update/remote/install
allow using functions to specify the name of snapshot files and snapshot path
generate human-readable .json with each package in a seperate line and is always sorted in ascending order, so that it is easier to track with version control tools like git
PackerSnapshot can take any number of arguments (nargs=*). When no argument is given, packer will automatically fall back to the default snapshot name
add .json appendix for the default snapshot name
use config.snapshot.name, config.snapshot.path, and config.snapshot.auto, and config.snapshot.silent_overwrite to configure snapshot behavior
More human-redable
Clearer version control
The the second point:
new user autocmds PackerInstallComplete, PackerUpdateComplete, PackerCleanComplete, PackerSnapshotComplete, PackerSnapshotRollbackComplete, PackerSnapshotDeleteComplete, and PackerCompileComplete are added
For the third point:
in the function packer.on_complete a notification is added to inform user of the completion of a task (i.e. sync, install, update, snapshot ...)
Some side notes: thank you for this awesome plugin, I've used it for over a year and love it. For me it is the fastest package manager since I can disable packer itself and only load the compiled file if it is there. Taking advantage of this feature packer is noticeably faster than lazy.nvim (15 ~ 25ms for packer and 25~35ms for lazy.nvim, though both is fast enough). Use packer as a 'compiler' also means that the startup time will not increase when the config file is broken into smaller files, as long as the specs are the same. Hoping packer keep thriving and keep fast in the future :)
Bekaboo
commented
1 year ago
These commits mainly aims to:
Packer*command is finishedFor the first point, now packer are capable to:
.jsonwith each package in a seperate line and is always sorted in ascending order, so that it is easier to track with version control tools like gitPackerSnapshotcan take any number of arguments (nargs=*). When no argument is given, packer will automatically fall back to the default snapshot name.jsonappendix for the default snapshot nameconfig.snapshot.name,config.snapshot.path, andconfig.snapshot.auto, andconfig.snapshot.silent_overwriteto configure snapshot behaviorThe the second point:
PackerInstallComplete,PackerUpdateComplete,PackerCleanComplete,PackerSnapshotComplete,PackerSnapshotRollbackComplete,PackerSnapshotDeleteComplete, andPackerCompileCompleteare addedFor the third point:
packer.on_completea notification is added to inform user of the completion of a task (i.e. sync, install, update, snapshot ...)Some side notes: thank you for this awesome plugin, I've used it for over a year and love it. For me it is the fastest package manager since I can disable packer itself and only load the compiled file if it is there. Taking advantage of this feature packer is noticeably faster than lazy.nvim (15 ~ 25ms for packer and 25~35ms for lazy.nvim, though both is fast enough). Use packer as a 'compiler' also means that the startup time will not increase when the config file is broken into smaller files, as long as the specs are the same. Hoping packer keep thriving and keep fast in the future :)