
Then I wanted to take notes with "living code". taking notes at whim of a moment, dumping all notes in a single file (you don't have to do it in a single file) categorized by tags. You write once, and then export the same to HTML, PDF, markdown, plain ASCII text, etc. I started off learning just the (1) org markup syntax, and exporting. The thing is that no one needs to "learn the whole org mode" you take it in piece by piece, based on the features you need. People complaining about "usability" of org mode do not know where to begin "learning" org mode. Org mode is a very powerful tool that is used for many more applications. when the idea hits you in the public transport), have it automatically sync over the taskserver to your desktop, and when you open the taskwiki file relevant to the project, the task is there!įor people, not familiar with org mode, the markup portion is a very very small subset of org mode. The power of this setup is that you can add a task on your phone (i.e. The next time you open the taskwiki file, it will look like this(syncing happens when you open the file): This file contains all the work-relevant information.Īfter saving that file, you will see the task in taskwarrior as well (with the tag assigned). Then your taskwiki file might look like this Say you have all your work tasks tagged with 'work'. The feature is called Viewport, and it's a header enhanced with a taskwarrior filter: On the contrary, taskwiki provides two-way sync, so they will show up in your taskwiki lists.
