From 1c28b7db14f04e722d5b5014289f41acb986e0f4 Mon Sep 17 00:00:00 2001 From: zuqini Date: Wed, 15 Apr 2026 09:57:05 +0000 Subject: [PATCH] docs: add migration notes for install feedback and passive libraries Surfaces two gotchas hit by users migrating from lazy.nvim: - vim.pack install/update progress lives in :messages and is hidden when cmdheight = 0 (issue #11) - lazy.nvim's community specs silently force plenary.nvim and similar passive libraries to lazy = true; zpack respects the user spec as written, so lazy must be set explicitly (issue #7) --- docs/tips.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/tips.md b/docs/tips.md index 8d830e7..22ed94e 100644 --- a/docs/tips.md +++ b/docs/tips.md @@ -6,6 +6,8 @@ Most of your lazy.nvim plugin specs will work as-is with zpack. However, zpack f - **version pinning**: lazy.nvim's `version` field maps to zpack's `sem_version`. See [Spec Reference](spec.md) and [version pinning examples](examples.md#version-pinning-for-lazynvim-compatibility) - **dev mode**: Use `src = vim.fn.expand('~/projects/my_plugin.nvim')` for local development - **profiling**: Use `nvim --startuptime startuptime.log`. Also refer to example [Neovim Profiler script](https://gist.github.com/zuqini/35993710f81983fbfa6baca67bdb32ed) +- **install/update feedback**: `vim.pack` surfaces progress via `:messages` (e.g. `vim.pack: Downloading updates (0/83)`) instead of a dedicated UI. These messages are hidden if you have `vim.opt.cmdheight = 0` — raise it, check `:messages`, or route them through a notifier like [snacks.notifier](https://github.com/folke/snacks.nvim), [nvim-notify](https://github.com/rcarriga/nvim-notify), or [noice.nvim](https://github.com/folke/noice.nvim) +- **passive libraries**: lazy.nvim's community specs silently force utility libraries like `plenary.nvim` to `lazy = true` regardless of your config. zpack respects your spec as-written, so set `lazy = true` explicitly on pure-dependency plugins you don't want eager-loaded ## Compatibility Notes