and all completed and deleted tasks to
They are text files, so they can just be copied to another location for safekeeping. Don't forget there is also the ~/.taskrc file that contains your taskwarrior configuration data. To be sure, and to future-proof your backup, consider backing up all the files in the ~/.task directory.
% cp ~/.taskrc ~/.taskrc_home
% (now edit .taskrc_home to change the value of data.location)
% alias wtask="task"
% alias htask="task rc:~/.taskrc_home"
This gives you two commands, 'wtask' and 'htask' that operate using two different sets of task data files.
Note that it is possible that the taskwarrior file format will change. For example, the format changed between versions 1.5.0 and 1.6.0. Taskwarrior will automatically upgrade the file but if you need to revert to a previous version of taskwarrior, there is the file format to consider. This is yet another good reason to back up your task data files!
% sudo apt-get install libncurses5-dev
Then you need to rebuild taskwarrior from scratch, starting with
% cd task-X.X.X
The result should be a taskwarrior program that knows the width of the terminal window, and wraps accordingly.
Note that all the binary packages include this capability.
The gcc and make packages allow you to compile the code, and are therefore required, but the ncurses packages are optional. Ncurses will allow taskwarrior to determine the width of the window, and therefore use the whole width and wrap text accordingly, for a more aesthetically pleasing display.
Note that there are binary packages that all include this capability.
If you run the command:
% task colors
Taskwarrior will display all the colors it can use, and you will see which ones you can use.
Note that if you install the 'mintty' shell in Cygwin, then you can use 256 colors.
See the 'man task-color' for more details on which colors can be used.
$ task rc:new-file version
Taskwarrior will create 'new-file' if it doesn't already exist. There will not be much in it though - taskwarrior relies heavily on default values, which can be seen with this command:
$ task show
which lists all the currently known settings. If you have just created new-file, then this command lists only the defaults.
Note that this is a good way to learn about new configuration settings, particularly if your .taskrc file was created by an older version.
configuration variable. Check out DropBox at http://www.dropbox.com.
Here is a basic example of the procedure:
$ task merge ssh://user@myremotehost/.task/
$ task push ssh://user@myremotehost/.task/
The first command fetches the undo.data file from the remote system, reads the changes made and updates the local database. When this merge command completes, you should copy all the local .data files to the remote system either by using the push command explicitly or by activating the merge.autopush feature in the ~/.taskrc file. This way you ensure that both systems are fully synchronized.
$ task color
and a full color palette is displayed. If you see only 8 or 16 colors, perhaps with those colors repeated, then your terminal does not support 256 colors.
See the task-color(5) man page for more details.
See the task-color(5) man page for an in-depth explanation of the color rules.
printf "\033]0;task $*"
You just need to run the script, and let the script run task. Here is a Bash function that does the same thing:
printf "\033]0;task $*"
This will affect searching for keywords:
$ task list Document
taskwarrior will perform a caseless search in the description and any annotations for the keyword 'Document'. It also affects description and annotation substitutions:
$ task 1 /teh/the/
The pattern on the left will now be a caseless search term.
When you run a report (such as "list"), the numbers are assigned before display. For example, you can do this:
$ task list
$ task do 12
$ task add Pay the rent
$ task delete 31
Those id numbers are then good until the next report is run. This is because taskwarrior performs a garbage-collect operation on the pending tasks file when a report is run, which moves the deleted and completed tasks from the pending.data file to the completed.data file. This keeps the pending tasks file small, and therefore keeps taskwarrior fast. The completed data file is the one that grows unbounded with use, but that one isn't accessed as much, so it doesn't matter as much. So in all, the ID number resequencing is about efficiency.
$ task list priority:H priority:M
There would be no results, because the priority could not simultaneously be 'H' AND 'M'. What is required is some way to use OR instead of an AND operator. The solution is to invert the filter in this way:
$ task list priority.not:L priority.any:
This filter states that the priority must not be 'L', AND there must be a priority assigned. This filter then properly lists tasks that are 'H' or 'M', because the two logical restrictions are not mutually exclusive as in the original filter.
Some of you may be familiar with DeMorgan's laws of formal logic that relate the AND and OR operators in terms of each other via negation, which can be used to construct task filters.
$ task add Original task
$ task 1 annotate foo
$ task 1 annotate bar
$ task 1 annotate foo bar
Now to delete the first annotation, use:
$ task 1 denotate foo
This takes the fragment 'foo' and compares it to each of the annotations. In this example, it will remove the first annotation, not the third, because it is an exact match. If there are no exact matches, it will remove the first non-exact match:
$ task 1 denotate ar
This will remove the second annotation - the first non-exact match.
- Provide feedback on what works, what does not
- Tell us how task does or does not fit your workflow
- Tell people about task
- Report bugs when you see them
- Contribute to our Wiki
- Suggest features
- Write unit tests
- Fix bugs
This man page was originally written by P. Beckingham.
Taskwarrior is distributed under the GNU General Public License. See http://www.gnu.org/licenses/gpl-2.0.txt for more information.
For more information regarding task, the following may be referenced: