summaryrefslogtreecommitdiffstats
path: root/2020/info/11.md
diff options
context:
space:
mode:
Diffstat (limited to '2020/info/11.md')
-rw-r--r--2020/info/11.md2
1 files changed, 2 insertions, 0 deletions
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?