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

Recommended strategy for version controlling private layers #10390

Closed
dangom opened this issue Feb 25, 2018 · 5 comments
Closed

Recommended strategy for version controlling private layers #10390

dangom opened this issue Feb 25, 2018 · 5 comments
Labels
- Forum - stale marked as a stale issue/pr (usually by a bot)

Comments

@dangom
Copy link
Contributor

dangom commented Feb 25, 2018

As per the spacemacs documentation, private layers should be placed in the private folder within .emacs.d.

This makes it hard to properly version control said private layers, as they are nested within the spacemacs repo. Although it does work to have a git repo nested within a git-ignored folder of a parent repo, this setup is rather fragile. A git clean -fdx would nuke everything.

What is the recommended setup for developing private layers?

@sdwolfz
Copy link
Collaborator

sdwolfz commented Feb 25, 2018

When I have a git repository inside an ignored directory of another, when I do git clean -fdx the inner respository is skipped.

Try doing a git clean -fdxn (n for dry ruN) and see if the private layer gets skipped.

@bmag bmag added the - Forum - label Feb 25, 2018
@bmag
Copy link
Collaborator

bmag commented Feb 25, 2018

Another option is to have a ~/.spacemacs.d directory. You use ~/.spacemacs.d/init.el as your dotspacemacs file instead of ~/.spacemacs, and you put private layers in that directory as well. It should be mentioned in the docs somewhere.

@dangom
Copy link
Contributor Author

dangom commented Feb 25, 2018

@sdwolfz Indeed, I didn't know that other repos would be skipped. Quite a positive surprise =)
In my case, the private layer would survive, but all my non vc'd snippets would be removed.

@bmag The docs do mention that. Not in the private layer README, but here.

@fiveNinePlusR
Copy link
Contributor

Is there really any benefit to having two ways to do this? having the default way to setup spacemacs being as a configuration directory under ~/.spacemacs.d is a clear win in usability to me. you could also have the folder template skeleton for layers, snippets whatever else put in place with a few examples to make adoption easier for new users. I say the default should be the configuration directory separate from ~/.emacs.d

@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 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
- Forum - stale marked as a stale issue/pr (usually by a bot)
Projects
None yet
Development

No branches or pull requests

4 participants