mirror of
https://github.com/GothenburgBitFactory/taskwarrior.git
synced 2025-08-28 13:37:20 +02:00
Documentation Update - clarification
- Added note about the lack of a need to escape shell metacharacters when they are used in a custom report filter (thanks to Bruce Dillahunty). - Corrected wrong header tag.
This commit is contained in:
parent
b194f37f11
commit
cce755e5da
2 changed files with 8 additions and 5 deletions
|
@ -69,10 +69,13 @@
|
|||
<pre><code>% task add "Buy bread & milk"</code></pre>
|
||||
|
||||
<p>
|
||||
Task itself interprets the commands, and it too can make mistakes.
|
||||
For example, any colon : character will be interpreted by task as a
|
||||
delimiter between an attribute name and its value. Currently there
|
||||
is no workaround for this.
|
||||
Note that if an & character (or any other character that needs
|
||||
to be escaped for the shell) appears in the
|
||||
<a href="filter.html">filter</a> of a
|
||||
<a href="custom.html">custom report</a>
|
||||
then it does not need to be escaped, as it never gets processed
|
||||
by the shell. In other words, shell escapes need only be used
|
||||
when typing task commands at a prompt.
|
||||
</p>
|
||||
</div>
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue