4 ms·

Obviously I'm biased since I built BrainTool because of my emacs/org use, but I also use markdowns and maintain the braintool.org blog on github in their markdo

Obviously I'm biased since I built BrainTool because of my emacs/org use, but I also use markdowns and maintain the braintool.org blog on github in their markdown. I don't find it more readable. Maybe it's a familiarity thing, anything specific you dislike? Anyway here's the definitive argument for org as markup of choice: https://karl-voit.at/2017/09/23/orgmode-as-markup-only/ https://karl-voit.at/2017/09/23/orgmode-as-markup-only/ It would for sure be nice to have a definitive spec to point to, independent of the emacs ecosystem. BTW see below the first few lines of my dev-log.org file for yesterday. I think its pretty readable! * <2022-03-30 Wed> ** DONE Today [83%] - [X] Call w alex - [X] Exercise - [X] instructions to Alex - [X] letter to Deignan - [X] taxes - [ ] styling for notes col ** DONE bug narrow edit card shows item under bullet which is confusing. :dev:099: ** DONE get rid of link in welcome topic, too confusing :dev:099: ** Instructions for running BrainTool locally: 1) Make sure you have git installed. (https://git-scm.com/download/mac) 2) Make a folder where you want to put the code

acquacow 5y ago
That's still too many formatting bits for me. My weekly todos look something like this: It uses a simialr format: YYYYMMDD - Task to be done - Subtask * Note about task / Task started/half done x Task completed ie: 20220328 - finish baselining instances for ami creation x server 1 / server 2 - server 3 * Make sure RH image is being used vs AWS provided AMI / verify routes exist for all subnets x snapshot instance X before users are added -- Dave
- ungamedplayer 5y ago
  You can have YYMMDD too.. its just how he's input it.
- emj 5y ago
  IMHO: Workflow, Text input fields and File formats are like APIs; if there is a way to abuse, hidden or public, then someone will use that in their process (https://xkcd.com/1172/ https://xkcd.com/1172/). So adhering to Org mode in your own parser will mean a lot of work anyway. There will always be some subtle point that make your format incompatible with a tool you want to use.
MattRix 5y ago
One of the clear problems I have with this format is that you have to write a dash in front of every todo. This may seem like a minor gripe, but when writing todos is by far the most common action, it really does increase the friction a lot.

acquacow 5y ago

That's still too many formatting bits for me. My weekly todos look something like this: It uses a simialr format: YYYYMMDD - Task to be done - Subtask * Note about task / Task started/half done x Task completed ie: 20220328 - finish baselining instances for ami creation x server 1 / server 2 - server 3 * Make sure RH image is being used vs AWS provided AMI / verify routes exist for all subnets x snapshot instance X before users are added -- Dave

ungamedplayer 5y ago
You can have YYMMDD too.. its just how he's input it.
emj 5y ago
IMHO: Workflow, Text input fields and File formats are like APIs; if there is a way to abuse, hidden or public, then someone will use that in their process (https://xkcd.com/1172/ https://xkcd.com/1172/). So adhering to Org mode in your own parser will mean a lot of work anyway. There will always be some subtle point that make your format incompatible with a tool you want to use.

MattRix 5y ago

One of the clear problems I have with this format is that you have to write a dash in front of every todo. This may seem like a minor gripe, but when writing todos is by far the most common action, it really does increase the friction a lot.