1. 12
  1.  

  2. 6

    I’ve been using Neovim for about a year now, haven’t looked back. Development cycle is a lot quicker, all my favorite old Vim plugins still work, and there’s been a huge ecosystem of new plugins that take advantage of Neovim’s remote plugin architecture (check out Deoplete and Denite, or any of Shuogo’s plugins).

    I guess with the addition of packpath, you can no longer directly port your configs from vim -> neovim with zero changes. I’m curious if that was a conscious choice on Vim’s part to try and prevent people from leaving for greener pastures.

    1. 1

      The one thing I want is multi-window support. I have multiple monitors, and I’d like to have a vim instance on each one sharing buffers.

      1. 2

        Can you explain what you mean here? Two (or more?) vim processes sharing the same buffer? I’m having trouble thinking of a use case for this. The only thing I can think of is if you have a large file and want to edit the top (or some distinct portion) of the file in one window and a different portion in another window. Is there another reason you would want this?

        1. 3

          If that’s the use case, CoVim might be a close approximation.

          1. 3

            Similar to Emacs' C-x 5 2 I would guess: you open a new window (a frame in Emacs parlance) that contains the same list of buffers as the original. You now have two independent windows that have access to the same opened buffers and that you can move, resize, put on different virtual desktops, etc. One use case would be to put one window on each monitor.

            1. 1

              Exactly.