Zef Hemel
c93d656ac6
* Moved YAML library import to index plug (so no async syscalls anymore) should speed things up * Merged task and item indexing * Merged tasks plug into index (questionable) * taskstate is now no longer a tag, but needs to be configured via configs
30 lines
1003 B
Markdown
30 lines
1003 B
Markdown
The task notation syntax is a [[Markdown]] extension to write down tasks.
|
|
|
|
Its most basic form is:
|
|
|
|
* [ ] This is my first task
|
|
|
|
which renders as follows:
|
|
|
|
* [ ] This is my first task
|
|
|
|
# Custom states
|
|
Tasks support the default `x` and ` ` states (done and not done), but custom states as well. Support for this is still very basic, however.
|
|
|
|
Example:
|
|
|
|
* [NOT STARTED] Task 1
|
|
Fix having global variables work in markdown.expandMarkdown
|
|
* [IN PROGRESS] Task 2
|
|
|
|
Restrictions:
|
|
|
|
* Task states cannot contain `:` to avoid ambiguity with [[Attribute]] syntax.
|
|
|
|
It is advisable to explicitly define custom task state using the [[Library/Std/APIs/Task State#taskState.define(def)]] API, this will enable cycling through the task states by clicking on them.
|
|
|
|
# Querying
|
|
SilverBullet allows you to simply toggle the complete state of a task by clicking the checkbox. It also allows for querying tasks as [[Object#task]]. For instance:
|
|
|
|
${query[[from index.tag "task" where page == editor.getCurrentPage()]]}
|