A basic yet fully capable setup for GNU Emacs. It covers all the essentials.
  • beleza pura@lemmy.eco.br
    2·
    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

    • davel [he/him]@lemmy.mlEnglish
      1·
      4 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.

      • beleza pura@lemmy.eco.br
        1·
        4 days ago

        do 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

        • davel [he/him]@lemmy.mlEnglish
          2·
          4 days ago

          I’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.

          • beleza pura@lemmy.eco.br
            1·
            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).

            • davel [he/him]@lemmy.ml
              3·
              4 days ago
              $ cat ~/.emacs.d/.gitignore 
/auto-save-list/
/elpa/
/init.el~
/transient
/org-roam.db
/.org-id-locations
$