Experimentation with bartib time tracking
bartib is a command line tool for time tracking. It had a good set of commands that were easy to learn and had a fair bit of depth. However, command args were awkward to present, and the forced project + description combo is not desired for my tracking.
Experimentation with bartib from 2023-05-15 to 2023-06-14
I developed some shell scripts to wrap the bartib command around https://github.com/charmbracelet/gum (nice command line utilities) and https://github.com/junegunn/fzf (fuzzy searching). I also wrapped the command reporting with a shell alias so I could keep logging breaks and filter them out in reporting. In the end, the habit of logging with this format didn't stick. I prefer hand-edited entries in a text file, and bartib forces the workflow on the command line due to verbose duration ranges and the forced project + description combo.
Now, my goal is to bring final improvements to my timelog tool and associated workflow. I want my custom timelog (for live, precise logging) format to map to hledger timeclock entries. Then, the combination of timedot (for approximate, retroactive logging) + timeclock (from timelog live logging) would be combined to collect duration of work tasks.