3 ms·

Are you using different OS? This sounds like the programs your NeoVim is calling is failing you - not nvim itself. _cough cough_ NixOS can help you out here

• mekster 4y ago
  Ubuntu 22.04. I'm guessing the few dozens of plugins are probably messed up in a way or another after each updates. Apparently, there's no unified QA testing among community supported ecosystem with 20 different authors.
  • ar_lan 4y ago
    In packer, at least, you can pin plug-in versions. I’ve never had the issue you describe - I suspect precisely because I keep my plugin count lean and pin each dependency so it’s always deterministic.
• selfmodruntime 4y ago
  It's not neovim, but the surrounding plugin architecture I need. I'm using coc.nvim to get autocompletions and documentation and I find that to be increasingly brittle. Also the python3 provider stuff randomly breaks in a venv sometime.
  • reissbaker 4y ago
    Huh, sorry to hear that. Personally the only annoyance I've had with coc.nvim was when they changed how autocomplete worked and I had to update my keybindings, but that wasn't particularly bad.