Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

extract layers mechanism as standalone elisp package #3590

Closed
thkoch2001 opened this issue Oct 29, 2015 · 4 comments
Closed

extract layers mechanism as standalone elisp package #3590

thkoch2001 opened this issue Oct 29, 2015 · 4 comments
Labels
- Mailling list - Core Feature request stale marked as a stale issue/pr (usually by a bot)

Comments

@thkoch2001
Copy link

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.

@a13ph
Copy link

a13ph commented Oct 29, 2015

👍 For a modular Emacs distro it's strangely not modular in some regards
And increase in userbase will probably lead to more layers available and improvements of layer system itself

@syl20bnr
Copy link
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...).

@a13ph
Copy link

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
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)

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Feb 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
- Mailling list - Core Feature request stale marked as a stale issue/pr (usually by a bot)
Projects
None yet
Development

No branches or pull requests

5 participants