<?xml version="1.0"?>
<!DOCTYPE tudu SYSTEM "/usr/local/share/tudu/tudu.dtd">
<todo>
	<todo done="no" collapse="no">
		<title>more complex cathegories</title>
		<text>Multi category support and not limitation on name length.

So categories become more like tags.
</text>
	</todo>
	<todo done="no" collapse="no">
		<title>command line interface for sort order or show info while press b</title>
		<text>
</text>
	</todo>
	<todo done="no" collapse="no">
		<title>one task two places</title>
		<text>
</text>
	</todo>
	<todo done="no" collapse="no">
		<title>cli interface</title>
		<text>
</text>
	</todo>
	<todo done="no" collapse="no">
		<title>cooerent editor and title</title>
		<text>
</text>
	</todo>
	<todo done="no" collapse="no">
		<title>import and export</title>
		<text>
</text>
	</todo>
	<todo done="no" collapse="no">
		<title>more filters (by project, keyword, date)</title>
		<text>
</text>
	</todo>
	<todo done="no" collapse="no">
		<title>more states for a task (undone, done, waiting, maybe, ...)</title>
		<text>
</text>
	</todo>
	<todo done="no" collapse="no">
		<title>configure the tudu.xml to load</title>
		<text>On 10:56, Thu 25 Mar 10, Ioan Calin Borcoman wrote:
&gt; One more thing - would it be hard for tudu to do something like git?
&gt; That is, if there is a .tudu xml file in the current dir or one of the
&gt; parent dirs, load it by default? This way, I could keep my todo for my
&gt; app with the code, on my repository. It's not a big deal, as tudu -f
&gt; tudu.xml is not that complicated, but I think it could be nice.

Maybe with an env variable like TUDU_XML, if is not set tudu read your
$HOME/.tudu.xml if is set tudu reads the file on it. So you can set in
your .profile:
export TUDU_XML=.tudu.xml

But in this case I'm not sure what to do if the $TUDU_XML file don't exist.
Should I create it? I think the answer is yes, but in your case could not be
what you wanted.

I'll think about it. Could be a nice feature.
</text>
	</todo>
</todo>