3 ms·
Alternatively, you can use something which saves in a format that would be trivial to make a replacement for reading/writing it. One example is jrnl[1]. Each j
by craftyguy 8y ago
Alternatively, you can use something which saves in a format that would be trivial to make a replacement for reading/writing it.
One example is jrnl[1]. Each journal (collection of entries) is written in a flat text file. You can optionally encrypt it with AES. They even give you reference code on how you could decrypt it yourself[2].
If jrnl stops being a thing, I can probably re-implement all of its functionality in a day. Or someone else can. Its output is very simple.
1. http://jrnl.sh/overview.html http://jrnl.sh/overview.html
2. http://jrnl.sh/encryption.html#manual-decryption http://jrnl.sh/encryption.html#manual-decryption
- phirschybar 8y agoI used jrnl.sh for about a year. I was able to extend it to parse the output so I could do some analysis on what I had written (I was using it partially to track time spent on certain tasks). However, I came to find that write long-form on the command line is just awkward. Lately I have been using checkvist.com which has been working out great.
- extropic-engine 8y agoI actually wrote my own jrnl command as a shell one-liner: pushd $JRNL_DIR && git pull && echo "##### "(date) >> (date "+%Y-%m-%d.txt") && vim (date "+%Y-%m-%d.txt") && git add *.txt && git commit -m "jrnl "(date "+%Y-%m-%d.txt") && git push && popd