5 ms·

Ok, but what it is? The page doesn't explain it. The top page explanation refers to spacemacs and most vim users don't know spacemacs. Is it a vim plus a bundl

• Shicholas 10y ago
  it's emacs with vim controls. FWIW, I wouldn't compare emacs with vim in this set up, but with something like tumx instead (and imo what emacs offers is better than tmux).
  • TheDong 10y ago
    They're not asking what space-emacs is, but what this linked page is. This page is not emacs. This page is just a bunch of neovim plugins, as OP surmised.
  • bn-usd-mistake 10y ago
    No it's not. This is actually vim, just with some configuration and plugins. You are probably talking about [Spacemacs](http://spacemacs.org/ http://spacemacs.org/)?
• arnarbi 10y ago
  It's a distribution, bundling vim with a whole bunch of plugins and configuration that's supposed to work out of the box. Spacemacs is the same for Emacs.
  • elcapitan 10y ago
    Thanks, that's the tldr I was looking for too.
  • jasonm23 10y ago
    I wish people stopped calling a shared config a 'distribution' In both Spacemacs and Spacevim, all that's being provided is a config. No runtime, no package manager, no changes to the actual binaries of either app. It's hyperbole.
    • deleted 10y ago
      [deleted]
    • the_duke 10y ago
      I disagree. Using and customizing SpaceMacs is considerably different from using plain emacs. They use their own config system, their own plugin system (aka layers), and the user experience is very different, right from the start. Of course it's emacs underneath, and you can still do much as with plain emacs, but it's different enough for it to be more than "just a config for emacs".
      • eyko 10y ago
        It's just a config for emacs. Sure it has some functions and life-cycle hooks for you to change a few things here and there, but in the end it's a glorified config. You delete .emacs.d and you're back to default emacs.
        • the_duke 10y ago
          It's not just a config, it's plenty of code. In emacs, thanks to Elisp, you can't really distinguish between a config and a plugin, because most 'configs' use actual code to (often extensively) alter the editors behaviour.
          • eyko 10y ago
            If you're suggesting that config files don't have actual code then by that reasoning your .vimrc is in fact also not a config.
          • randomthrowr88 10y ago
            A config in my mind gets me to a state of being. Plugins let me extend that state, but may not make it into a "config". A config can contain a plugin (which may have its own config!). It's silly semantics all the way down! None of this stuff is rigidly defined because it's pointless to do so, generally.
        • 10y ago
  • jeremiep 10y ago
    The difference in Emacs vs Vim is Emacs-Lisp. This means Spacemacs is incredibly more powerful than Spacevim from a conceptual point of view. Emacs is a living, self-documenting environment and Spacemacs extends it quite a lot. This Lisp environment is very different from a set of plugins developed offline or mere configurations. Calling Spacemacs a bunch of plugins and configuration is like calling any conventional program a plugin of its language and runtime. Plugins attach to an environment with a specific runtime API, instead of extending said API, blurring the line between runtime and extension in the process.
• wsdjeg 10y ago
  SpaceVim is a modular Vim distribution. but it has same idea with spacemacs. the goal of SpaceVim is to make user get a better experience of vim/neovim.