GothenburgBitFactory/taskwarrior
1
0
Fork 0
mirror of https://github.com/GothenburgBitFactory/taskwarrior.git synced 2025-06-26 10:54:26 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Sample .taskrc - update

Browse source 
- Added default config variables for new reports.
- Removed README.1.5.0.
- Removed messages configure.ac
This commit is contained in:
Paul Beckingham 2009-02-16 21:35:26 -05:00
parent bcf512e529
commit 72efddc066
6 changed files with 12 additions and 37 deletions
Download patch file Download diff file Expand all files Collapse all files

1
ChangeLog
View file

@ -18,6 +18,7 @@
sort order, with optional filtering in the configuration file. This
means user-defined reports can be written, and the reports currently
in the configuration file can be renamed.
+ New algorithm for determining when the "nag" message is displayed.
------ old releases ------------------------------

2
Makefile.am
View file

@ -1,3 +1,3 @@
SUBDIRS = src
EXTRA_DIST = DEVELOPERS README.1.5.0
EXTRA_DIST = DEVELOPERS

15
README.1.5.0
View file

@ -1,15 +0,0 @@
Task 1.5.0 has a custom reports feature. Three of the existing task reports
are no longer implemented in task, and need to be added as custom reports.
Simply copy the following six lines into your existing .taskrc file.
New task users need not do this - task will create an initial .taskrc file
on first startup.
report.long.columns=id,project,priority,entry,start,due,age,tags,description
report.long.sort=due+,priority-,project+
report.list.columns=id,project,priority,due,active,age,description
report.list.sort=due+,priority-,project+
report.ls.columns=id,project,priority,description
report.ls.sort=priority-,project+

6
configure.ac
View file

@ -74,9 +74,3 @@ AC_CHECK_FUNC(srandom, [AC_DEFINE([HAVE_SRANDOM], [1], [Found srandom])])
AC_CONFIG_FILES([Makefile src/Makefile])
AC_OUTPUT
AC_MSG_NOTICE([...])
AC_MSG_NOTICE([...])
AC_MSG_NOTICE([Existing task users please read the README.1.5.0 file!])
AC_MSG_NOTICE([...])
AC_MSG_NOTICE([...])

16
html/task.html
View file

@ -112,23 +112,9 @@
sort order, with optional filtering in the configuration file. This
means user-defined reports can be written, and the reports currently
in the configuration file can be renamed.
<li>New algorithm for determining when the "nag" message is displayed.
</ul>
<p>
Note that users of task prior to version 1.5.0 will need to add
the following six lines to their .taskrc file. See also the
README.1.5.0 file in the distribution for more details.
</p>
<pre><code>report.long.columns=id,project,priority,entry,start,due,age,tags,description
report.long.sort=due+,priority-,project+
report.list.columns=id,project,priority,due,active,age,description
report.list.sort=due+,priority-,project+
report.ls.columns=id,project,priority,description
report.ls.sort=priority-,project+</code></pre>
<p>
(Find out <a href="versions.html">what was new in prior versions</a>)
</p>

9
src/Config.cpp
View file

@ -38,6 +38,15 @@
////////////////////////////////////////////////////////////////////////////////
Config::Config ()
{
// These are default (but overridable) reports.
(*this)["report.large.columns"] = "id,uuid,project,priority,entry,start,due,age,active,tags,description";
(*this)["report.large.sort"] = "due+,priority-,project+";
(*this)["report.long.columns"] = "id,project,priority,entry,start,due,age,tags,description";
(*this)["report.long.sort"] = "due+,priority-,project+";
(*this)["report.list.columns"] = "id,project,priority,due,active,age,description";
(*this)["report.list.sort"] = "due+,priority-,project+";
(*this)["report.ls.columns"] = "id,project,priority,description";
(*this)["report.ls.sort"] = "priority-,project+";
}
////////////////////////////////////////////////////////////////////////////////