bashlog

I do something similar. Simple highlights on to-do items helps a lot. And using bullet journal style to-do markers help organization. - [ ] todo - [x] done - [-] failed - [v] dropped - [>] migrated - [^] scheduled - [<] delegated Easy to set up vim highlighting on those patterns. I have some examples here: https://jodavaho.io/posts/bullet-journalling.html And a bash setup here https://github.com/jodavaho/bashlog

I have a text file in a known location. It's backed up on git. I can open and edit that file quickly using bash. From within VIM I can quickly commit to reduce the # keystrokes. More details: https://github.com/jodavaho/bashlog#git-integration (Really though, you can just save as an environment variable your file location) The text file is structured with space-delimited text, like this: https://github.com/dkogan/vnlog My current structure for tracking a contribution to an OKR item (e.g. "meditate") by date (e.g., 2020-01-15) and amount (e.g., "1") is simply: "# date item amount" Easy to open, easy to plop down today's date and the item / amount. Save multiple date/item entries and add them inscripts ... Easy to save. Done. The work came in building stuff to plot it: I have other files that link "items" to goals or other metadata like ca

I link this all the time, but my system is almost the same! https://github.com/jodavaho/bashlog One command `log`, keeps files with YYYY-MM-DD.md and helps sync to github. I often edit my day's words, but don't much go back. When I do want to go back, I can just use `log 3/4/19` or `log yesterday`

Ive been writing almost every day for many years. My secret was to use Bash and write a few scripts to make it very easy to jot down thoughts. I also added a vim command to push it to github while editing. These just remove barriers to opening and syncing the file, but the concept is the same. You can see the result here: https://github.com/jodavaho/bashlog The result is a treasure trove of greppable data. Someday I was to apply some sentiment analysis ...

In case you still haven't found it, bashlog is here: https://github.com/jodavaho/bashlog

Same, of course. I added some bash aliases to make it much easier to write to the file, and use markdown instead to allow tracking todos easier. I also added a vim command to push it to github while editing. These just remove barriers to opening and syncing the file, but the concept is the same. You can see the result here: https://github.com/jodavaho/bashlog

Same, of course. I added some bash aliases to make it much easier to write to the file, and use markdown instead to allow tracking todos easier. I also added a vim command to push it to github while editing. These just remove barriers to opening and syncing the file, but the concept is the same. You can see the result here: https://github.com/jodavaho/bashlog

(too late to edit) Like this: https://github.com/jodavaho/bashlog