When I’m ready to actually go camping, I can make a new copy of the basic taskpaper config: $ cp car_camping.taskpaper 2016_06_beverly_beach_camping.taskpaper But I discovered another use case that’s very handy: frequently used checklists!įor example, I have a car_camping.taskpaper file for camping trips, which looks like so: Pantry: These tools together have provided me pretty much everything I need for day to day GTD/To Do. The UI for working with taskpaper files is great, very easy to drag things around to reorganize them, fold projects to focus on specific ones, and most importantly, check things off as they’re completed. As long as I’m online, it’s got the latest versions of all my files. If you work in Markdown at all, give it a look.īecause it supports Dropbox, the synchronization is easy. It’s incredibly useful to be able to simply extend it with Python, when needed, and even without that capability it’s wonderful out of the box. I can’t say enough about the Editorial app. Because I’m the only one actually editing this file, the risk of a race condition here is nearly nil. Translating to English – if the filetype is one that’s used by the taskpaper extension, then auto-save the files on edit, and do a force-reload if file changes are detected on the filesystem. (Using Vundle syntax here to show the plugins needed.) " Autosave taskpaper filesĪutocmd filetype taskpaper let g:auto_save = 1Īutocmd filetype taskpaper :WatchForChanges! Similarly, if I make a mobile edit, and don’t reopen the file in vim, I’ll lose those changes. However, that’s not ideal for the ‘ubiquitous capture.’ If I have the file open, and I haven’t saved all my edits, I may clobber them if editing on mobile. I generally have a vim running with my todo.taskpaper file open at all times.
0 Comments
Leave a Reply. |