dot-doom VS git-auto-commit-mode

I switched from a hand-maintained config to Doom last year, and I can highly recommend it. It's very well organized, the community is very friendly and it works great. If you are interested, my config is at https://github.com/zzamboni/dot-doom/blob/master/doom.org.

This sets the default for all the emacs-lisp blocks in the file, but you can still selectively write other blocks to different files, or not at all by specifying :tangle no. This way you can easily tangle multiple destination files from a single Org file. For an example, you can see my doom.org file, from which Doom's init.el, config.el and packages.el are all tangled.

In my config I have a hook I can call after saving the .org file to automatically export it and update the open browser to the current slide. This makes the process of updating/viewing the presentation a lot smoother. You can find my config here: https://github.com/zzamboni/dot-doom/blob/master/doom.org#revealjs-presentations

Note that I said my "old config". A few months ago. I decided to try Doom Emacs. Over a couple of days, I ported most of the important bits of my decades-old, hand-maintained config, and in the process realized I could get rid of a lot of scaffolding (like the whole package-management bits in your config) by virtue of Doom's existing mechanisms, and also I could omit a lot of the configuration because Doom includes decent defaults for many things. I have not regretted moving to Doom. You can find my new config at https://github.com/zzamboni/dot-doom/blob/master/doom.org.

If you use use-package, it works well to define the package to be loaded :after org. I have lots of examples in my old emacs config, for example: (use-package ox-hugo :defer 3 :after org :custom (org-hugo-use-code-for-kbd t)) I now use Doom Emacs, but the same technique can be used with use-package!. For example, from my Doom Config: (use-package! ox-leanpub :after org :config (require 'ox-leanpub-markdown) (org-leanpub-book-setup-menu-markdown)) HTH

git-auto-commit-mode for auto committing & pushing from eMacs on save after specified timeout

If you're wanting to use git, but not worry about staging/committing, i've used this package on my org repo. https://github.com/ryuslash/git-auto-commit-mode

I use git-auto-commit-mode. Just install the package and then enable it whenever you visit a file in Org-Roam:

I just looked around a bit and found a git-auto-commit-mode.

You can use the package git-auto-commit for timed automatic commits. If you use Doom Emacs, as it's indicated next to your username, you can enable the module vc which contains the package git-timemachine. This package has a command that allows you to easily browse through all your commits. If you're not using Doom, you can just install a configure git-timemachine the package by itself for the same effect.

I did find https://github.com/ryuslash/git-auto-commit-mode which lets you enable it from .dir-locals which you could commit to a repo and make it a project so its auto applied when loading.

I’ve been using git-auto-commit-mode with a directory-local variable in my org-agenda-dir. You can set it to push automatically also. It’s worked great for a few years now.

I do this with magit in conjunction with git-auto-commit-mode. With those two packages installed and configured, you can bind `save-all-buffers` and `magit-push-current-to-upstream` to simple key chords, then just invoke those two commands in succession and all new changes will be staged, committed, and push to GitHub.

Version control with git and magit. I use git even for non-software projects, like writing. For writing projects where you don't want to interrupt your focus/workflow to commit, you might find git-auto-commit-mode helpful.