-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
use private layers to customise layers? #5375
Comments
User configuration should be called in
Using a layer is another, but heavier, solution. |
@StreakyCobra Excellent! Just what I wanted. One small question though. If I use the |
You can also create more than one private layer, so you can just split it out into xxh-org layer, for example. |
I would just add one more point to @StreakyCobra's suggestion. I do use |
@xiaoxinghu Using and loading another file is for structuring your code. For the lazy loading part, you can use the same mechanism as used in the layers, i.e. |
Closing this issue for being inactive. Also discussions contain possible solution. Also, there is somewhat outdated answer for exact question. |
I really like the concept of layer. But sometimes it doesn't feel exactly right. E.g. I have tons of customisation on org-mode. You can't expect a "right" config for everyone in terms of org-mode. And it is too big to be in
.spacemacs
file. So I created my own layer for it. But it is not exactly a new module. It is a big customisation on an existing one -- the org layer. I assume for now the private layer is the best way of doing this. Am I right? I am expecting a mechanism to customise a layer. Maybe it is redundant design since the purpose of layer is to customise. Thoughts?The text was updated successfully, but these errors were encountered: