So, I realized that I updated the task structure but forgot to update the necessary functions (such as task_new) and so forth to work with these changes.

Sure, it works, but it's not pretty at all.

1. I think it would be beneficial if the user could see the text of the task that was removed from the tasklist, also an undo option might be a cool thing to add down the road.
2. I also think it would be a great thing to add the ability to remove a task based on the given text. For instance remove task with text "Sunday run to work" in it.

-Just some ideas.

This includes listing the tasks and searching for tasks.

The fix should get rid of all the blank lines and only write lines with content.

Valgrind is showing memory leaks in task_dump and other functions. The testing code is crashing due to a malloc memory corruption in task_dump (after a 4th call to the function).

Some fancy regular expressions could do the job.

The query option is detected but a valid keyword is given (one that is found in the todo.txt) and still "No matches." is given.

I'll see what I can do to track down the issue

I think it would be to your advantage to adding a configuration file. I can work on the parser for it. Send a list of configurations needed. Some that come to mind are: TODO_LIST_PATH

It's simple; the keyword "move" and then an index would move the task over to the given file.

Example invocation
todoc move 1 other.txt

How about
todoc undo 3
to undo the third task?

So i went to incorporate the efficient list into your program last night, and I found a messy structure. I think now that some ideas are becoming more clear about what we want to do, we should devote a branch to sudo code for structure. I'm in the process of documenting your code, and cleaning some things up. will push soon.

In order to make sure the remove function works, we need a unit test.

Should be pretty easy.

I get these errors while compiling:

tests/task_test.c: In function ‘parse_test’:
tests/task_test.c:48:5: warning: passing argument 1 of ‘seatest_assert_string_equal’ discards ‘const’ qualifier from pointer target type [enabled by default]
In file included from tests/task_test.c:1:0:
tests/seatest.h:26:6: note: expected ‘char *’ but argument is of type ‘const char *’
tests/tasklist_test.c: In function ‘tlist_get_test’:
tests/tasklist_test.c:50:5: warning: passing argument 1 of ‘seatest_assert_string_equal’ discards ‘const’ qualifier from pointer target type [enabled by default]
In file included from tests/tasklist_test.c:3:0:
tests/seatest.h:26:6: note: expected ‘char *’ but argument is of type ‘const char *’
tests/tasklist_test.c: In function ‘tlist_remove_test’:
tests/tasklist_test.c:71:5: warning: passing argument 1 of ‘seatest_assert_string_equal’ discards ‘const’ qualifier from pointer target type [enabled by default]
In file included from tests/tasklist_test.c:3:0:
tests/seatest.h:26:6: note: expected ‘char *’ but argument is of type ‘const char *’
tests/tasklist_test.c:72:5: warning: passing argument 1 of ‘task_dump’ from incompatible pointer type [enabled by default]
In file included from tests/tasklist_test.c:1:0:
./include/task.h:31:13: note: expected ‘struct task_t *’ but argument is of type ‘struct tasklist_t *’
tests/tasklist_test.c:72:5: warning: passing argument 2 of ‘seatest_assert_string_equal’ discards ‘const’ qualifier from pointer target type [enabled by default]
In file included from tests/tasklist_test.c:3:0:
tests/seatest.h:26:6: note: expected ‘char *’ but argument is of type ‘const char *’

Output of gcc -v

Using built-in specs.
COLLECT_GCC=/bin/gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.7.2/lto-wrapper
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --disable-build-with-cxx --disable-build-poststage1-with-cxx --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --with-linker-hash-style=gnu --enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto --enable-plugin --enable-initfini-array --enable-java-awt=gtk --disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-ppl --with-cloog --with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux
Thread model: posix
gcc version 4.7.2 20120921 (Red Hat 4.7.2-2) (GCC)

Command Given: todoc -l #rainbows
Output: Segmentation Fault (core dumped)

Todo.txt:

(null)
blue skys arnd rainbows!
(null)
blue skys and rainbows
blue skys and rainbows!

It would be nice if you could remove tasks in a range of values. Perhaps like
todoc -r 1-3
The above would remove tasks 1 through 3.

Right now I am working on moving the task-specific and list specific to their own separate "objects". This will allow:

• Easier bug squashing because of better location of functions.
• Faster feature implementation since each object will have lots of very simple functions, with more advanced functions building on top of them.

For instance, every search will return a completely new TaskList struct, which can be written to a new file, sorted, merged with another TaskList, etc.

It'll be a simple rename.

After working with regex for a while I think I'll attempt to rewrite the parser using regexs. Should be easy

Example invocation:
todoc -r -s "delectables"