taskpaper files-“TP Due Date”, “TP Mark due and available”, and “TP Focus on Tag…”. These workflows enable Editorial to read/write and work with. I’ve been using several contributed TaskPaper workflows with Editorial for quite a while. Editorial has deserved a powerful desktop companion for a couple of years, and FoldingText is perhaps the nearest thing to a directly comparable app. I’m kicking myself for not finding these things out earlier! Now I have a nice, folding text editor combination on multiple platforms that’s aesthetically pleasing (sorry, but I simply can’t get on with these horrible text editors preferred by programmers with their DOS-era looks, ghastly colours and numbered lines - there, I’ve said it!), that supports focusing and tagging, and can sync very rapidly over Dropbox.
1Writer on iOS, Outlinely on MacOS), but they do implement it. They don’t implement it quite as well as other apps (e.g. And both of them understand GitHub task list syntax, which is extremely useful. Above all, both of them allow you to fold sections of text under headers, which is such a useful feature. It is, in short, a great way to keep Workflowy-style lists for task management.īut there’s still no sign of an Outlinely for iOS, and Robin still hasn’t unveiled his plans for OutlineEdit for iOS, so I started casting around in some frustration for another solution.Īnd found it in a slightly unexpected quarter: FoldingText, from the somewhat eccentric developer of TaskPaper, combined with the extremely powerful Editorial on iOS.īoth of them can access Dropbox, and both of them understand the same hybrid syntax (not entirely consistently, but that’s okay – highlights and comments work, for example). I like the desktop version of Outlinely very much it’s very quick to use, quite flexible, and it’s easy to move items from one part of the outline to another. I mostly write fiction so that's less often important to me.I’ve been pining for an iOS version of Outlinely for a while now. The § is a leftover from misunderstanding how Christian and Sascha were using it the important thing is that it's a string that will never appear in the actual text of my writing.Ĭitations, if there are any, are in markdown format.
#Foldingtext vs taskpaper archive#
I have a search for that in The Archive for when I want to see what things I haven't worked on recently enough. "§§" is a tag that means "working active document or draft". "#foo" tags are for ones that I want to be clickable/searchable using The Archive and 1Writer on ios (which recognizes #tags but not "bar" tags (without the #) are for one-off keywords that aren't in the text but that I don't want crowding my list of tags in 1Writer.
#Foldingtext vs taskpaper software#
I think I had one piece of software that wanted them but no others have minded them so I just left them as a standard.
The three dashes are for some YAML parsers of metadata. I think in dates like so the uid also works for me as a creation date. The header I just created by typing yy because I have that set up in keyboard maestro I also don't use internal note links, as I would rather go for strict atomicity (granularity enhances connectivity, etc).ĭocument title: 20171191231 Some things about other things That way I can focus on the writing the content immediately. I can infer all the information I need from that, so I found no need for me to add extra text to state what is a title or what is a tag. The § sign shows me it is a zettel and the title of the note is already evident within the text (I only use the § character for zettel notes). My rationale is the following, I want an extremely minimal note that is still recognisable as a zettel note. A note title that is the filename too: §201710190602 Note Title
I went for a barebones structure that goes like this. If you have followed the blog for a while you will probably have seen that Sascha and Christian's use of zettel naming+data structures has changed with time For instance, in the latest videos they seem to have dropped the § sign. Thanks for starting this important thread.
0 kommentar(er)
