Marty/dotfiles
1
0
Fork 0
Code Issues 3 Pull requests Projects Releases Wiki Activity
dotfiles/nvim/.config/nvim/lazy-lock.json

74 lines
6.8 KiB
JSON
Raw Normal View History

nvim: Move to lazy.nvim package manager Migrated from packer.nvim to lazy.nvim - it gives really fast loading times, easy lazy loading for any package and a snazzy package manager overview page (invoked through `:Lazy`) which, importantly, all do not rely on a compiled plugin list. In essence it feels like an easier to manage and robust packer replacement (even though packer is a really good manager as well) that is well worth to switch to. Migration was pretty painless as well. One thing I might do in the future is split up the plugin structure itself from a single plugin list (which invokes plugin settings files) to several files containing the plugins and their settings since it might give more structure.
2023-02-10 08:15:56 +00:00
{
"BetterLua.vim": { "branch": "master", "commit": "d2d6c115575d09258a794a6f20ac60233eee59d5" },
nvim: Default to stable versions for plugins Using the lazy option 'version' we default to updating only to the latest stable (semver) version of plugins. This should make it a little more stable in the long run to keep up with plugin updates. Not all plugins support this versioning scheme and for those that do not it just keeps tracking the main branch. Currently from the plugins that support it, only `nvim-lspconfig` needs to be manually kept on the main branch since it is missing the correct lua language server otherwise. This should be a problem of the past with the release of the next version of the plugin.
2023-03-03 11:51:21 +00:00
"LuaSnip": { "branch": "master", "commit": "500981ff6cefc7343e3959ef0f939bd0bfd49ba9" },
"Navigator.nvim": { "branch": "master", "commit": "52225923679ec866651bb0c2e0691374131ec939" },
nvim: Move to lazy.nvim package manager Migrated from packer.nvim to lazy.nvim - it gives really fast loading times, easy lazy loading for any package and a snazzy package manager overview page (invoked through `:Lazy`) which, importantly, all do not rely on a compiled plugin list. In essence it feels like an easier to manage and robust packer replacement (even though packer is a really good manager as well) that is well worth to switch to. Migration was pretty painless as well. One thing I might do in the future is split up the plugin structure itself from a single plugin list (which invokes plugin settings files) to several files containing the plugins and their settings since it might give more structure.
2023-02-10 08:15:56 +00:00
"bats.vim": { "branch": "master", "commit": "6a5d2ef22b0ede503d867770afd02ebb1f97b709" },
"cmp-buffer": { "branch": "main", "commit": "3022dbc9166796b644a841a02de8dd1cc1d311fa" },
nvim: Update plugin lockfile
2023-03-01 16:39:23 +00:00
"cmp-cmdline": { "branch": "main", "commit": "8fcc934a52af96120fe26358985c10c035984b53" },
nvim: Move to lazy.nvim package manager Migrated from packer.nvim to lazy.nvim - it gives really fast loading times, easy lazy loading for any package and a snazzy package manager overview page (invoked through `:Lazy`) which, importantly, all do not rely on a compiled plugin list. In essence it feels like an easier to manage and robust packer replacement (even though packer is a really good manager as well) that is well worth to switch to. Migration was pretty painless as well. One thing I might do in the future is split up the plugin structure itself from a single plugin list (which invokes plugin settings files) to several files containing the plugins and their settings since it might give more structure.
2023-02-10 08:15:56 +00:00
"cmp-latex-symbols": { "branch": "main", "commit": "165fb66afdbd016eaa1570e41672c4c557b57124" },
"cmp-nvim-lsp": { "branch": "main", "commit": "0e6b2ed705ddcff9738ec4ea838141654f12eeef" },
"cmp-nvim-lua": { "branch": "main", "commit": "f3491638d123cfd2c8048aefaf66d246ff250ca6" },
nvim: Update plugin lockfile
2023-03-01 16:39:23 +00:00
"cmp-pandoc-references": { "branch": "master", "commit": "2c808dff631a783ddd2c554c4c6033907589baf6" },
nvim: Move to lazy.nvim package manager Migrated from packer.nvim to lazy.nvim - it gives really fast loading times, easy lazy loading for any package and a snazzy package manager overview page (invoked through `:Lazy`) which, importantly, all do not rely on a compiled plugin list. In essence it feels like an easier to manage and robust packer replacement (even though packer is a really good manager as well) that is well worth to switch to. Migration was pretty painless as well. One thing I might do in the future is split up the plugin structure itself from a single plugin list (which invokes plugin settings files) to several files containing the plugins and their settings since it might give more structure.
2023-02-10 08:15:56 +00:00
"cmp-path": { "branch": "main", "commit": "91ff86cd9c29299a64f968ebb45846c485725f23" },
"cmp-spell": { "branch": "master", "commit": "60584cb75e5e8bba5a0c9e4c3ab0791e0698bffa" },
"cmp-tmux": { "branch": "main", "commit": "984772716f66d8ee88535a6bf3f94c4b4e1301f5" },
"cmp-treesitter": { "branch": "master", "commit": "b40178b780d547bcf131c684bc5fd41af17d05f2" },
nvim: Switch to lsp-zero lsp-zero offers a simple to set-up lsp configuration which is based around the plugins I use anyway (lsp, cmp, luasnip) but integrates them very well. I add a few small quality of life things on top (cmp completion for / search and for vim command mode) as well as a boatload of custom completion sources but otherwise make use of the nice presets. This has de-bloated my _cmp.lua settings somewhat and allows me to have a simple treesitter and a simple(r) lsp setup! Additionally, switched to mason.nvim to manage my lsp sources (and linters), which is both the new hotness and actually really useful. Allows portable installation of most lsp servers into neovim data directory so they do not clutter any other directories or global namespaces.
2023-02-10 14:33:33 +00:00
"cmp_luasnip": { "branch": "master", "commit": "18095520391186d634a0045dacaa346291096566" },
nvim: Move to lazy.nvim package manager Migrated from packer.nvim to lazy.nvim - it gives really fast loading times, easy lazy loading for any package and a snazzy package manager overview page (invoked through `:Lazy`) which, importantly, all do not rely on a compiled plugin list. In essence it feels like an easier to manage and robust packer replacement (even though packer is a really good manager as well) that is well worth to switch to. Migration was pretty painless as well. One thing I might do in the future is split up the plugin structure itself from a single plugin list (which invokes plugin settings files) to several files containing the plugins and their settings since it might give more structure.
2023-02-10 08:15:56 +00:00
"completion-vcard": { "branch": "master", "commit": "2220fd517a985ececed1adcf0e5be8f2815564c7" },
nvim: Default to stable versions for plugins Using the lazy option 'version' we default to updating only to the latest stable (semver) version of plugins. This should make it a little more stable in the long run to keep up with plugin updates. Not all plugins support this versioning scheme and for those that do not it just keeps tracking the main branch. Currently from the plugins that support it, only `nvim-lspconfig` needs to be manually kept on the main branch since it is missing the correct lua language server otherwise. This should be a problem of the past with the release of the next version of the plugin.
2023-03-03 11:51:21 +00:00
"dial.nvim": { "branch": "master", "commit": "54b503f906bc9e5ab85288414840a1b86d40769f" },
nvim: Update plugin lockfile
2023-03-01 16:39:23 +00:00
"dressing.nvim": { "branch": "master", "commit": "5f44f829481640be0f96759c965ae22a3bcaf7ce" },
"formatter.nvim": { "branch": "master", "commit": "ed949c13e1a942db29ababa35e8c7864ced90eb6" },
nvim: Default to stable versions for plugins Using the lazy option 'version' we default to updating only to the latest stable (semver) version of plugins. This should make it a little more stable in the long run to keep up with plugin updates. Not all plugins support this versioning scheme and for those that do not it just keeps tracking the main branch. Currently from the plugins that support it, only `nvim-lspconfig` needs to be manually kept on the main branch since it is missing the correct lua language server otherwise. This should be a problem of the past with the release of the next version of the plugin.
2023-03-03 11:51:21 +00:00
"friendly-snippets": { "branch": "main", "commit": "009887b76f15d16f69ae1341f86a7862f61cf2a1" },
nvim: Improve dynamic colorscheme sourcing
2023-03-07 09:41:10 +00:00
"fwatch.nvim": { "branch": "main", "commit": "a691f7349dc66285cd75a1a698dd28bca45f2bf8" },
nvim: Default to stable versions for plugins Using the lazy option 'version' we default to updating only to the latest stable (semver) version of plugins. This should make it a little more stable in the long run to keep up with plugin updates. Not all plugins support this versioning scheme and for those that do not it just keeps tracking the main branch. Currently from the plugins that support it, only `nvim-lspconfig` needs to be manually kept on the main branch since it is missing the correct lua language server otherwise. This should be a problem of the past with the release of the next version of the plugin.
2023-03-03 11:51:21 +00:00
"gitsigns.nvim": { "branch": "main", "commit": "bb808fc7376ed7bac0fbe8f47b83d4bf01738167" },
nvim: Update plugin lockfile
2023-03-01 16:39:23 +00:00
"jupyter-kernel.nvim": { "branch": "main", "commit": "92eee2a9fcff65aedaba8f0544b87db44981673b" },
nvim: Update plugins
2023-03-07 09:49:04 +00:00
"lazy.nvim": { "branch": "main", "commit": "14075657131b9a19883a8845c47f1ab65461cd6f" },
nvim: Move to lazy.nvim package manager Migrated from packer.nvim to lazy.nvim - it gives really fast loading times, easy lazy loading for any package and a snazzy package manager overview page (invoked through `:Lazy`) which, importantly, all do not rely on a compiled plugin list. In essence it feels like an easier to manage and robust packer replacement (even though packer is a really good manager as well) that is well worth to switch to. Migration was pretty painless as well. One thing I might do in the future is split up the plugin structure itself from a single plugin list (which invokes plugin settings files) to several files containing the plugins and their settings since it might give more structure.
2023-02-10 08:15:56 +00:00
"lightspeed.nvim": { "branch": "main", "commit": "299eefa6a9e2d881f1194587c573dad619fdb96f" },
nvim: Switch to lsp-zero lsp-zero offers a simple to set-up lsp configuration which is based around the plugins I use anyway (lsp, cmp, luasnip) but integrates them very well. I add a few small quality of life things on top (cmp completion for / search and for vim command mode) as well as a boatload of custom completion sources but otherwise make use of the nice presets. This has de-bloated my _cmp.lua settings somewhat and allows me to have a simple treesitter and a simple(r) lsp setup! Additionally, switched to mason.nvim to manage my lsp sources (and linters), which is both the new hotness and actually really useful. Allows portable installation of most lsp servers into neovim data directory so they do not clutter any other directories or global namespaces.
2023-02-10 14:33:33 +00:00
"lsp-format.nvim": { "branch": "master", "commit": "ca0df5c8544e51517209ea7b86ecc522c98d4f0a" },
nvim: Update plugins
2023-03-07 09:49:04 +00:00
"lsp-zero.nvim": { "branch": "main", "commit": "79d2091809a295aba94f9ea72cd622bca198d046" },
nvim: Default to stable versions for plugins Using the lazy option 'version' we default to updating only to the latest stable (semver) version of plugins. This should make it a little more stable in the long run to keep up with plugin updates. Not all plugins support this versioning scheme and for those that do not it just keeps tracking the main branch. Currently from the plugins that support it, only `nvim-lspconfig` needs to be manually kept on the main branch since it is missing the correct lua language server otherwise. This should be a problem of the past with the release of the next version of the plugin.
2023-03-03 11:51:21 +00:00
"lsp_signature.nvim": { "branch": "master", "commit": "4665921ff8e30601c7c1328625b3abc1427a6143" },
nvim: Update plugin lockfile
2023-03-01 16:39:23 +00:00
"lualine.nvim": { "branch": "master", "commit": "e99d733e0213ceb8f548ae6551b04ae32e590c80" },
"magma-nvim-goose": { "branch": "main", "commit": "d54719dad7771061678a77dace5bef43b4462be8" },
nvim: Default to stable versions for plugins Using the lazy option 'version' we default to updating only to the latest stable (semver) version of plugins. This should make it a little more stable in the long run to keep up with plugin updates. Not all plugins support this versioning scheme and for those that do not it just keeps tracking the main branch. Currently from the plugins that support it, only `nvim-lspconfig` needs to be manually kept on the main branch since it is missing the correct lua language server otherwise. This should be a problem of the past with the release of the next version of the plugin.
2023-03-03 11:51:21 +00:00
"markdown-preview.nvim": { "branch": "master", "commit": "9becceee5740b7db6914da87358a183ad11b2049" },
nvim: Update plugins
2023-03-07 09:49:04 +00:00
"mason-lspconfig.nvim": { "branch": "main", "commit": "a31e011135a79d63c71254c250c9158e1056a1cb" },
"mason.nvim": { "branch": "main", "commit": "3ee3174e30e33c9d58fa07b0a73a6e180474b59c" },
nvim: Update plugin lockfile
2023-03-01 16:39:23 +00:00
"mini.nvim": { "branch": "main", "commit": "427751024313e2270ca723eb16af7b218c83a7fc" },
nvim: Default to stable versions for plugins Using the lazy option 'version' we default to updating only to the latest stable (semver) version of plugins. This should make it a little more stable in the long run to keep up with plugin updates. Not all plugins support this versioning scheme and for those that do not it just keeps tracking the main branch. Currently from the plugins that support it, only `nvim-lspconfig` needs to be manually kept on the main branch since it is missing the correct lua language server otherwise. This should be a problem of the past with the release of the next version of the plugin.
2023-03-03 11:51:21 +00:00
"neural": { "branch": "main", "commit": "155618730b87a67655bdde373ee27bfce8b07ac9" },
nvim: Update plugin lockfile
2023-03-01 16:39:23 +00:00
"nui.nvim": { "branch": "main", "commit": "0dc148c6ec06577fcf06cbab3b7dac96d48ba6be" },
nvim: Improve dynamic colorscheme sourcing
2023-03-07 09:41:10 +00:00
"nvim-base16": { "branch": "master", "commit": "0cab02bac9ca02a70db9e1d07e25fdb630b18a21" },
nvim: Update plugins
2023-03-07 09:49:04 +00:00
"nvim-cmp": { "branch": "main", "commit": "feed47fd1da7a1bad2c7dca456ea19c8a5a9823a" },
nvim: Move to lazy.nvim package manager Migrated from packer.nvim to lazy.nvim - it gives really fast loading times, easy lazy loading for any package and a snazzy package manager overview page (invoked through `:Lazy`) which, importantly, all do not rely on a compiled plugin list. In essence it feels like an easier to manage and robust packer replacement (even though packer is a really good manager as well) that is well worth to switch to. Migration was pretty painless as well. One thing I might do in the future is split up the plugin structure itself from a single plugin list (which invokes plugin settings files) to several files containing the plugins and their settings since it might give more structure.
2023-02-10 08:15:56 +00:00
"nvim-colorizer.lua": { "branch": "master", "commit": "36c610a9717cc9ec426a07c8e6bf3b3abcb139d6" },
nvim: Update plugins
2023-03-07 09:49:04 +00:00
"nvim-lspconfig": { "branch": "master", "commit": "1a2d5f5224c65b0709bf5da0ccd9cad29272083a" },
nvim: Default to stable versions for plugins Using the lazy option 'version' we default to updating only to the latest stable (semver) version of plugins. This should make it a little more stable in the long run to keep up with plugin updates. Not all plugins support this versioning scheme and for those that do not it just keeps tracking the main branch. Currently from the plugins that support it, only `nvim-lspconfig` needs to be manually kept on the main branch since it is missing the correct lua language server otherwise. This should be a problem of the past with the release of the next version of the plugin.
2023-03-03 11:51:21 +00:00
"nvim-notify": { "branch": "master", "commit": "bdd647f61a05c9b8a57c83b78341a0690e9c29d7" },
nvim: Move to lazy.nvim package manager Migrated from packer.nvim to lazy.nvim - it gives really fast loading times, easy lazy loading for any package and a snazzy package manager overview page (invoked through `:Lazy`) which, importantly, all do not rely on a compiled plugin list. In essence it feels like an easier to manage and robust packer replacement (even though packer is a really good manager as well) that is well worth to switch to. Migration was pretty painless as well. One thing I might do in the future is split up the plugin structure itself from a single plugin list (which invokes plugin settings files) to several files containing the plugins and their settings since it might give more structure.
2023-02-10 08:15:56 +00:00
"nvim-surround": { "branch": "main", "commit": "a06dea11e7fdcf338776fa51fa5277163ffb048d" },
nvim: Default to stable versions for plugins Using the lazy option 'version' we default to updating only to the latest stable (semver) version of plugins. This should make it a little more stable in the long run to keep up with plugin updates. Not all plugins support this versioning scheme and for those that do not it just keeps tracking the main branch. Currently from the plugins that support it, only `nvim-lspconfig` needs to be manually kept on the main branch since it is missing the correct lua language server otherwise. This should be a problem of the past with the release of the next version of the plugin.
2023-03-03 11:51:21 +00:00
"nvim-toggleterm.lua": { "branch": "main", "commit": "a5638b2206c3930a16a24e5c184dddd572f8cd34" },
"nvim-treesitter": { "branch": "master", "commit": "c38646edf2bdfac157ca619697ecad9ea87fd469" },
nvim: Update plugin lockfile
2023-03-01 16:39:23 +00:00
"nvim-treesitter-context": { "branch": "master", "commit": "895ec44f5c89bc67ba5440aef3d1f2efa3d59a41" },
"nvim-treesitter-textsubjects": { "branch": "master", "commit": "b913508f503527ff540f7fe2dcf1bf1d1f259887" },
nvim: Hook treesitter commentstrings into comment maps
2023-03-07 09:46:25 +00:00
"nvim-ts-context-commentstring": { "branch": "main", "commit": "729d83ecb990dc2b30272833c213cc6d49ed5214" },
nvim: Update rainbow brackets to maintained fork
2023-03-07 09:45:43 +00:00
"nvim-ts-rainbow2": { "branch": "master", "commit": "b2d1f4f51b1bd20de419ffb6f5d0876c4f20d9db" },
nvim: Update plugin lockfile
2023-03-01 16:39:23 +00:00
"otter.nvim": { "branch": "main", "commit": "8b46caf113918c26a9247031d6482709078ec907" },
"playground": { "branch": "master", "commit": "4044b53c4d4fcd7a78eae20b8627f78ce7dc6f56" },
"plenary.nvim": { "branch": "master", "commit": "253d34830709d690f013daf2853a9d21ad7accab" },
nvim: Move to lazy.nvim package manager Migrated from packer.nvim to lazy.nvim - it gives really fast loading times, easy lazy loading for any package and a snazzy package manager overview page (invoked through `:Lazy`) which, importantly, all do not rely on a compiled plugin list. In essence it feels like an easier to manage and robust packer replacement (even though packer is a really good manager as well) that is well worth to switch to. Migration was pretty painless as well. One thing I might do in the future is split up the plugin structure itself from a single plugin list (which invokes plugin settings files) to several files containing the plugins and their settings since it might give more structure.
2023-02-10 08:15:56 +00:00
"popup.nvim": { "branch": "master", "commit": "b7404d35d5d3548a82149238289fa71f7f6de4ac" },
nvim: Default to stable versions for plugins Using the lazy option 'version' we default to updating only to the latest stable (semver) version of plugins. This should make it a little more stable in the long run to keep up with plugin updates. Not all plugins support this versioning scheme and for those that do not it just keeps tracking the main branch. Currently from the plugins that support it, only `nvim-lspconfig` needs to be manually kept on the main branch since it is missing the correct lua language server otherwise. This should be a problem of the past with the release of the next version of the plugin.
2023-03-03 11:51:21 +00:00
"quarto-nvim": { "branch": "main", "commit": "b44f8772686241e563c7d0f200748fd71766b64e" },
nvim: Update plugin lockfile
2023-03-01 16:39:23 +00:00
"significant.nvim": { "branch": "main", "commit": "5450e9d5917dc6aa9afb0fcbe32355799b8303fb" },
nvim: Move to lazy.nvim package manager Migrated from packer.nvim to lazy.nvim - it gives really fast loading times, easy lazy loading for any package and a snazzy package manager overview page (invoked through `:Lazy`) which, importantly, all do not rely on a compiled plugin list. In essence it feels like an easier to manage and robust packer replacement (even though packer is a really good manager as well) that is well worth to switch to. Migration was pretty painless as well. One thing I might do in the future is split up the plugin structure itself from a single plugin list (which invokes plugin settings files) to several files containing the plugins and their settings since it might give more structure.
2023-02-10 08:15:56 +00:00
"spellsitter.nvim": { "branch": "master", "commit": "4af8640d9d706447e78c13150ef7475ea2c16b30" },
"symbols-outline.nvim": { "branch": "master", "commit": "512791925d57a61c545bc303356e8a8f7869763c" },
"telescope-fzf-native.nvim": { "branch": "main", "commit": "580b6c48651cabb63455e97d7e131ed557b8c7e2" },
nvim: Default to stable versions for plugins Using the lazy option 'version' we default to updating only to the latest stable (semver) version of plugins. This should make it a little more stable in the long run to keep up with plugin updates. Not all plugins support this versioning scheme and for those that do not it just keeps tracking the main branch. Currently from the plugins that support it, only `nvim-lspconfig` needs to be manually kept on the main branch since it is missing the correct lua language server otherwise. This should be a problem of the past with the release of the next version of the plugin.
2023-03-03 11:51:21 +00:00
"telescope.nvim": { "branch": "master", "commit": "c1a2af0af69e80e14e6b226d3957a064cd080805" },
"twilight.nvim": { "branch": "main", "commit": "8bb7fa7b918baab1ca81b977102ddb54afa63512" },
"vifm.vim": { "branch": "master", "commit": "6898b7fcbc36324c127ba42cabe488ab15c785f4" },
nvim: Move to lazy.nvim package manager Migrated from packer.nvim to lazy.nvim - it gives really fast loading times, easy lazy loading for any package and a snazzy package manager overview page (invoked through `:Lazy`) which, importantly, all do not rely on a compiled plugin list. In essence it feels like an easier to manage and robust packer replacement (even though packer is a really good manager as well) that is well worth to switch to. Migration was pretty painless as well. One thing I might do in the future is split up the plugin structure itself from a single plugin list (which invokes plugin settings files) to several files containing the plugins and their settings since it might give more structure.
2023-02-10 08:15:56 +00:00
"vim-criticmarkup": { "branch": "master", "commit": "d15dc134eb177a170c79f6377f81eb02a9d20b02" },
nvim: Default to stable versions for plugins Using the lazy option 'version' we default to updating only to the latest stable (semver) version of plugins. This should make it a little more stable in the long run to keep up with plugin updates. Not all plugins support this versioning scheme and for those that do not it just keeps tracking the main branch. Currently from the plugins that support it, only `nvim-lspconfig` needs to be manually kept on the main branch since it is missing the correct lua language server otherwise. This should be a problem of the past with the release of the next version of the plugin.
2023-03-03 11:51:21 +00:00
"vim-easy-align": { "branch": "master", "commit": "0db4ea6132110631ec678a99a82aa49a0686ae65" },
nvim: Move to lazy.nvim package manager Migrated from packer.nvim to lazy.nvim - it gives really fast loading times, easy lazy loading for any package and a snazzy package manager overview page (invoked through `:Lazy`) which, importantly, all do not rely on a compiled plugin list. In essence it feels like an easier to manage and robust packer replacement (even though packer is a really good manager as well) that is well worth to switch to. Migration was pretty painless as well. One thing I might do in the future is split up the plugin structure itself from a single plugin list (which invokes plugin settings files) to several files containing the plugins and their settings since it might give more structure.
2023-02-10 08:15:56 +00:00
"vim-exchange": { "branch": "master", "commit": "784d63083ad7d613aa96f00021cd0dfb126a781a" },
nvim: Default to stable versions for plugins Using the lazy option 'version' we default to updating only to the latest stable (semver) version of plugins. This should make it a little more stable in the long run to keep up with plugin updates. Not all plugins support this versioning scheme and for those that do not it just keeps tracking the main branch. Currently from the plugins that support it, only `nvim-lspconfig` needs to be manually kept on the main branch since it is missing the correct lua language server otherwise. This should be a problem of the past with the release of the next version of the plugin.
2023-03-03 11:51:21 +00:00
"vim-numbertoggle": { "branch": "main", "commit": "df9b1fe616507340718716204ba7f434125bdf7a" },
nvim: Update plugins
2023-03-07 09:49:04 +00:00
"vim-oscyank": { "branch": "main", "commit": "ffe827a27dae98aa826e2295336c650c9a434da0" },
nvim: Move to lazy.nvim package manager Migrated from packer.nvim to lazy.nvim - it gives really fast loading times, easy lazy loading for any package and a snazzy package manager overview page (invoked through `:Lazy`) which, importantly, all do not rely on a compiled plugin list. In essence it feels like an easier to manage and robust packer replacement (even though packer is a really good manager as well) that is well worth to switch to. Migration was pretty painless as well. One thing I might do in the future is split up the plugin structure itself from a single plugin list (which invokes plugin settings files) to several files containing the plugins and their settings since it might give more structure.
2023-02-10 08:15:56 +00:00
"vim-pandoc-syntax": { "branch": "master", "commit": "4268535e1d33117a680a91160d845cd3833dfe28" },
nvim: Default to stable versions for plugins Using the lazy option 'version' we default to updating only to the latest stable (semver) version of plugins. This should make it a little more stable in the long run to keep up with plugin updates. Not all plugins support this versioning scheme and for those that do not it just keeps tracking the main branch. Currently from the plugins that support it, only `nvim-lspconfig` needs to be manually kept on the main branch since it is missing the correct lua language server otherwise. This should be a problem of the past with the release of the next version of the plugin.
2023-03-03 11:51:21 +00:00
"vim-spellsync": { "branch": "master", "commit": "3d6dd50de9c4d953cc16638112a6ae196df41463" },
"which-key.nvim": { "branch": "main", "commit": "2a0c2d80c0a60f041afb1b789cfedbd510e2b2b6" },
nvim: Add wrapping plugin
2023-03-03 11:38:09 +00:00
"wrapping.nvim": { "branch": "master", "commit": "a4013c377e2ffa3be00fb67791d3605ae3115acb" },
nvim: Default to stable versions for plugins Using the lazy option 'version' we default to updating only to the latest stable (semver) version of plugins. This should make it a little more stable in the long run to keep up with plugin updates. Not all plugins support this versioning scheme and for those that do not it just keeps tracking the main branch. Currently from the plugins that support it, only `nvim-lspconfig` needs to be manually kept on the main branch since it is missing the correct lua language server otherwise. This should be a problem of the past with the release of the next version of the plugin.
2023-03-03 11:51:21 +00:00
"zen-mode.nvim": { "branch": "main", "commit": "4bd28fb3a44317c6258cebc7d92243d4b11dfe2c" },
nvim: Update plugin lockfile
2023-03-01 16:39:23 +00:00
"zettelkasten.nvim": { "branch": "main", "commit": "0e77624689b470410f5355b613d45219c9350264" },
"zk-nvim": { "branch": "main", "commit": "0413c52500cd0133b0cd8e7e7d43084855ac1760" }
nvim: Move to lazy.nvim package manager Migrated from packer.nvim to lazy.nvim - it gives really fast loading times, easy lazy loading for any package and a snazzy package manager overview page (invoked through `:Lazy`) which, importantly, all do not rely on a compiled plugin list. In essence it feels like an easier to manage and robust packer replacement (even though packer is a really good manager as well) that is well worth to switch to. Migration was pretty painless as well. One thing I might do in the future is split up the plugin structure itself from a single plugin list (which invokes plugin settings files) to several files containing the plugins and their settings since it might give more structure.
2023-02-10 08:15:56 +00:00
}
Reference in a new issue Copy permalink