2 ms·
I did pretty much the same thing for years, using Emacs org mode (same hyperlinked setup). Then I used vim using `CTRL-Wgf`, same as you. Then I added to my .
by lelanthran 3y ago
I did pretty much the same thing for years, using Emacs org mode (same hyperlinked setup).
Then I used vim using `CTRL-Wgf`, same as you.
Then I added to my .bash_profile:
alias todo='vim ~/.todo'
Then I test drove a bunch of todo apps (yeah, Obsidian too).
The problem I found with this, eventually, is that it's really not great at allowing me to perform my most common workflow:
push-context -> start-new-thing -> finish-new-thing -> pop-context
Or
switch-context $OLD-THING -> switch-context $NEW-THING -> switch-previous-context
Or even
switch-previous-context -> switch-previous-context (repeat ad nauseum)
Or
switch-to-most-recent-context-in-admin -> switch-to-most-recent-context-in-other-project
etc.
Really, my tasks are not lists, they aren't even items to do. They're contexts which I want to switch to, switch between, discard once done (to maintain high SNR), branch off from, etc.
It's context management. A todolist app isn't going to cut it, and in fact, none of them did.
For the last 6 months or so I've been happily using a small tool I developed for myself, to suit my workflows (like the ones above). Even made a GUI for it.
It's the only thing I've used since I started with TODO files in the 90s that gets better at managing my contexts over time. Everything else gets worse over time, because the mismatch between what I want (context management) and what they provide (TODO items management) can easily be negligible when first using it with few items entered, but as that list grows so does the magnitude of the mismatch in what I want and what they do.
It's missing remote sync but I'll eventually add that in (so I can use it from the phone eventually). Easily the best 1 week I've ever spent on a project.
- seletskiy 3y agoHey, I've realized the same thing (that my workflows are stack-based) awhile ago, but didn't get to the point of writing a tool yet. Dare to share? Also, which approach you use to efficiently store and re-store relevant context information? I often find that intricate but important details are lost during context switch.
- lelanthran 3y ago> Hey, I've realized the same thing (that my workflows are stack-based) awhile ago, but didn't get to the point of writing a tool yet. Dare to share? Sure, but because I'm only using it for myself, you're going to have to compile it yourself if you want (for now, anyway). Originally designed to be CLI app, I find I only use the GUI these days (also in the repo). Start here in case this is not for you: https://github.com/lelanthran/frame/blob/master/docs/FrameIntroduction.odp https://github.com/lelanthran/frame/blob/master/docs/FrameIn... > Also, which approach you use to efficiently store and re-store relevant context information? I often find that intricate but important details are lost during context switch. Everything is stored in a hierarchical DB, AKA the filesystem :-) Each 'frame' is a directory with a specific set of files, and the directory name serves as the name of the frame. At any given time, a metainfo file in the root points to the currently active frame.