Actual behaviour

When simply trying to edit some additional files I often type :e *.js or something similar; this almost ALWAYS results in E77: 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

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?

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

Difficulty doing initial setup of the plugin
3rd party description of setup steps:
https://atlas-vim.readthedocs.io/vim/plugged/vim-ctrlspace/README/

• convert to plugin vim docs?
• create wiki pages on this repo?