summaryrefslogtreecommitdiffstats
path: root/2020/info/11.md
diff options
context:
space:
mode:
authorSacha Chua <sacha@sachachua.com>2020-12-01 00:44:21 -0500
committerSacha Chua <sacha@sachachua.com>2020-12-01 00:44:21 -0500
commit59a50e53ec403dcd3a78a20ab4d67817813e07ae (patch)
tree0469a3258e7d8272119a50338109170b8a465f33 /2020/info/11.md
parent6be6f782694313f7492164b60db640e78a2e3d58 (diff)
downloademacsconf-wiki-59a50e53ec403dcd3a78a20ab4d67817813e07ae.tar.xz
emacsconf-wiki-59a50e53ec403dcd3a78a20ab4d67817813e07ae.zip
Fix spaces
Diffstat (limited to '2020/info/11.md')
-rw-r--r--2020/info/11.md6
1 files changed, 0 insertions, 6 deletions
diff --git a/2020/info/11.md b/2020/info/11.md
index 10d5138e..3e8286a4 100644
--- a/2020/info/11.md
+++ b/2020/info/11.md
@@ -11,7 +11,6 @@ Bonus: there's even a few tests written for the package! We'll go
over those too.
<!-- from the pad --->
-
- Actual start and end time (EST): Start 2020-11-28T13.26.16; End: 2020-11-28T13.41.53
@@ -32,23 +31,18 @@ They stay where they are, because they belong to the project. Org-edna will auto
## 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, and so I've always been able to simplify what I had to do into linear projects, even if it was a simple linear project with a last task of "create a new project based on what I've learned"
-
- I have zero idea of how I would intelligently display this, yet, so I've stayed away from this. Contrary to most personal projects I've worked on, this one has "ease of use" front and center, so before implementing something like this, I'd need to know how to properly represent this: if possible, in the agenda view, and if not, I guess it would be in a HUD I would create for the package.
-
- <https://orgmode.org/list/87pn6zzoj7.fsf@localhost/> might be relevant. The feature request suggest a way to show notes dynamically in headlines.
## How do you make use of incubated items? Do they show up in the agenda for the whole day? That would be distracting, I guess.
I have a block of time, every morning, dedicated to processing the inbox and seeing what's on my plate for the day. I would use this time 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?
# Notes
-
- [speaker] I forgot to mention this in my talk because it's fairly recent: someone pointed me to screens that David Allen designed for "the ideal GTD app", which means I've got some path forward for making emacs the ideal GTD app (see <https://github.com/Trevoke/org-gtd.el/issues/21> )
- Showcases org-gtd: <https://github.com/Trevoke/org-gtd.el>
- Custom org-gtd-capture, but reusing parts of org-mode