diff options
| -rw-r--r-- | 2020/info/10.md | 1 | ||||
| -rw-r--r-- | 2020/info/11.md | 2 | ||||
| -rw-r--r-- | 2020/info/12.md | 2 |
3 files changed, 4 insertions, 1 deletions
diff --git a/2020/info/10.md b/2020/info/10.md index a263b119..3bea9f70 100644 --- a/2020/info/10.md +++ b/2020/info/10.md @@ -37,4 +37,3 @@ in. And programming in OCaml was so nice in there :) dynamic blocks: <https://github.com/alphapapa/org-ql#dynamic-block> - Blog: <https://ag91.github.io> - <https://ag91.github.io/blog/2020/09/27/org-agenda-and-your-future-or-how-to-keep-score-of-your-long-term-goals-with-org-mode/> - diff --git a/2020/info/11.md b/2020/info/11.md index 716f1843..0305982f 100644 --- a/2020/info/11.md +++ b/2020/info/11.md @@ -32,6 +32,7 @@ view. ## Are you only using linear next-task-method or do you use org-edna to mark tasks even in other projects as NEXT? Currently I only use linear next-task-method, for two reasons. One is a technical reason, another one is part of my current approach to GTD: + - I haven't yet had a reason to consider that, say, a project might block another project, or that an action might block a project - possibly I haven't tried to do complex enough things in my life yet, @@ -55,6 +56,7 @@ to decide what to do with the incubated item: incubate it again, make it into a project, discard it, etc. My "incubate" file has a bunch of top-level headlines like "To Read", "To Watch", "To Eat", "To Visit", etc. + - That sounds similar to SOMEDAY-list, but processed on per-item basis. If you decide to re-incubate an item, how to you chose the new time? diff --git a/2020/info/12.md b/2020/info/12.md index 2ea7dea6..f506ba5e 100644 --- a/2020/info/12.md +++ b/2020/info/12.md @@ -38,6 +38,7 @@ For knowledge management: many files (see also org-roam). Otherwise: one big file to have everything (todos, projects, notes, etc…) in one single place. + - Possible walk around by some hacks? ## Do you switch between British and French accents? @@ -60,6 +61,7 @@ knowledge management and those don't get archived most of the time. ## Does it not consume more resources and time to load multiple files than a large file of the same contents? Dealing with hiding contents is computationally expensive. + - I doubt it is correct. Emacs display engine is quite effective dealing with invisible text. Moving cursor around is affected, but I never heard (and never experienced) issues with scrolling on large |