NanoooK@sh.itjust.works to EmacsEnglish · 4 days agoEmacs: a basic and capable configurationprotesilaos.comexternal-linkmessage-square6fedilinkarrow-up111arrow-down10cross-posted to: hackernews@lemmy.bestiver.se
arrow-up111arrow-down1external-linkEmacs: a basic and capable configurationprotesilaos.comNanoooK@sh.itjust.works to EmacsEnglish · 4 days agomessage-square6fedilinkcross-posted to: hackernews@lemmy.bestiver.se
minus-squarebeleza pura@lemmy.eco.brlinkfedilinkarrow-up2·4 days ago Use ~/.emacs.d/init.el for your configurations. If there is an ~/.emacs file on your system, make sure to delete it why? does init.el have any advantage over .emacs? personally, i like using .emacs bc then, if anything goes wrong, i can just nuke .emacs.d and let my .emacs set everything up from scratch
minus-squaredavelAlinkfedilinkEnglisharrow-up1·edit-24 days ago why? does init.el have any advantage over .emacs? Presumably because of the very next point, #2: “Put all auto-generated configurations in a separate file.” If you’re going to use more than one config file, then that means you need to go with the .emacs.d directory route.
minus-squarebeleza pura@lemmy.eco.brlinkfedilinkarrow-up1·4 days agodo you? you can set a different custom file from .emacs just fine and i’ve seen it done before. unless i’m missing something, i believe that’s not it
minus-squaredavelAlinkfedilinkEnglisharrow-up2·edit-24 days agoI’m far from an Emacs expert. If you say so, I believe you. One reason I do it is because I made ~/.emacs.d a git repo.
minus-squarebeleza pura@lemmy.eco.brlinkfedilinkarrow-up1·4 days ago I made ~/.emacs.d a git repo. ooh, interesting. though i’m a bit squeamish about mixing tracked content and “build artifacts” (in this case, installed packages).
minus-squaredavelAlinkfedilinkarrow-up3·4 days ago$ cat ~/.emacs.d/.gitignore /auto-save-list/ /elpa/ /init.el~ /transient /org-roam.db /.org-id-locations $
why? does
init.elhave any advantage over.emacs?personally, i like using
.emacsbc then, if anything goes wrong, i can just nuke.emacs.dand let my.emacsset everything up from scratchPresumably because of the very next point, #2: “Put all auto-generated configurations in a separate file.” If you’re going to use more than one config file, then that means you need to go with the
.emacs.ddirectory route.do you? you can set a different custom file from
.emacsjust fine and i’ve seen it done before. unless i’m missing something, i believe that’s not itI’m far from an Emacs expert. If you say so, I believe you.
One reason I do it is because I made
~/.emacs.da git repo.ooh, interesting. though i’m a bit squeamish about mixing tracked content and “build artifacts” (in this case, installed packages).
$ cat ~/.emacs.d/.gitignore /auto-save-list/ /elpa/ /init.el~ /transient /org-roam.db /.org-id-locations $