• Olap@lemmy.world
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    10 months ago

    For me vim is one of those things that just works. It’s ever present, reliable, and dependable. The simplicity of it mirrors the unix way and my usage of it is so closely wrapped in screen, /tmux, bash, gnu-coreutils, and a few terminals over the years that any change is going to have me asking ‘why?’ essentially. So a command line flag allows familiarity of existing tooling to really sing, and I suspect offers far more compatibility than the suggested fix too given the length of the windows addendum to the guide

    And totally agreed about out in, I use Arch btw. And I’m not in a hurry to switch to nvim either, I tried and switched back pretty quickly. Pathogen is still an amazing plugin system, leveraging my git and bash knowledge to boot

    • BatmanAoD@programming.dev
      link
      fedilink
      arrow-up
      3
      ·
      10 months ago

      Well, sure, if the appeal of vim for you is that it “just works” on every platform you use, then there’s no advantage to adopting neovim. That’s no reason to complain that neovim isn’t meeting your needs, though.

      • Olap@lemmy.world
        link
        fedilink
        arrow-up
        1
        arrow-down
        3
        ·
        10 months ago

        It’s more advice than a complaint. I run on one setup. Linux terminals. And neovim has to beat that for me to switch