Neovim

Neovim is a refactor, and sometimes redactor, in the tradition of Vim. It is not a rewrite but a continuation and extension of Vim. Neovim is built for users who want the good parts of Vim, and more.
Here are 1,965 public repositories matching this topic...
-
Updated
Apr 1, 2020 - TypeScript
-
Updated
Oct 3, 2020 - Swift
-
Updated
Oct 1, 2020 - Vim script
-
Updated
Jun 16, 2020 - Vim script
-
Updated
Sep 17, 2020 - Vim script
-
Updated
Sep 4, 2020 - Vim script
-
Updated
Sep 19, 2020 - Vim script
Neovim terminal mode
Hi,
When I run my tests using the neovim
strategy, it opens a new terminal but auto focus on the buffer. Then I have to press <C-o>
to not close the buffer and go back to my split pane.
Is there a way to have it open but not switch my focus to the newly opened pane automatically?
-
Updated
Dec 8, 2019 - Vim script
-
Updated
Oct 2, 2020 - Vim script
-
Updated
Sep 18, 2020 - CSS
I actually wanted to investigate #287 because I was curious how the TERM variable is changing the behavior in neovide. I started the same way I always do, I get a fresh master release build without any modifications for my baseline.
That didn't quite workout though. This is what happens when I use my usual neovim init:
<img width="910" alt="0" src="https://user-images.githubusercontent.com/1
-
Updated
Oct 23, 2018 - Python
-
Updated
Aug 22, 2020 - Vim script
-
Updated
Oct 1, 2020 - Vim script
-
Updated
Sep 11, 2020 - Vim script
-
Updated
Apr 22, 2020 - Vim script
Created by Thiago de Arruda
Released January 31, 2014
Latest release 2 months ago
- Repository
- neovim/neovim
- Website
- neovim.io
- Wikipedia
- Wikipedia
Actual behaviour
When simply trying to edit some additional files I often type
:e *.js
or something similar; this almost ALWAYS results inE77: Too many file names
.Expected behaviour
It's pretty clear what the user wants in this situation; they want to open the files as buffers! I'm sure there are legacy reasons for this error, but it's a pretty poor experience these days that