Archiving Null-Ls

3 points by bronzecarnage 2 years ago | 2 comments

hannofcart 2 years ago |

I wish the author thanks and the very best going forward in whatever he chooses to work on.

Having said that, this is going to cause not a little trouble for a lot of Lunarvim users.

I was quite surprised by Lunarvim choosing null-ls as it's default linting and formatting handling plugin.

I had to struggle quite a bit to get null-ls working with the new lvim release because as the author points out, the architecture of the plugin is very much exposed to changes in neovim and lsp.

Spent a lot of time after the lvim 1.3 release to get null-ls working as before. I even tried debugging the lua code a bit to get a sense of what was going wrong. Finally I just ditched it and went with a different linter plugin (and yet another formatter plugin).

bronzecarnage 2 years ago | |

This is ultimately due to the general problem of neovim internals being in so much flux. So much keeps changing, updating, and breaking in the internals and plugins. It does take some upkeep at every level, and after a point I think people get tired of it. At the end of the day, you only have so much time and patience.