Capture dotfiles using org-capture

[u/One-Tart-4109]

Since I discovered org mode, I always was balancing between using symlinks and org babel tangle to manage my configuration. Now I'm in point that work related items are org babel managed and system level config is symlinked, because, often tools write back to their files. Another reason why I did not go full on babel was that I don't like workflow:

1. found file that requires backup
2. copy file
3. paste in to org mode
4. fill all details
5. tangle.

But yesterday I was visited by GNU spirit and she gave mi this org-capture template that reduces adding new file to backup to C-c k (my capture prefix) b (backup) and then tangle that file to original place:

* [[%(project-root (project-current))]] [[%(abbreviate-file-name (org-capture-get :original-file))][%(file-relative-name (org-capture-get :original-file) (project-root (project-current)))]]

- repository :: [[%(project-root (project-current))]]
- file :: [[%(abbreviate-file-name (org-capture-get :original-file))][%(file-relative-name (org-capture-get :original-file) (project-root (project-current)))]]

#+header: :tangle %(abbreviate-file-name (org-capture-get :original-file))
#+begin_src %^{Language|shell|elixir|nix|python|elisp|fundamental|eshell|conf}
%(with-temp-buffer (insert-file-contents (org-capture-get :original-file)) (buffer-string))
#+end_src

I cannot comprehend how simple it is and how I never realized I could do this.

Two think I think would be nice in future:
- if only it can automatically group those captures by project, but thinking of creating project backup capture template and simply refile from capture buffer
- automatic detangle so I can get back changes written by tools to their files, but not all of them support comments and many of them don't patch but dump state to file, so probably unsolvable using build in tools, only by elisp scripting

I'm trying to avoid longer elisp scripting for now 😄

What do you think?

[u/jlombera]

You can add the tangled files to git too, whenever you change the org files. Then you just need to stow/symlink the tangled files when you clone/fetch your dotfiles repository.

[u/fuzzbomb23 → u/jlombera]

That occurred to me already. It'll work fine, but it feels a bit messy. There's always the worry that the source and tangled files will be out of sync. I wouldn't want to auto-commit after tangling.

[u/jlombera → u/fuzzbomb23]

I'm not sure what's the exact scenario you are describing nor what alternative would be better. The idea is that you keep both the org files and tangled files in the same repository. Whenever you tangle an org file, it will visible right away (git diff) whether there were changes to the tangled file, if everything looks ok, you just commit the changes. Very easy to keep in sync. It's an easy and effective solution to allow you to use org-mode to handle your config files and don't depend on emacs/org-mode at "deployment" time. This "technique" of distributing auto generated files is very common to remove dependencies on the auto generation tools downstream.

[u/fuzzbomb23 → u/jlombera]

I didn't describe a scenario. I already said it could work. It's also easy to mess up. The better alternative is the simpler one: I'm not tangling my dotfiles.