A collection of utilities to work with files in (todo.txt format)[http://todotxt.org/]
load(filename: &Path) -> Result<TaskVec, terr::TodoError>
Loads a list of todos from a given file path. Returns the list of loaded todos or an error. If the file does not exist the function returns empty list.
save(tasks: &TaskSlice, filename: &Path) -> Result<(), terr::TodoError>
Saves the todo list to a given file path. It may return an error if creating file or writing to it fails. The list is saved in two steps:
filename
filename
archive(tasks: &TaskSlice, filename: &Path) -> Result<(), terr::TodoError>
It works similar to save
but appends task list to a given filename
. It does not create a temporary file.
filter(tasks: &todo::TaskSlice, c: &Conf) -> todo::IDVec
The function gets the list of all todos and filtering rules and returns the list of todo IDs(todo's ID is the order number of the todo in the original list) that matches the rules. If a rule works with strings(e.g, projects or regex), the rule is caseinsensitive. Available rules (if a rule is None the rule is skipped):
range
- selects one todo by its ID, or a few ones by ID range(inclusive);all
- selects only all done, only incomplete, or both;pri
- selects with any priority, without any priority, or with the same/higher/lower priority(inclusive);regex
- when use_regex
is true, it does regular expression pattern matching, otherwise it search for a substring. Note: it searches for the regex
in subject, projects, and contexts;projects
- selects all todos that have any of projects
. This rule allows a caller to do very basic pattern matching: *
added to the begining or to the end of a project means to look for a project which name ends or starts respectively with the word, Adding *
to both ends works like regex
but checks only projects. *
in the middle of the word does not have any special meaning - use regex
in this case;contexts
- selects all todos that have any of contexts
. The rule can use *
in the same way projects
does;due
- selects all todos with any due date, without due date, a todo with due date within range, or todos which are less than the number of days ahead;rec
- selects all recurrent todos or all without recurrent flag.sort(ids: &mut todo::IDVec, todos: &todo::TaskSlice, c: &Conf)
Because sort
is the function that should be called after filter
, it wants a list of selected todo IDs that must be sorted, the whole todo list (IDs in ids
are the order numbers of a todo in todos
) and sorting rules. The function changes ids
in-place and the sorting is always stable - it keeps the order of todos in the ids
list for todos that are equal to each other. There are only two sorting rules:
fields
- is a comma(or colon) separated list of fields in order of importance for soring. If the vector is empty the list remains unchanged. Supported field names(and their abbreviations):
pri
or prioroty
- sort by priority (without priority are the last ones);due
- sor by due date (todos that do not have due date are at the bottom);completed
or finished
- sort by completion date (incomplete ones are at the bottom);created
or create
- sort by creation date;subject
, subj
or text
- sort by todo's subjects;done
- order: incomplete, recurrent, and done todos;project
or proj
- sort by project names, if todos have more than one project they are compared in order of appearance and shorter list of projects goes first;context
or ctx
- sort by contexts, if todos have more than one context they are compared in order of appearance and shorter list of contexts goes first;rev
- when it is true
the sorted list is reversed before returning the result.add(tasks: &mut TaskVec, c: &Conf) -> usize
The function gets a list of existing todos and a c
with non-None field subject
, then it parses subject
and adds the result todo to the list and return the ID of the new todo. If adding fails - e.g, subject
is empty or parsing returns an error - the function returns INVALID_ID
.
Functions of this category gets a list of all todos, list of todo IDs that should be modified and optionally new values for properties. If list of IDs ids
is None then the function modifies all todos. It returns the vector of boolean values with the length equal to the length of ids
(or length of tasks
if ids
is None). If the result vector has true
at some index it means that the todo from ids
at the same index was modified.
done(tasks: &mut TaskVec, ids: Option<&IDVec>) -> ChangedVec
Makes all todos from ids
list that are incomplete completed.
Special case: recurrent todos. They are not marked completed, their due date moves to the next date. If you need to mark recurrent todo completed you have to remove recurrence from the todo beforehand.
undone(tasks: &mut TaskVec, ids: Option<&IDVec>) -> ChangedVec
Removes completion mark from all todos from ids
list that are done.
Special case: recurrent todos. They are not changed.
edit(tasks: &mut TaskVec, ids: Option<&IDVec>, c: &Conf) -> ChangedVec
The function modifies all todos in tasks
which IDs are in ids
list. Note: modifying a subject changes only the first todo in ids
list because it does not make sense to make all todos the same.
What can be modified:
subject
- set a new onepriority
- set, remove, increase or decrease prioritydue date
- set or removerecurrence
- set or removeprojects
- add, remove or replacecontexts
- add, remove or replace