org-autolist VS git-auto-commit-mode

Because org-autolist overrides org-return with :around advice, it might not be easy. That's why I suggest opening an issue in https://github.com/calvinwyoung/org-autolist

I use org-autolist.el to automatically continue lists. One issue though is that if I want to write some text between items in the list, I can't continue the list from the last number. For example, if I have an enumerated list with two items in it and some text in between, I get the following....

https://github.com/calvinwyoung/org-autolist - if someone else will look for the same.

C-j does not indent. As for what you're looking for: https://github.com/calvinwyoung/org-autolist

Off-note: explore org-autolist. It makes orgmode's lists so much easy to use.

I didn’t verify with evil mode, but org-autolist might solve your problem: https://github.com/calvinwyoung/org-autolist

One package that was helpful for note-taking was org-autolist. I took all my notes as outlines and that made it faster.

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.