4 ms·

I disagree. Using and customizing SpaceMacs is considerably different from using plain emacs. They use their own config system, their own plugin system (aka l

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.
- Gaelan 10y ago
  If you delete //bin/ Ubuntu just becomes regular Linux.
  - eriknstr 10y ago
    Bad example. Most Linux distros have plenty of changes to the kernel itself also.
    - Gaelan 10y ago
      Changes to the code or just compile-time flags and/or additional modules?
weaksauce 10y ago
It's a well thought out config for Emacs. A layer is just a list of use package statements with some config to make it work with the leader concept and vim bindings if that's set. You can still install Melpa packages quite easily and you can still bind keys however you want. It's still 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.
Gaelan 10y ago
If you delete //bin/ Ubuntu just becomes regular Linux.
- eriknstr 10y ago
  Bad example. Most Linux distros have plenty of changes to the kernel itself also.
  - Gaelan 10y ago
    Changes to the code or just compile-time flags and/or additional modules?

weaksauce 10y ago

It's a well thought out config for Emacs. A layer is just a list of use package statements with some config to make it work with the leader concept and vim bindings if that's set. You can still install Melpa packages quite easily and you can still bind keys however you want. It's still Emacs.