| 5 Jan 2024 |
 champignoom | Or alternatively, can we carve out a subset of the gtd spec which can be quickly implemented | 14:23:04 |
 max397 | where can I find the code? | 14:23:05 |
| champignoom | Dunno, I learnted it from a discussion comment | 14:23:34 |
| max397 | 🤔 | 14:23:38 |
| max397 | u sure we aren't talking about the gtd pickers from neorg-telescope here? | 14:23:48 |
| max397 | also
the old gtd thing was just a neorg module
not a plugin | 14:24:00 |
| champignoom | https://github.com/nvim-neorg/neorg/discussions/1110#discussioncomment-7672709 | 14:24:23 |
| max397 | quite sure he means the gtd pickers | 14:24:48 |
| max397 | which are of no use at all anymore | 14:24:54 |
| champignoom | so it's like picking headinga followed by parentheses? | 14:25:28 |
| max397 | nope | 14:25:37 |
| max397 | they were really op | 14:25:41 |
| max397 | https://github.com/nvim-neorg/neorg-telescope#gtd-pickers | 14:25:58 |
| max397 | when those were created you couldn't even add the parentheses after headings | 14:26:14 |
| champignoom | ic | 14:28:50 |
| champignoom | But the UX is very cool tho | 14:29:01 |
| champignoom | What's the missing parts to get it revived? | 14:29:53 |
| max397 | well gtd | 14:30:15 |
| max397 | | 14:30:17 |
| champignoom | I mean | 14:30:39 |
| max397 | no chance to do that without gtd module | 14:30:41 |
| max397 | ? | 14:31:17 |
| champignoom | do we need a parser or a database or something else? | 14:32:12 |
| max397 | we need the gtd system | 14:33:03 |
| max397 | with projects, aof, a syntax to get task and stuff | 14:33:10 |
| champignoom | ic | 14:33:19 |
| champignoom | but something is better than nothing | 14:34:15 |
| max397 | yes but we can't get something | 14:34:22 |
| champignoom | Telescoping headings followed by parentheses can still be useful | 14:34:35 |
| max397 | except if you wanna write an api which gets all the tasks in a workspace
with metadata for file location and state | 14:34:54 |
