Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upextract layers mechanism as standalone elisp package #3590
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
a13ph
Oct 29, 2015
And increase in userbase will probably lead to more layers available and improvements of layer system itself
a13ph
commented
Oct 29, 2015
|
|
TheBB
added
Feature request
Core
labels
Oct 30, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
syl20bnr
Oct 30, 2015
Owner
The layer system is not finished.
I originally started to work on it outside of Spacemacs (see Crown repos) but I changed my strategy because nobody would have used it this way. I decided to start implementing it in my configuration as well as documenting it extensively. Few weeks later some people started to try it so the strategy seems to have work.
So basically speaking Spacemacs was a POC and a direct usable application of Crown. Spacemacs has grown quickly and so it took quite some time to implement the desired feature of the layer system without breaking people config.
I'll release the layer system as a stand-alone package at some point but there is still work to be done on it and I want to limit the scope of users to Spacemacs users for now because it makes things a lot easier to manage (especially backward compatibility etc...).
|
The layer system is not finished. I originally started to work on it outside of Spacemacs (see Crown repos) but I changed my strategy because nobody would have used it this way. I decided to start implementing it in my configuration as well as documenting it extensively. Few weeks later some people started to try it so the strategy seems to have work. So basically speaking Spacemacs was a POC and a direct usable application of Crown. Spacemacs has grown quickly and so it took quite some time to implement the desired feature of the layer system without breaking people config. I'll release the layer system as a stand-alone package at some point but there is still work to be done on it and I want to limit the scope of users to Spacemacs users for now because it makes things a lot easier to manage (especially backward compatibility etc...). |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
a13ph
Feb 25, 2016
I assume it would be wise to discuss these matters with JW, since he's author of use-package and quite a take on init file, which reminded me of Spacemacs layer system somewhat
Maybe not now, but just at some point. Since it's not urgent, scheduling a talk and asking him to look into our loading and layer setup earlier rather than later might give him time to assess and schedule well, too
(I'm just trying to make all parties happier here)
a13ph
commented
Feb 25, 2016
|
I assume it would be wise to discuss these matters with JW, since he's author of use-package and quite a take on init file, which reminded me of Spacemacs layer system somewhat |
thkoch2001 commentedOct 29, 2015
I believe the layers mechanism of spacemacs could also be interesting for people that want to keep using plain emacs but are looking for a good way to organize their configuration. (me ATM)
It might also help to make spacemacs more approachable. One can start using layers and maybe switch to full spacemacs later?
Hopefully it also becomes possible to use spacemacs layers in plain emacs and thus increase their userbase.