> For example, I'm using it with org-capture to track sleep data straight into the table, which results in a table row for each day (with an auto-generated timestamp).
I'm curious how one would do that. Would you mind sharing your capture template?
I'm curious how one would do that. Would you mind sharing your capture template?
, but sleep logging is in a 'private' config for some reason, so I'll just paste it here:
(setq --my/extra-capture-templates
'(("s"
"sleep"
table-line
(file+headline "/path/to/capture.org" "sleep table")
"| %U | %? | | | |")))
- I press the capture hotkey (F4 for me)
- then 's' which prompts me for a table line
- %U automatically substitutes the timestamp
- the cursor is placed at %? (second column), so I can just log whatever I need to, tab for the next column, and then finish capture
I track my blood pressure similarly. The entry is simple and I can read the csv into R/python whenever I want to visualize it.
That org capture template will feed new data into a table; below it, in the same .org file, you can keep your R code and your Python code and whatever other code you prototype (I often write Elisp code), and you can execute all that code inside the .org file.
This approach is not giving you any new features, it's just optimizing for convenience. Think of .org files as Jupyter notebooks on steroids :).