Like, that spreadsheet example seems clunky to me, why would I want to use this?
Like, that spreadsheet example seems clunky to me, why would I want to use this?
Spreadsheets.. personally, never had the need to use formulas, but they are very nice when you need.. well, to organize information in tables. 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?
, 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 | %? | | | |")))
"sleep table" is the heading, under which the table is contained. So:- 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 :).
In large, it is Emacs taken to an extreme. With the major feature point that all cards are on the table. Meaning the file you get at the end, is just plain text. There is no need to ever worry about export of data being locked out from you. Yes, using it is currently best exemplified with Emacs. No, nothing is forcing that.
- teaching classes and grading students - working on a quote / invoice for a customer (I add numeric properties to an org item, org gather them in a table, and I add columns to that to get sums, taxes, discounts, etc) - designing my woodworking and other building stuff, for cutlist and so on
I am not the kind of guy that lives in emacs, I only use it for org mode, in a way that resembles a scientific notebook, mixing text, data and code.
I would not force it onto anyone, but using anything else feels backwards.
So far, this could be easily done in markdown, or even plain text. But then I tally up the points, and convert them to a grade based on some simple equation in a table. My colleagues need to do this in a separate Excel sheet. I can do it right in my org document.
When editing, it updates the width of columns automatically and supports tabbing through, along with re-arranging rows using common shortcuts within org mode.
The formula functionality is pretty useful too, although I rarely use it and working it out is a bit of a puzzle still.
I also use org's ability to show properties as a table. When I read something I write a little review for myself and have some relevant info in the properties drawer. I can toggle a table view to see and sort all the properties.
Also, stubbornly, I prefer my comfortable emacs environment to the clicky unfamiliar interface of something like Google Sheets / Excel. Finally, org-export is fairly infinite in potential. I actually sync these notes to GitHub, which displays the org file as Github-Flavored Markdown -> HTML without even needing to export. The tables export very nicely, and are easily consumable in a read-only fashion by those who asked for them.
| -1 | req. | 100 | 100 | 50 |
| 3 | milk | 2.92| 4.37| 3.5|
| # | |-91.2|-86.8|-39.5|
#+TBLFM: @>$3..$5=(@<$1..@>>$1)*(@<..@>>)Source: I use org-mode for project notes, and they do end up with a lot of tables.