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

84 lines
7.6 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
{
nvim: Update plugin lockfile
2023-03-19 13:49:38 +00:00
"Arduino.nvim": { "branch": "main", "commit": "63f71687c0f4bcebafbb7e480f0d47b6fe46bd82" },
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" },
nvim: Move Navigator to dev version Since Navigator.nvim only implements wezterm compatibility in its main branch as of now, we explicitly switch away from its stable version for now.
2023-03-07 09:49:51 +00:00
"Navigator.nvim": { "branch": "master", "commit": "91d86506ac2a039504d5205d32a1d4bc7aa57072" },
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" },
nvim: Prepare lsp-zero switch to v2 branch Switched the configuration of lsp-zero to its less integrated v2 version. Switched back to manually configuring most of nvim-cmp. Addded some manual formatting to cmp which displays completion kind as icons not as text. Manually add luasnip integration.
2023-03-22 07:30:04 +00:00
"cmp-beancount": { "branch": "main", "commit": "da154ea94d598e6649d6ad01efa0a8611eff460d" },
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-buffer": { "branch": "main", "commit": "3022dbc9166796b644a841a02de8dd1cc1d311fa" },
nvim: Prepare lsp-zero switch to v2 branch Switched the configuration of lsp-zero to its less integrated v2 version. Switched back to manually configuring most of nvim-cmp. Addded some manual formatting to cmp which displays completion kind as icons not as text. Manually add luasnip integration.
2023-03-22 07:30:04 +00:00
"cmp-calc": { "branch": "main", "commit": "50792f34a628ea6eb31d2c90e8df174671e4e7a0" },
nvim: Restructure lua dir Moved plugins into individual component module files which are automatically required by lazy.nvim. Should make everything a tiny bit more modular, or at least prepare the way for true modularity if I ever have the time on my hands to ensure everything works with missing modules. Moved core settings into their own directory (`core`), and created a `personal` folder which contains functions/plugins I wrote that do not necessarily have to be their own imported plugin yet. Finally, extended the utility functions a little, so we can detect if a plugin exists and change e.g. key maps based on that (once again, extending modularity a little more). Some simple attempts have been made at that in the `mappings.lua` file, though it is nowhere near extensive yet - most keymaps are still set regardless of plugin availability. However, with this slimmer base to work off of, I feel more confident in changing future things about this setup a little more ad-hoc without having as many ripple repercussions as before.
2023-06-15 13:45:21 +00:00
"cmp-cmdline": { "branch": "main", "commit": "8ee981b4a91f536f52add291594e89fb6645e451" },
nvim: Prepare lsp-zero switch to v2 branch Switched the configuration of lsp-zero to its less integrated v2 version. Switched back to manually configuring most of nvim-cmp. Addded some manual formatting to cmp which displays completion kind as icons not as text. Manually add luasnip integration.
2023-03-22 07:30:04 +00:00
"cmp-digraphs": { "branch": "master", "commit": "5efc1f0078d7c5f3ea1c8e3aad04da3fd6e081a9" },
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" },
nvim: Update plugins
2023-05-23 13:50:37 +00:00
"cmp-nvim-lua": { "branch": "main", "commit": "f12408bdb54c39c23e67cab726264c10db33ada8" },
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" },
nvim: Prepare lsp-zero switch to v2 branch Switched the configuration of lsp-zero to its less integrated v2 version. Switched back to manually configuring most of nvim-cmp. Addded some manual formatting to cmp which displays completion kind as icons not as text. Manually add luasnip integration.
2023-03-22 07:30:04 +00:00
"cmp-rg": { "branch": "master", "commit": "1cad8eb315643d0df13c37401c03d7986f891011" },
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-spell": { "branch": "master", "commit": "60584cb75e5e8bba5a0c9e4c3ab0791e0698bffa" },
"cmp-tmux": { "branch": "main", "commit": "984772716f66d8ee88535a6bf3f94c4b4e1301f5" },
nvim: Update plugins
2023-05-23 13:50:37 +00:00
"cmp-treesitter": { "branch": "master", "commit": "389eadd48c27aa6dc0e6b992644704f026802a2e" },
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 plugins
2023-06-07 08:05:16 +00:00
"dressing.nvim": { "branch": "master", "commit": "f16d7586fcdd8b2e3850d0abb7e46f944125cc25" },
nvim: Update plugins
2023-05-23 13:50:37 +00:00
"easyread.nvim": { "branch": "main", "commit": "0b07e315a4cd7d700c4a794bdddbec79fdc2628b" },
"fidget.nvim": { "branch": "main", "commit": "0ba1e16d07627532b6cae915cc992ecac249fb97" },
nvim: Restructure lua dir Moved plugins into individual component module files which are automatically required by lazy.nvim. Should make everything a tiny bit more modular, or at least prepare the way for true modularity if I ever have the time on my hands to ensure everything works with missing modules. Moved core settings into their own directory (`core`), and created a `personal` folder which contains functions/plugins I wrote that do not necessarily have to be their own imported plugin yet. Finally, extended the utility functions a little, so we can detect if a plugin exists and change e.g. key maps based on that (once again, extending modularity a little more). Some simple attempts have been made at that in the `mappings.lua` file, though it is nowhere near extensive yet - most keymaps are still set regardless of plugin availability. However, with this slimmer base to work off of, I feel more confident in changing future things about this setup a little more ad-hoc without having as many ripple repercussions as before.
2023-06-15 13:45:21 +00:00
"friendly-snippets": { "branch": "main", "commit": "b3cd8d77feb7871d8b04bb45bcd8154120a796a1" },
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 plugins
2023-05-23 13:50:37 +00:00
"jupyter-kernel.nvim": { "branch": "main", "commit": "5b409598033884a3d819e2a3bcd1fe340bc8d783" },
nvim: Restructure lua dir Moved plugins into individual component module files which are automatically required by lazy.nvim. Should make everything a tiny bit more modular, or at least prepare the way for true modularity if I ever have the time on my hands to ensure everything works with missing modules. Moved core settings into their own directory (`core`), and created a `personal` folder which contains functions/plugins I wrote that do not necessarily have to be their own imported plugin yet. Finally, extended the utility functions a little, so we can detect if a plugin exists and change e.g. key maps based on that (once again, extending modularity a little more). Some simple attempts have been made at that in the `mappings.lua` file, though it is nowhere near extensive yet - most keymaps are still set regardless of plugin availability. However, with this slimmer base to work off of, I feel more confident in changing future things about this setup a little more ad-hoc without having as many ripple repercussions as before.
2023-06-15 13:45:21 +00:00
"lazy.nvim": { "branch": "main", "commit": "6b2311a46a3808e366bb251270f4cc04afb421ed" },
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: Restructure lua dir Moved plugins into individual component module files which are automatically required by lazy.nvim. Should make everything a tiny bit more modular, or at least prepare the way for true modularity if I ever have the time on my hands to ensure everything works with missing modules. Moved core settings into their own directory (`core`), and created a `personal` folder which contains functions/plugins I wrote that do not necessarily have to be their own imported plugin yet. Finally, extended the utility functions a little, so we can detect if a plugin exists and change e.g. key maps based on that (once again, extending modularity a little more). Some simple attempts have been made at that in the `mappings.lua` file, though it is nowhere near extensive yet - most keymaps are still set regardless of plugin availability. However, with this slimmer base to work off of, I feel more confident in changing future things about this setup a little more ad-hoc without having as many ripple repercussions as before.
2023-06-15 13:45:21 +00:00
"lsp-setup.nvim": { "branch": "main", "commit": "4656a1882546b702b18a84f5de209a2f8aa43dee" },
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 plugins
2023-05-23 13:50:37 +00:00
"lualine.nvim": { "branch": "master", "commit": "05d78e9fd0cdfb4545974a5aa14b1be95a86e9c9" },
nvim: Restructure lua dir Moved plugins into individual component module files which are automatically required by lazy.nvim. Should make everything a tiny bit more modular, or at least prepare the way for true modularity if I ever have the time on my hands to ensure everything works with missing modules. Moved core settings into their own directory (`core`), and created a `personal` folder which contains functions/plugins I wrote that do not necessarily have to be their own imported plugin yet. Finally, extended the utility functions a little, so we can detect if a plugin exists and change e.g. key maps based on that (once again, extending modularity a little more). Some simple attempts have been made at that in the `mappings.lua` file, though it is nowhere near extensive yet - most keymaps are still set regardless of plugin availability. However, with this slimmer base to work off of, I feel more confident in changing future things about this setup a little more ad-hoc without having as many ripple repercussions as before.
2023-06-15 13:45:21 +00:00
"magma-nvim-goose": { "branch": "main", "commit": "d7931d773efcedc9c92337b8d500e32a3725fe26" },
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-06-07 08:05:16 +00:00
"mason-lspconfig.nvim": { "branch": "main", "commit": "5230617372e656d4a2e1e236e03bf7e7b4b97273" },
nvim: Integrate null_ls for formatting and linting Formatting and linting should from now be done with null_ls instead of formatter.nvim (and nothing for linting so far). This will still take a little to fully transition, for now we use null_ls for eslint linting and prettier formatting for a variety of javascript/typescript and astro files. null_ls uses Mason installations under the hood and any tool it uses also gets installed by Mason.
2023-06-15 07:46:38 +00:00
"mason-null-ls.nvim": { "branch": "main", "commit": "cfbd83909cbc56e2f07cb3f8a03157e069c5c91c" },
nvim: Restructure lua dir Moved plugins into individual component module files which are automatically required by lazy.nvim. Should make everything a tiny bit more modular, or at least prepare the way for true modularity if I ever have the time on my hands to ensure everything works with missing modules. Moved core settings into their own directory (`core`), and created a `personal` folder which contains functions/plugins I wrote that do not necessarily have to be their own imported plugin yet. Finally, extended the utility functions a little, so we can detect if a plugin exists and change e.g. key maps based on that (once again, extending modularity a little more). Some simple attempts have been made at that in the `mappings.lua` file, though it is nowhere near extensive yet - most keymaps are still set regardless of plugin availability. However, with this slimmer base to work off of, I feel more confident in changing future things about this setup a little more ad-hoc without having as many ripple repercussions as before.
2023-06-15 13:45:21 +00:00
"mason.nvim": { "branch": "main", "commit": "4be1226f48bc2011024110f37b17f5ee468df58f" },
"mini.nvim": { "branch": "main", "commit": "296ebbbd3e5ba5e43f5125efe18ad76fe3b632cc" },
nvim: Update plugins
2023-05-23 13:50:37 +00:00
"nabla.nvim": { "branch": "master", "commit": "8c143ad2b3ab3b8ffbd51e238ccfcbd246452a7e" },
nvim: Integrate null_ls for formatting and linting Formatting and linting should from now be done with null_ls instead of formatter.nvim (and nothing for linting so far). This will still take a little to fully transition, for now we use null_ls for eslint linting and prettier formatting for a variety of javascript/typescript and astro files. null_ls uses Mason installations under the hood and any tool it uses also gets installed by Mason.
2023-06-15 07:46:38 +00:00
"null-ls.nvim": { "branch": "main", "commit": "a138b14099e9623832027ea12b4631ddd2a49256" },
nvim: Update plugins
2023-05-23 13:50:37 +00:00
"nvim-base16": { "branch": "master", "commit": "4f3aa29f49b38edb6db1c52cea57e64ce3de2373" },
nvim: Restructure lua dir Moved plugins into individual component module files which are automatically required by lazy.nvim. Should make everything a tiny bit more modular, or at least prepare the way for true modularity if I ever have the time on my hands to ensure everything works with missing modules. Moved core settings into their own directory (`core`), and created a `personal` folder which contains functions/plugins I wrote that do not necessarily have to be their own imported plugin yet. Finally, extended the utility functions a little, so we can detect if a plugin exists and change e.g. key maps based on that (once again, extending modularity a little more). Some simple attempts have been made at that in the `mappings.lua` file, though it is nowhere near extensive yet - most keymaps are still set regardless of plugin availability. However, with this slimmer base to work off of, I feel more confident in changing future things about this setup a little more ad-hoc without having as many ripple repercussions as before.
2023-06-15 13:45:21 +00:00
"nvim-cmp": { "branch": "main", "commit": "b8c2a62b3bd3827aa059b43be3dd4b5c45037d65" },
nvim: Update colorizer git address
2023-03-22 15:29:10 +00:00
"nvim-colorizer.lua": { "branch": "master", "commit": "dde3084106a70b9a79d48f426f6d6fec6fd203f7" },
nvim: Restructure lua dir Moved plugins into individual component module files which are automatically required by lazy.nvim. Should make everything a tiny bit more modular, or at least prepare the way for true modularity if I ever have the time on my hands to ensure everything works with missing modules. Moved core settings into their own directory (`core`), and created a `personal` folder which contains functions/plugins I wrote that do not necessarily have to be their own imported plugin yet. Finally, extended the utility functions a little, so we can detect if a plugin exists and change e.g. key maps based on that (once again, extending modularity a little more). Some simple attempts have been made at that in the `mappings.lua` file, though it is nowhere near extensive yet - most keymaps are still set regardless of plugin availability. However, with this slimmer base to work off of, I feel more confident in changing future things about this setup a little more ad-hoc without having as many ripple repercussions as before.
2023-06-15 13:45:21 +00:00
"nvim-lspconfig": { "branch": "master", "commit": "295c646488d5baa63c6c4da68fe61171b9257375" },
nvim: Update plugins
2023-06-07 08:05:16 +00:00
"nvim-notify": { "branch": "master", "commit": "ea9c8ce7a37f2238f934e087c255758659948e0f" },
"nvim-surround": { "branch": "main", "commit": "211eaad7c6d01ef4ac02cba9052b3082ec232101" },
"nvim-toggleterm.lua": { "branch": "main", "commit": "95204ece0f2a54c89c4395295432f9aeedca7b5f" },
nvim: Restructure lua dir Moved plugins into individual component module files which are automatically required by lazy.nvim. Should make everything a tiny bit more modular, or at least prepare the way for true modularity if I ever have the time on my hands to ensure everything works with missing modules. Moved core settings into their own directory (`core`), and created a `personal` folder which contains functions/plugins I wrote that do not necessarily have to be their own imported plugin yet. Finally, extended the utility functions a little, so we can detect if a plugin exists and change e.g. key maps based on that (once again, extending modularity a little more). Some simple attempts have been made at that in the `mappings.lua` file, though it is nowhere near extensive yet - most keymaps are still set regardless of plugin availability. However, with this slimmer base to work off of, I feel more confident in changing future things about this setup a little more ad-hoc without having as many ripple repercussions as before.
2023-06-15 13:45:21 +00:00
"nvim-tree.lua": { "branch": "master", "commit": "f873625d0636889af4cd47a01e486beb865db205" },
nvim: Update plugins
2023-05-23 13:50:37 +00:00
"nvim-treesitter": { "branch": "master", "commit": "cc360a9beb1b30d172438f640e2c3450358c4086" },
nvim: Restructure lua dir Moved plugins into individual component module files which are automatically required by lazy.nvim. Should make everything a tiny bit more modular, or at least prepare the way for true modularity if I ever have the time on my hands to ensure everything works with missing modules. Moved core settings into their own directory (`core`), and created a `personal` folder which contains functions/plugins I wrote that do not necessarily have to be their own imported plugin yet. Finally, extended the utility functions a little, so we can detect if a plugin exists and change e.g. key maps based on that (once again, extending modularity a little more). Some simple attempts have been made at that in the `mappings.lua` file, though it is nowhere near extensive yet - most keymaps are still set regardless of plugin availability. However, with this slimmer base to work off of, I feel more confident in changing future things about this setup a little more ad-hoc without having as many ripple repercussions as before.
2023-06-15 13:45:21 +00:00
"nvim-treesitter-context": { "branch": "master", "commit": "efe87061af560847679fca93697991e474f049e2" },
nvim: Update plugin lockfile
2023-03-01 16:39:23 +00:00
"nvim-treesitter-textsubjects": { "branch": "master", "commit": "b913508f503527ff540f7fe2dcf1bf1d1f259887" },
nvim: Restructure lua dir Moved plugins into individual component module files which are automatically required by lazy.nvim. Should make everything a tiny bit more modular, or at least prepare the way for true modularity if I ever have the time on my hands to ensure everything works with missing modules. Moved core settings into their own directory (`core`), and created a `personal` folder which contains functions/plugins I wrote that do not necessarily have to be their own imported plugin yet. Finally, extended the utility functions a little, so we can detect if a plugin exists and change e.g. key maps based on that (once again, extending modularity a little more). Some simple attempts have been made at that in the `mappings.lua` file, though it is nowhere near extensive yet - most keymaps are still set regardless of plugin availability. However, with this slimmer base to work off of, I feel more confident in changing future things about this setup a little more ad-hoc without having as many ripple repercussions as before.
2023-06-15 13:45:21 +00:00
"nvim-ts-autotag": { "branch": "main", "commit": "e254b306fb81ed69049cce526e7906150d73e0d1" },
nvim: Update plugins
2023-05-23 13:50:37 +00:00
"nvim-ts-context-commentstring": { "branch": "main", "commit": "0bf8fbc2ca8f8cdb6efbd0a9e32740d7a991e4c3" },
nvim: Update plugins
2023-06-07 08:05:16 +00:00
"nvim-ts-rainbow2": { "branch": "master", "commit": "c00d61ab7517530c49457ba49186776e6611a3e1" },
"nvim-web-devicons": { "branch": "master", "commit": "2a125024a137677930efcfdf720f205504c97268" },
"otter.nvim": { "branch": "main", "commit": "242d180e7f23cc2af6b5d5193bc50909408caef7" },
nvim: Update plugins
2023-05-23 13:50:37 +00:00
"playground": { "branch": "master", "commit": "2b81a018a49f8e476341dfcb228b7b808baba68b" },
nvim: Update plugin lockfile
2023-03-01 16:39:23 +00:00
"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: Update plugins
2023-06-07 08:05:16 +00:00
"quarto-nvim": { "branch": "main", "commit": "b299266c6287d74b60480fae348d629ec1dc02bb" },
nvim: Add smartcolumn plugin
2023-03-22 15:14:10 +00:00
"smartcolumn.nvim": { "branch": "main", "commit": "0c572e3eae48874f25b74394a486f38cadb5c958" },
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
"symbols-outline.nvim": { "branch": "master", "commit": "512791925d57a61c545bc303356e8a8f7869763c" },
nvim: Update plugins
2023-06-07 08:05:16 +00:00
"telescope-fzf-native.nvim": { "branch": "main", "commit": "9bc8237565ded606e6c366a71c64c0af25cd7a50" },
nvim: Restructure lua dir Moved plugins into individual component module files which are automatically required by lazy.nvim. Should make everything a tiny bit more modular, or at least prepare the way for true modularity if I ever have the time on my hands to ensure everything works with missing modules. Moved core settings into their own directory (`core`), and created a `personal` folder which contains functions/plugins I wrote that do not necessarily have to be their own imported plugin yet. Finally, extended the utility functions a little, so we can detect if a plugin exists and change e.g. key maps based on that (once again, extending modularity a little more). Some simple attempts have been made at that in the `mappings.lua` file, though it is nowhere near extensive yet - most keymaps are still set regardless of plugin availability. However, with this slimmer base to work off of, I feel more confident in changing future things about this setup a little more ad-hoc without having as many ripple repercussions as before.
2023-06-15 13:45:21 +00:00
"telescope.nvim": { "branch": "master", "commit": "776b509f80dd49d8205b9b0d94485568236d1192" },
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
"twilight.nvim": { "branch": "main", "commit": "8bb7fa7b918baab1ca81b977102ddb54afa63512" },
nvim: Add undotree plugin Lua implementation of the undo tree plugin, mapped to be reachable with <leader>su (for show undo).
2023-06-17 19:58:04 +00:00
"undotree": { "branch": "main", "commit": "2685ce282702ab0b79c65916f352db2265b245dd" },
nvim: Update plugins
2023-05-23 13:50:37 +00:00
"vifm.vim": { "branch": "master", "commit": "a8130c37d144b51d84bee19f0532abcd3583383f" },
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" },
nvim: Update plugins
2023-06-07 08:05:16 +00:00
"which-key.nvim": { "branch": "main", "commit": "e271c28118998c93a14d189af3395812a1aa646c" },
"wrapping.nvim": { "branch": "master", "commit": "5e87f1424c86c50d3bc205830aa56ed1cad45467" },
nvim: Update plugins
2023-05-23 13:50:37 +00:00
"zen-mode.nvim": { "branch": "main", "commit": "6e6c963d70a8e47854fa656987666bfb863f9c4e" },
nvim: Update plugin lockfile
2023-03-01 16:39:23 +00:00
"zettelkasten.nvim": { "branch": "main", "commit": "0e77624689b470410f5355b613d45219c9350264" },
nvim: Update plugins
2023-06-07 08:05:16 +00:00
"zk-nvim": { "branch": "main", "commit": "5ddb53688035d115f941f0c8255f6e6618e608ac" }
nvim: Restructure lua dir Moved plugins into individual component module files which are automatically required by lazy.nvim. Should make everything a tiny bit more modular, or at least prepare the way for true modularity if I ever have the time on my hands to ensure everything works with missing modules. Moved core settings into their own directory (`core`), and created a `personal` folder which contains functions/plugins I wrote that do not necessarily have to be their own imported plugin yet. Finally, extended the utility functions a little, so we can detect if a plugin exists and change e.g. key maps based on that (once again, extending modularity a little more). Some simple attempts have been made at that in the `mappings.lua` file, though it is nowhere near extensive yet - most keymaps are still set regardless of plugin availability. However, with this slimmer base to work off of, I feel more confident in changing future things about this setup a little more ad-hoc without having as many ripple repercussions as before.
2023-06-15 13:45:21 +00:00
}
Reference in a new issue Copy permalink