What is your workflow of maintaining logs of literate scripts? I converted most of my scripts to org-mode and tangle them out to scripts for running them. I want to be able to run them within org-babel itself. I use mostly python and bash. I have two laptops one personal and one for work and a desktop. Mostly I want my laptop and desktop in sync so that I can work in either of them depending upon the need. When I want to install or update any of the tools I use in one system I want that to be replicated in the other, not automatically.
I also need to version the literate scripts, in the sense with history visible in the org file itself. I want the org file to capture my thought flow and the evolution of the code so that I can understand it later by just looking through the file not by meddling with git.
Does any have similar need and a workflow I can copy?
You must log in or register to comment.
Why are you working so hard to avoid source control? It solves the following:
- assuming you use github, gitlab or chiselapp (fossil hosting), it provides a practically free way to keep multiple machines in sync. You could also just use something like dropbox or an S3 bucket.
- if I wanted wanted to see commit history (what you’re calling logs) in the file I’m working on, I’d create a src block that ran a command against the source control system and formatted the results appropriately. While I haven’t done this with commit messages, I have done it on export to record the exported version.
I avoid git (work) or fossil (home) with literate org files as I don’t want a full repository for a single file so I’ll use rcs or sccs with emacs vc-mode.