diff options
Diffstat (limited to 'weblog/from-packer-to-lazy-nvim.md')
| -rw-r--r-- | weblog/from-packer-to-lazy-nvim.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/weblog/from-packer-to-lazy-nvim.md b/weblog/from-packer-to-lazy-nvim.md index 9ab0c95..0ab471f 100644 --- a/weblog/from-packer-to-lazy-nvim.md +++ b/weblog/from-packer-to-lazy-nvim.md @@ -2,6 +2,8 @@ post_date: 2023-11-01 --- +> Note: This was ported from my old gemini capsule, still served on gemini at `gemini.ctrl-c.club/~tjp` + # From packer to lazy.nvim I ported my vim configuration again. @@ -41,5 +43,3 @@ All in all, the new setup on lazy.nvim is superior to what I had with packer in Mason is managing a limited set of LSP options so everything is right there - what you've installed and what you haven't. Lazy.nvim is different because the set of vim plugins you haven't installed is pretty much unknowable. However, it is telling that strings like 'pluginname' automatically reference vim.org/scripts, and strings like 'author/name' automatically reference github.com. With that in mind, it would be great if the Lazy UI offered a means of searching vim.org scripts and public github repos. There would probably be github rate limits to contend with, but otherwise it seems like something that should be doable. Finally, as I mentioned before it would be amazing to have a UI like Mason but which manages treesitter parsers. I wouldn't expect this to come from lazy.nvim, it's just another plugin that should exist. - -> Note: This was ported from my old gemini capsule, still served on gemini at `gemini.ctrl-c.club/~tjp` |