Conversation

Notices

1. Embed this notice
   Biason::Julio::new(); (juliobiason@functional.cafe)'s status on Saturday, 25-Jan-2025 02:36:25 JST Biason::Julio::new();

   With the thing about LSP breaking with Rust files, I'm considering nuking my NeoVim configuration and starting from scratch...

   • Embed this notice
     Biason::Julio::new(); (juliobiason@functional.cafe)'s status on Saturday, 25-Jan-2025 02:37:28 JST Biason::Julio::new();

     in reply to

     I also have another issue, that I'm using Packer for plugin management, but it is currently unmaintained. So it would be a good time to switch to another plugin manager...

   • Embed this notice
     Biason::Julio::new(); (juliobiason@functional.cafe)'s status on Saturday, 25-Jan-2025 05:08:54 JST Biason::Julio::new();

     in reply to

     • Mirek Długosz 🕸️:python:🐛

     @mirekdlugosz I tried lazy and gave up after 10 minutes.

     I went to Pckr, which describes itself as "spiritual successor of Packer" (also took a chance to reduce the number of plugins).

   • Embed this notice
     Mirek Długosz 🕸️:python:🐛 (mirekdlugosz@fosstodon.org)'s status on Saturday, 25-Jan-2025 05:08:55 JST Mirek Długosz 🕸️:python:🐛

     in reply to

     @juliobiason

     I recently moved from packer to savq/paq-nvim . It was mostly just a syntax change.

     A lot of folks move to lazy.nvim, but for me that was much more involved and many things initially broke. I don’t really like the idea of creating extensions system parallel to one that nvim has built-in, and I find speed improvements overrated. I gave up on lazy.nvim after hour or two.