mirror of
https://github.com/GothenburgBitFactory/taskwarrior.git
synced 2025-07-07 20:06:36 +02:00
fbea29e27c
- Updated the FAQ with links to the donwload page, rather than mention the versions page, which no longer has links to packages.
242 lines
8.9 KiB
HTML
242 lines
8.9 KiB
HTML
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
|
<html xmlns="http://www.w3.org/1999/xhtml">
|
|
<head>
|
|
<title>Frequently Asked Questions</title>
|
|
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
|
<link rel="stylesheet" href="task.css" type="text/css" />
|
|
</head>
|
|
|
|
<body>
|
|
<div id="container">
|
|
<table>
|
|
<tr>
|
|
<td>
|
|
<div id="toolbar">
|
|
<a href="task.html">Home</a>
|
|
<a href="setup.html">Setup</a>
|
|
<a href="30second.html">30-second Tutorial</a>
|
|
<a href="simple.html">Simple</a>
|
|
<a href="advanced.html">Advanced</a>
|
|
<a href="shell.html">Shell</a>
|
|
<a href="config.html">Configuration</a>
|
|
<a href="color.html">Colors</a>
|
|
<a href="recur.html">Recurrence</a>
|
|
<a href="date.html">Date Handling</a>
|
|
<a href="faq.html">FAQ</a>
|
|
<a href="versions.html">Old Versions</a>
|
|
<a href="links.html">Task on the Web</a>
|
|
<a href="download.html">Download</a>
|
|
</div>
|
|
|
|
<div id="content">
|
|
<br />
|
|
<br />
|
|
<br />
|
|
<h2 class="title">Frequently Asked Questions</h2>
|
|
<div class="content">
|
|
<p>
|
|
(Actually, that's a misnomer. These are really Repeatedly Asked
|
|
Questions.)
|
|
</p>
|
|
|
|
<p>
|
|
<b>
|
|
Q: When I redirect the output of task to a file, I lose all
|
|
the colors. How do I fix this?
|
|
</b>
|
|
<br />
|
|
A: Task knows (or thinks it knows) when the output is not going
|
|
directly to a terminal, and strips out all the color control
|
|
characters. Prevent this with the following entry in your
|
|
.taskrc file:
|
|
<pre><code>_forcecolor=on</code></pre>
|
|
</p>
|
|
<hr>
|
|
|
|
<p>
|
|
<b>
|
|
Q: How do I backup my task data files? Where are they?
|
|
</b>
|
|
<br />
|
|
A: Task writes all pending tasks to the file ~/.task/pending.data
|
|
and all completed and deleted tasks to ~/.task/completed.data.
|
|
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 task configuration data.
|
|
<br />
|
|
<br />
|
|
To be sure, and to future-proof your backup, consider backing
|
|
up all the files in the ~/.task directory, because upcoming
|
|
releases will make greater use of this directory.
|
|
</p>
|
|
<hr>
|
|
|
|
<p>
|
|
<b>
|
|
Q: How can I separate my work tasks from my home tasks?
|
|
Specifically, can I keep them completely separate?
|
|
</b>
|
|
<br />
|
|
A: You can do this by creating an alternate .taskrc file,
|
|
then using shell aliases. Here is are example Bash
|
|
commands to achieve this:
|
|
|
|
<pre><code>% cp ~/.taskrc ~/.taskrc_home
|
|
% (now edit .taskrc_home to change the value of data.location)
|
|
% alias wtask="task"
|
|
% alias htask="task rc:~/.taskrc_home"</code></pre>
|
|
|
|
This gives you two commands, 'wtask' and 'htask' that
|
|
operate using two different sets of task data files.
|
|
</p>
|
|
<hr>
|
|
|
|
<p>
|
|
<b>
|
|
Q: Can I revert to a previous version of task? How?
|
|
</b>
|
|
<br />
|
|
A: Yes, you can revert to a previous version of task,
|
|
simply by <a href="download.html">downloading</a> the
|
|
prior version and installing it. If you find a bug in
|
|
task, then this may be the only way to work around the bug,
|
|
until a new release is made.
|
|
</p>
|
|
<p>
|
|
Note that it is possible that the task file format will
|
|
change. For example, the format changed between versions
|
|
1.5.0 and 1.6.0. Task will automatically upgrade the file
|
|
but if you need to revert to a previous version of task,
|
|
there is the file format to consider. This is yet another
|
|
good reason to back up your task data files!
|
|
</p>
|
|
<hr>
|
|
|
|
<p>
|
|
<b>
|
|
Q: I'm using Ubuntu 9.04, and I want task to word-wrap
|
|
descriptions. How do I do this?
|
|
</b>
|
|
<br />
|
|
A: You need to install ncurses, by doing this:
|
|
<code><pre>% sudo apt-get install libncurses5-dev</pre></code>
|
|
Then you need to rebuild task from scratch, starting with
|
|
<code><pre>% cd task-X.X.X
|
|
% ./configure
|
|
...</pre></code>
|
|
The result should be a task program that knows the width
|
|
of the terminal window, and wraps accordingly.
|
|
</p>
|
|
<hr>
|
|
|
|
<p>
|
|
<b>
|
|
Q: How do I build task under Cygwin?
|
|
</b>
|
|
<br />
|
|
A: Task is built the same way everywhere. But under Cygwin, you'll
|
|
need to make sure you have the following packages available
|
|
first:
|
|
|
|
<ul>
|
|
<li>gcc
|
|
<li>make
|
|
<li>libncurses-devel
|
|
<li>libncurses8
|
|
</ul>
|
|
|
|
The gcc and make packages allow you to compile the code, and
|
|
are therefore required, but the ncurses packages are optional.
|
|
Ncurses will allow task to determine the width of the window, and
|
|
therefore use the whole width and wrap text accordingly, for a
|
|
more aesthetically pleasing display.
|
|
</p>
|
|
<hr>
|
|
|
|
<p>
|
|
<b>
|
|
Q: Do colors work under Cygwin?
|
|
</b>
|
|
<br />
|
|
A: They do, but only in a limited way. You can use regular
|
|
foreground colors (black, red, green ...) and you can
|
|
regular background colors (on_black, on_red, on_green ...),
|
|
but underline and bold are not supported.
|
|
<br />
|
|
<br />
|
|
If you run the command:
|
|
<code><pre>% task colors</pre></code>
|
|
Task will display all the colors it can use, and you will
|
|
see which ones you can use.
|
|
<br />
|
|
<br />
|
|
See the <a href="color.html">color</a> documentation for
|
|
more details on which colors can be used.
|
|
</p>
|
|
<hr>
|
|
|
|
<!--
|
|
<p>
|
|
<b>
|
|
Q:
|
|
</b>
|
|
<br />
|
|
A:
|
|
</p>
|
|
<hr>
|
|
-->
|
|
</div>
|
|
|
|
<br />
|
|
<br />
|
|
<div class="content">
|
|
<p>
|
|
Copyright 2006-2009, P. Beckingham. All rights reserved.
|
|
</p>
|
|
</div>
|
|
|
|
</div>
|
|
</td>
|
|
|
|
<td align="right" valign="top" width="200px">
|
|
<br />
|
|
<br />
|
|
<br />
|
|
<br />
|
|
<br />
|
|
<br />
|
|
<br />
|
|
<br />
|
|
<br />
|
|
<br />
|
|
|
|
<script type="text/javascript"><!--
|
|
google_ad_client = "pub-9709799404235424";
|
|
/* Task Main */
|
|
google_ad_slot = "8660617875";
|
|
google_ad_width = 120;
|
|
google_ad_height = 600;
|
|
//-->
|
|
</script>
|
|
<script type="text/javascript"
|
|
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
|
|
</script>
|
|
</td>
|
|
</tr>
|
|
</table>
|
|
|
|
</div>
|
|
|
|
<script type="text/javascript">
|
|
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
|
|
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
|
|
</script>
|
|
<script type="text/javascript">
|
|
var pageTracker = _gat._getTracker("UA-4737637-1");
|
|
pageTracker._initData();
|
|
pageTracker._trackPageview();
|
|
</script>
|
|
|
|
</body>
|
|
</html>
|
|
|