this post was submitted on 21 Oct 2023
1 points (100.0% liked)

Emacs

313 readers
3 users here now

A community for the timeless and infinitely powerful editor. Want to see what Emacs is capable of?!

Get Emacs

Rules

  1. Posts should be emacs related
  2. Be kind please
  3. Yes, we already know: Google results for "emacs" and "vi" link to each other. We good.

Emacs Resources

Emacs Tutorials

Useful Emacs configuration files and distributions

Quick pain-saver tip

founded 1 year ago
MODERATORS
rglullis@communick.news
raphael@communick.news
1
Workflow for maintaining logs of literate scripts using org-babel (alien.top)
submitted 1 year ago by paarulakan@alien.top to c/emacs@communick.news
1 comments fedilink hide all child comments
 

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 are viewing a single comment's thread
view the rest of the comments
[–] fragbot2@alien.top 1 points 1 year ago

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.