spaceneovim-layers

While Oni is still very young, it looks like one of the more promising Neovim frontends, and the development is progressing quite fast! If you are one of those types that often switch between editors, like me, then you might want to retain some of the muscle memory you've built up in stuff like Atom/VSCode/Whatever. I started creating a layer[0] for SpaceNeovim to replicate some of the common keybindings, such as Cmd+s for save, Cmd+w for closing tabs, Cmd+[1-9] for switching tabs etc. If anyone is interested in getting this, without going full in with SpaceNeovim, they can extract it from [1], which currently handles both VimR and Oni (different key for CMD), but you could simplify it to not use exe if you wanted to. It requires that you load your init.vim, so "oni.loadInitVim": true needs to be set in the Oni config. Another thing, you

I am sorry for that issue, and sorry for all the emails,but SpaceVim is not only copy the name of spacemacs,it has many important ideas of spacemacs, such as layers(plugin and config groups), leader guide,and mappings fuzzy searching. why I create SpaceVim, instead of support space-vim, I think space-vim is just a copy of https://github.com/ctjhoa/spacevim and https://github.com/Tehnix/spaceneovim-layers and https://github.com/Tehnix/spaceneovim BTW space-vim's some syntax script is copy from https://github.com/junegunn/vim-plug and install script is just copy from spf13. so I do not want to support it, but when I create SpaceVim, and post blog anout SpaceVim, the author of space-vim comments a lot of unfriendly message. and here is the link. so I will apologies to all the people who receive my emails about SpaceVim, but I will not apolo

Just to share a little about the motivation of this: Switching back-and-forth a bit between Spacemacs and Neovim, I got inspired by spacevim[0] and thought to myself "Hey, that's a great idea!", and so I went into my first time actually toying with vim script (love-hate relationship atm). The result of the last couple of days so far is the ground work for a Neovim specific port of Spacemacs, SpaceNeovim[1]. The major difference between this and the existing spacevim is that the layers are separated out from the core, and can be updated via an editor command (calling git pull). It makes it a lot nicer to add new layers later on (oh, and of course also the fact that I've dropped any though of vim support). Contributions or feedback are more than welcome! :) The easiest way, if you want, is probably to contribute a layer, or expand on an exi

Switching back-and-forth a bit between Spacemacs and Neovim, I got inspired by https://github.com/ctjhoa/spacevim and thought to myself "Hey, that's a great idea!", and so I went into my first time actually toying with vim script (love-hate relationship atm). The result of the last couple of days so far is the ground work for a Neovim specific port of Spacemacs, located here https://github.com/Tehnix/spaceneovim. The major difference between that and the existing spacevim is that the layers are separated out from the core, and can be updated via an editor command (calling git pull). It makes it a lot nicer to add new layers later on (oh, and of course also the fact that I've dropped any though of vim support). Contributions or feedback are more than welcome! :) The easiest way, if you want, is probably to contribute a layer, or expand on