![]() Partially because I'm always looking for the one that's better than what I use now - looking for the thing that fits me the best - but also because I just like trying things. To add some counterpoint to this, I try a lot of apps. There is not a huge need for portability between to do apps. > A formal spec also doesn't help much for apps to use this format. So, all told, it is a beautiful effort, nicely presented, but I think it is unnecessary. Beyond that, different to do apps use different systems of categorization and tagging, so really in practice I doubt this will become any kind of standardized format. Even if an app adopted this, being tied to a plain text format would likely hinder feature development, including the ability to sync across multiple devices. There is not a huge need for portability between to do apps, and for most users to do items are ephemeral and not something that needs to be archived and revisited. Time spent conforming to a spec is time wasted.Ī formal spec also doesn't help much for apps to use this format. In the vast majority of cases no one is going to see them but you. You don't need a standardized format if you are writing to do items manually in a text editor. On the other hand, I do not think this is necessary or even all that helpful in the real world. I like the thought that went into it and the nice presentation. ![]() I love the recognition that dates may be imprecise (e.g., 2022-05 - although I would count that as the last day of the period, 23:59:59 on, rather than the first day of the next period, ). #TASKPAPER INSERT SEPARAT CODE#** Instructions for running BrainTool locally:Ģ) Make a folder where you want to put the code ** DONE get rid of link in welcome topic, too confusing :dev:099: ** DONE bug narrow edit card shows item under bullet which is confusing. It would for sure be nice to have a definitive spec to point to, independent of the emacs ecosystem.īTW see below the first few lines of my file for yesterday. Maybe it's a familiarity thing, anything specific you dislike?Īnyway here's the definitive argument for org as markup of choice: Obviously I'm biased since I built BrainTool because of my emacs/org use, but I also use markdowns and maintain the blog on github in their markdown. #TASKPAPER INSERT SEPARAT FREE#There is obviously not much tooling support (yet), but feel free to create something if the idea resonates with you. This is what it! is about, which is a plain-text file format for todos and check lists. This puts the data first, and it allows the tools to be built on top and shared (or interchanged) more easily. I think the best basis for staying independent is to have a data format that’s properly specified and meaningful on its own. I personally use Sublime Text, and even though I enjoy it a lot, I don’t like being bound to specific tools. So, kind-of similar to Emacs Org Mode, but without having to use Emacs. ![]() Rather than having to memorise CLI commands for these interactions (which I’m not super good at), I figured that it’s easier for me to use my text editor directly, and have an editor plugin help me with the visual structure and some convenience functionality. Most of the time, my use cases are quite simple, like viewing my todo items, checking them off, or adding a new one. NvUltra will never be a replacement for TaskPaper, but with its flexibility nvUltra can certainly integrate well with TaskPaper.After having cycled through various CLI-based todo apps, I started to realise that I actually don’t need a tool at all for managing my todos. `.search` inserts my collection of saved searches for use in TaskPaper (I have searches to show items due today, overdue items, items due in the next 2 days, and to show me only "next actions" in the GTD sense (the first available undone action for each project in the file).). ![]() For example, `.d` inserts the tag, and inserts the current date. ![]() I do like having blank lines between top-level projects, so I insert them there, but those don't cause any problems.Īs an aside - I am packaging up some of the saved TaskPaper searches I have created over the years into an expansion file for nvUltra/Composer. default contents of a new document) - don't use an empty line between a project and it's child tasks. The solution I prefer is the one used by TaskPaper itself in it's built-in document s(e.g. Depending on which TaskPaper features you use, that may or may not be problematic for you. If you remove the leading tabs, then my understanding is that those items are no longer tasks within the the project, but rather tasks that are siblings of the project. Yes - if you insert an empty line between the project name and the tasks "inside" that project, it will be treated as a code block due to the indentation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |