Skip to content
Commits on Jun 2, 2011
  1. Merge pull request #1 from brandonvalentine/patch-1

    committed Jun 2, 2011
    git add .
  2. @bval

    Add any new files in TODO_DIR, will make this work when you're adding…

    bval committed Jun 2, 2011
    … todo.txt to your project for the first time.
Commits on Feb 14, 2011
  1. @devonjones @ginatrapani

    Environment variables override config, flags override environment var…

    devonjones committed with ginatrapani Feb 9, 2011
    …iables
    
    * Added more flags to give action developers more control over commands
    that are leveraged inside their actions.
    * Writing a better message for the help screen
  2. @trajano @ginatrapani

    Added quotes to dirname call.

    trajano committed with ginatrapani Feb 10, 2011
    This allows the todo.sh to exist in a path with spaces.
  3. @guildencrantz @ginatrapani

    Change the default TODO_DIR so that it's the same as the todo.sh dir.

    guildencrantz committed with ginatrapani Feb 1, 2011
    This change makes todo.sh work out-of-the-box, and allows for excellent portable usage within Dropbox or on a flash drive.
  4. @guildencrantz @ginatrapani

    Todo.sh will now check for the config in the same directory as the sc…

    guildencrantz committed with ginatrapani Feb 1, 2011
    …ript--if it's not specified or found in HOME.
    
    This is really nice if todo.sh is kept in dropbox and accessed from multiple computers.
Commits on Feb 1, 2011
  1. @njwilson

    Fix erroneously removing pipe chars from input

    njwilson committed Jan 31, 2011
    cleaninput() unintentionally deletes the '|' character from input.  This
    commit fixes it and adds test for adding tasks with a bunch of symbols.
Commits on Jan 24, 2011
  1. @njwilson

    Fix substitution for hiding contexts/projects

    njwilson committed Jan 23, 2011
    When using the -+ or -@ option to hide project or context names in list
    output, the color reset sequence was being deleted if the project/context
    was at the end of the line.
    
    For example, with the following tasks:
    
        (B) with priority, ending in a +project
        task that shouldn't be highlighted
    
    Running 'todo.sh -+ list' would hide the "+project" from the first task,
    but would also remove the color reset sequence ^[[0m at the end.  The
    color from the prioritized task would continue to the next lines.
    
    This commit fixes the problem and adds a test to verify the fix.
Commits on Jan 20, 2011
  1. @ginatrapani

    Merge branch 'inkarkat/master'

    ginatrapani committed Jan 20, 2011
    * inkarkat/master:
      Cosmetics: Corrected inconsistent indentation.
      Skipping 'nonexecutable action' test on Cygwin.
      Factored out generation of custom action scripts.
      Fixed test environment for escaped test output.
      MINOR: Removed unnecessary empty & reference in sed substitution.
      Avoiding todo.sh help error when .todo.actions.d contains subdirs.
      BUG: interpretation of \033 escape sequences in task
      BUG: task listing aborted on embedded \c escape sequence
      BUG: tr: extra operand `d' error caused by missing quoting
  2. @inkarkat
  3. @inkarkat

    Skipping 'nonexecutable action' test on Cygwin.

    inkarkat committed Jan 20, 2011
    On Cygwin, clearing the executable flag may have no effect, as the Windows ACL may still grant execution rights. In this case, we skip the test instead of failing.
  4. @inkarkat

    Factored out generation of custom action scripts.

    inkarkat committed Jan 20, 2011
    - Reduced duplication via common make_action() function.
    - ENH: Adding proper shebang line to the custom action scripts.
    - Changed output of custom action to better differentiate from todo.sh output.
  5. @inkarkat

    Fixed test environment for escaped test output.

    inkarkat committed Jan 20, 2011
    - test-lib uses 'read -r' to parse the test session input literally, without interpretation of backslashes.
    - FIX: Use quoting to maintain original whitespace (tabs and multiple spaces) from the test session input (instead of condensing into a single space).
    - Using Bash instead of POSIX shell for t1340-listescapes.sh, so that the interpretation of escape sequences is not dependent on the POSIX shell being used.
    - Changed Makefile so that the shell selected by the shebang line is actually used when invoking tests, not the POSIX shell.
    - Above changes obsolete the multiple escaping of the test session data; now, the test session can actually be pasted as-is into a test script, even when it contains backslashes. (I.e. works as expected now.)
Commits on Jan 19, 2011
  1. @ginatrapani

    Added GPL license

    ginatrapani committed Jan 18, 2011
Commits on Dec 30, 2010
  1. @inkarkat
Commits on Oct 21, 2010
  1. @inkarkat

    Avoiding todo.sh help error when .todo.actions.d contains subdirs.

    inkarkat committed Oct 21, 2010
    I have placed tests for my custom todo actions in ~/.todo.actions.d/tests/; this causes a ".../.todo.actions.d/tests: is a directory" error on todo.sh help.
    Added condition for regular files to the executable check in order to exclude subdirectories.
  2. @inkarkat

    BUG: interpretation of \033 escape sequences in task

    inkarkat committed Oct 21, 2010
    The global substitution in the AWK highlighting of prioritized and done tasks also affected the task text itself, not just the inserted color definitions.
    Factored out the evaluation of the color variables and interpretation of \033 into a highlight() AWK function.
    Added test cases which check that \a, \t, \n, \x.. and \0.. escape characters in the task text are listed as-is, without interpretation.
  3. @inkarkat

    BUG: task listing aborted on embedded \c escape sequence

    inkarkat committed Oct 21, 2010
    Fixed by removing the -e option that causes the echo command to interpret escape characters. Coloring of done tasks (the only step in the _list pipeline that required this interpretation) has been moved into the AWK pipeline step which is responsible for the priority coloring, and which does the escape character interpretation internally.
    As a nice side effect, this shortening of the _list pipeline should also speed up the listing a wee bit.
Commits on Aug 9, 2010
  1. @inkarkat

    BUG: tr: extra operand `d' error caused by missing quoting

    inkarkat committed Aug 9, 2010
    Reported by Bill Goffe on the todotxt mailing list.
Commits on Jul 17, 2010
  1. @inkarkat

    Improved color map instructions.

    inkarkat committed Jul 17, 2010
    Clarified the use of ANSI escape codes.
    Added motivation why to change, e.g. when using Conky.
    Added requirement to uncomment color defaults when changing the color map, based on a support request on the mailing list.
  2. @inkarkat

    Aligned PRI_X comment with updated one in config.

    inkarkat committed Jul 17, 2010
    As an addendum to commit 9b7f85b.
Commits on Jul 16, 2010
  1. @inkarkat

    Added fallback for $TODO_DIR/${FILE}.txt.

    inkarkat committed Jul 16, 2010
    This allows to leave off the .txt file extension in commands like "todo.sh listfile done".
    Plus: Minor coding style alignment, replaced $1 argument with existing $FILE variable.
Commits on Jul 15, 2010
  1. @inkarkat

    ENH: Added highlighting of done (but not yet archived) tasks.

    inkarkat committed Jul 15, 2010
    This makes done tasks more stand out (like prioritized tasks) in the task list. Default highlighting is LIGHT_GREY, which seems to be modest and go well with the assumed dark terminal background.
    Reintroduced the OSX-compatible sed filter that was introduced by commit 8b7e2e6 and superseded by the PRI_X coloring generalization.
  2. @inkarkat

    Config file addendum to generalization of PRI_X color support.

    inkarkat committed Jul 15, 2010
    Adapts the config file comments to the generalization of PRI_X color support to all priorities (commit e7b5841).
  3. @inkarkat
  4. @inkarkat

    Aligned "no such task" error message with verbose messages.

    inkarkat committed Jul 15, 2010
    The message now also starts with "TODO:", like all other messages (except for the usage messages).
    Before: 42: No such task.
    After:  TODO: No task 42.
Commits on Jul 14, 2010
  1. @inkarkat

    Aligned verbose message output of tasks with normal task output.

    inkarkat committed Jul 14, 2010
    I.e. removed the colon after the ITEM#. Updated tasks are now listed like the 'todo.sh ls' command does, e.g.
        42 smell the roses
    This is in preparation to eventually use a function factored out from _list() for the verbose task output, which would enable coloring in the verbose message and thus align the verbose message output even more with the normal task output.
  2. @inkarkat
  3. @inkarkat

    Better verbose messages for 'replace' and 'del TERM'.

    inkarkat committed Jul 14, 2010
    Added "TODO:" prefix and simplified messages.
  4. @inkarkat

    Aligned implementations of verbose output.

    inkarkat committed Jul 14, 2010
    Replaced multi-line [ ] && { ... } with if-then.
Commits on Jul 13, 2010
  1. @inkarkat

    Merge commit 'upstream/master'

    inkarkat committed Jul 13, 2010
  2. @inkarkat

    Improved 'move' command.

    inkarkat committed Jul 13, 2010
    - Removed (accidental) printing of the task (without leading ITEM#) when checking for existence of the task; using empty check of task text as done elsewhere.
    - Simplified error handling and using die() for proper exit code.
    - Aligned verbose move message with the verbose output of other commands.
  3. @inkarkat
  4. @inkarkat

    ENH: Improved 'del ITEM# TERM' command.

    inkarkat committed Jul 13, 2010
    - Condensing whitespace around TERM into a single space and removing leading/trailing spaces if at the beginning/end of the task.
    - Proper error message if TERM not found.
    - Aligned verbose removal message with the verbose output of the 'replace' command.
    In addition, removed (accidental) printing of the task (without leading ITEM#) when checking for existence of the task; using empty check of task text as done elsewhere.
Something went wrong with that request. Please try again.