@@ -278,63 +278,4 @@ PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS -* - How to Apply These Terms to Your New Programs - - If you develop a new program, and you want it to be of the greatest -possible use to the public, the best way to achieve this is to make it -free software which everyone can redistribute and change under these terms. - - To do so, attach the following notices to the program. It is safest -to attach them to the start of each source file to most effectively -convey the exclusion of warranty; and each file should have at least -the "copyright" line and a pointer to where the full notice is found. - - <one line to give the program's name and a brief idea of what it does.> - Copyright (C) <year> <name of author> - - This program is free software; you can redistribute it and/or modify - it under the terms of the GNU General Public License as published by - the Free Software Foundation; either version 2 of the License, or - (at your option) any later version. - - This program is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - GNU General Public License for more details. - - You should have received a copy of the GNU General Public License - along with this program; if not, write to the Free Software - Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA - - -Also add information on how to contact you by electronic and paper mail. - -If the program is interactive, make it output a short notice like this -when it starts in an interactive mode: - - Gnomovision version 69, Copyright (C) year name of author - Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. - This is free software, and you are welcome to redistribute it - under certain conditions; type `show c' for details. - -The hypothetical commands `show w' and `show c' should show the appropriate -parts of the General Public License. Of course, the commands you use may -be called something other than `show w' and `show c'; they could even be -mouse-clicks or menu items--whatever suits your program. - -You should also get your employer (if you work as a programmer) or your -school, if any, to sign a "copyright disclaimer" for the program, if -necessary. Here is a sample; alter the names: - - Yoyodyne, Inc., hereby disclaims all copyright interest in the program - `Gnomovision' (which makes passes at compilers) written by James Hacker. - - <signature of Ty Coon>, 1 April 1989 - Ty Coon, President of Vice -This General Public License does not permit incorporating your program into -proprietary programs. If your program is a subroutine library, you may -consider it more useful to permit linking proprietary applications with the -library. If this is what you want to do, use the GNU Library General -Public License instead of this License. COPYING @@ -1,11 +1,11 @@ 1.1.0 (?) - Command line specification of alternate .taskrc file + - Bug: when run without arguments, task dumps core on Solaris 10 1.0.0 (?) - New movie made, uploaded + Bug: assertion fails on mobile for t v + Bug: configure.ac does not properly determine ncurses availability - - Bug: when run without arguments, task dumps core on Solaris 10 + Bug: Cannot seem to use the percent character in a task description + Bug: New installation "task stats" reports newest task 12/31/1969 + Bug: New installation task projects displays header but no data - should short-circuit ChangeLog @@ -16,5 +16,5 @@ included. color.cpp Color support functions. rules.cpp Auto-colorization rules. -Don't forget, please send patches to task@beckingham.net +Don't forget, please send bugs, patches to task@beckingham.net DEVELOPERS @@ -9,15 +9,15 @@ Task has been built and tested on the following configurations: Known Issues: - - problems running on Solaris 10 + - intermittent problems running on Solaris 10 While Task has undergone testing, bugs are sure to remain. If you encounter a -bug, please contact me at bugs@beckingham.net. Here is what you could do, in +bug, please contact me at task@beckingham.net. Here is what you could do, in order of increasing effort (to you) and usefulness (to me): - Do nothing. Bug probably won't get fixed. - - Send an email to bugs@beckingham.net, explaining what you saw. The bug + - Send an email to task@beckingham.net, explaining what you saw. The bug will be addressed, and a new release will be made. You will be a hero. - Send an email, and a reproducible test case in the form of the few commands NEWS @@ -1,15 +1,23 @@ +# Welcome to "task". + task add do laundry task add project:garage order dumpster task add +phone tell mom i loveher task add +phone pro:garage schedule goodwill pickup -task add +email pro:garage ask Tom if he wants that old bike +task add +email pro:garage ask Tom if he wants that old bkie +task ls + +task 5 /bkie/bike/ task ls task 1 pro:home task 3 pro:home tell mom I love her task ls pro:garage + task long pro:garage + task list pro:garage + task lis +phone task li pro:garage +phone task l mom @@ -18,13 +26,15 @@ task 1 priority:H task pri:H 3 task 1 pri:M task li + task 2 pri:L task li -task do 3 + +task done 3 task li -# There may be an arbitrary number of tags. task 2 +phone +mistake + # Oops! task 2 -mistake task tags @@ -46,8 +56,11 @@ task 4 fg: task colors task 1 due:6/8/2008 +date + task li task calendar + task 1 due:6/1/2008 task li task overdue @@ -66,3 +79,5 @@ task active task summary task history +# Thanks for watching. + script.txt 1aa90518858c48025755e363d603352a4b99b25b Paul Beckingham paul@beckingham.net http://github.com/pbeckingham/task/commit/8a0b8e03286813b8655b768b4e2d09d4451a1b60 8a0b8e03286813b8655b768b4e2d09d4451a1b60

2008-05-30T18:22:22-07:00

- Updated all documents. 2600642af9e79bb592c45d4b89f2b2a33f3fc3bb Paul Beckingham paul@beckingham.net