6 ms·

1. You shouldn't be updating your `.gitignore` continuously. You need to ignore everything and explicitly define exceptions e.g. * !.gitignore !init.el

by rafiei 9y ago

1. You shouldn't be updating your `.gitignore` continuously. You need to ignore everything and explicitly define exceptions e.g. * !.gitignore !init.el 2. The reason I prefer ~/.emacs.d/ is that I have it in a git repo and on every system, I'll just clone the repo and soft link it in the home directory. This way, I have only one directory inside home about emacs within which my files are explicitly separated and tracked. P.S. I've recently tried to move from Spacemacs to Emacs and by no means a pro, so the process I've described may not be optimal.

sigjuice 9y ago
1. I still need to grow my .gitignore file as I add more .el files of my own. 2. A similar scheme would be to maintain a directory called ~/elisp in git and make ~/.emacs a symlink to ~/elisp/emacs. And pretend that ~/.emacs.d/ does not exist.
- rafiei 9y ago
  1. Perhaps make a new directory `.emacs.d/elisp`, append it to your path and add your files in it and have .gitignore not ignore the directory? 2. You could!
TeMPOraL 9y ago
I solve this issue by using my own config directory; this way I soft-link two things from my dotfiles repo: - .emacs - which defines my config dir and loads everything in there - my own config dir (called .emacs.conf), in which I have lots of .el files with specific configurations Emacs packages still write by default to .emacs.d, and this way I don't have to care about any of that when moving between machines, because my configuration and Emacs's ongoing state are separate. To be honest, though, I'll probably be migrating into a single-file literate solution soon, which will render my own config directory unnecessary.
- geokon 9y ago
  So each time you launch emacs you have to point it to your init file?
  - TeMPOraL 9y ago
    No. My .emacs has a code snippet that points Emacs to another directory for my own configs. I softlink both .emacs and the config directory.
- smnscu 9y ago
  I do this as well! I have this repo [0] at ~/cfg, then I symlink what I need [1] as an init script. My end goal is to be able to run a single script and get everything [2] set up on a new machine (I change machines somewhat frequently and I got the manual process to under 45 minutes, so there's room for improvement). More on setting up Macs [3]. There is also GNU Stow [4] that does something similar, and probably better. 0: https://github.com/andreis/cfg https://github.com/andreis/cfg 1: https://github.com/andreis/cfg/blob/master/init.sh#L64-L69 https://github.com/andreis/cfg/blob/master/init.sh#L64-L69 2: brew and brew cask, dotfiles ofc, and a _lot_ of system settings on mac os can be changed via the CLI, see 3: https://github.com/iCHAIT/awesome-macOS#setup https://github.com/iCHAIT/awesome-macOS#setup 4: http://brandon.invergo.net/news/2012-05-26-using-gnu-stow-to-manage-your-dotfiles.html http://brandon.invergo.net/news/2012-05-26-using-gnu-stow-to...
- frumiousirc 9y ago
  I used to do it that way. I've switched to `vcsh` to let me keep various files directly in my ~/ directory in various different git repos without needing a ~/.git/ marking the whole thing as a working directory.

by rafiei 9y ago

sigjuice 9y ago

1. I still need to grow my .gitignore file as I add more .el files of my own. 2. A similar scheme would be to maintain a directory called ~/elisp in git and make ~/.emacs a symlink to ~/elisp/emacs. And pretend that ~/.emacs.d/ does not exist.

rafiei 9y ago
1. Perhaps make a new directory `.emacs.d/elisp`, append it to your path and add your files in it and have .gitignore not ignore the directory? 2. You could!

TeMPOraL 9y ago

I solve this issue by using my own config directory; this way I soft-link two things from my dotfiles repo: - .emacs - which defines my config dir and loads everything in there - my own config dir (called .emacs.conf), in which I have lots of .el files with specific configurations Emacs packages still write by default to .emacs.d, and this way I don't have to care about any of that when moving between machines, because my configuration and Emacs's ongoing state are separate. To be honest, though, I'll probably be migrating into a single-file literate solution soon, which will render my own config directory unnecessary.

geokon 9y ago
So each time you launch emacs you have to point it to your init file?
- TeMPOraL 9y ago
  No. My .emacs has a code snippet that points Emacs to another directory for my own configs. I softlink both .emacs and the config directory.
smnscu 9y ago
I do this as well! I have this repo [0] at ~/cfg, then I symlink what I need [1] as an init script. My end goal is to be able to run a single script and get everything [2] set up on a new machine (I change machines somewhat frequently and I got the manual process to under 45 minutes, so there's room for improvement). More on setting up Macs [3]. There is also GNU Stow [4] that does something similar, and probably better. 0: https://github.com/andreis/cfg https://github.com/andreis/cfg 1: https://github.com/andreis/cfg/blob/master/init.sh#L64-L69 https://github.com/andreis/cfg/blob/master/init.sh#L64-L69 2: brew and brew cask, dotfiles ofc, and a _lot_ of system settings on mac os can be changed via the CLI, see 3: https://github.com/iCHAIT/awesome-macOS#setup https://github.com/iCHAIT/awesome-macOS#setup 4: http://brandon.invergo.net/news/2012-05-26-using-gnu-stow-to-manage-your-dotfiles.html http://brandon.invergo.net/news/2012-05-26-using-gnu-stow-to...
frumiousirc 9y ago
I used to do it that way. I've switched to `vcsh` to let me keep various files directly in my ~/ directory in various different git repos without needing a ~/.git/ marking the whole thing as a working directory.