1. 27 Feb, 2017 3 commits
  2. 24 Feb, 2017 3 commits
  3. 22 Feb, 2017 3 commits
    • Bram Schoenmakers's avatar
    • Bram Schoenmakers's avatar
      Fix generic help and usage of invalid subcommands in aliases · 6faf0ded
      Bram Schoenmakers authored
      Plain 'help' would crash the column UI, as would the usage of an invalid
      command in an alias.
      
      This case should be handled properly, as the CLI and Prompt mode do.
      
      For this purpose, the generic help text was extracted, such that it can
      be printed in column mode (and also in prompt mode, while I was at it).
      6faf0ded
    • Bram Schoenmakers's avatar
      Apply LimitFilter after HiddenTagFilter · d0342c58
      Bram Schoenmakers authored
      The LimitFilter should be performed at the very last step. Instead of
      complicating ExpressionCommand and ListCommand to cough up a well
      ordered set of filters, order the filters when updating the view. Each
      filter is assigned an order number, where filters with a higher order
      are applied later.
      
      This fixes the output when using the ls -n flag, where the truncation
      appears before the hide tag filter. This results in possibly less items
      to be printed than specified (or worse: nothing is printed).
      d0342c58
  4. 21 Feb, 2017 2 commits
  5. 20 Feb, 2017 3 commits
  6. 15 Feb, 2017 1 commit
  7. 10 Feb, 2017 3 commits
  8. 09 Feb, 2017 6 commits
  9. 08 Feb, 2017 1 commit
    • Bram Schoenmakers's avatar
      Make text editor more configurable · ebb3b4c2
      Bram Schoenmakers authored
      Lookup mechanism:
      
      1. Check whether an editor was given with the -E flag:
      
           topydo edit -E vim
      
      2. Use the value of $TOPYDO_EDITOR
      3. Use the value in the configuration file:
      
         [edit]
         editor = vim
      
      4. Use the value in $EDITOR
      5. Use 'vi' if the above fails.
      
      This makes it easier to invoke an editor as vim with additional
      parameters, for instance by adding the full todo.txt file to the
      completion options (see the tip in issue #164). This trick was added to
      the configuration file as a comment.
      ebb3b4c2
  10. 07 Feb, 2017 1 commit
  11. 06 Feb, 2017 2 commits
  12. 27 Jan, 2017 1 commit
    • Bram Schoenmakers's avatar
      Do not apply ordinal filtering when a tag appears more than once · 5e13411a
      Bram Schoenmakers authored
      Suppose we have the todo item:
      
          (C) Some item key:value1 key:value2
      
      And then I do an ls:
      
          topydo ls -x key:value2
      
      Before, this would yield an empty result, which is undesired. Therefore,
      only apply ordinal tag filtering when a tag appears exactly once in the
      todo item. This is a simple approach, and special operators >, >= etc
      will not be applicable:
      
          topydo ls -x key:>value1
      
      will no longer work. The result could be ambiguous: filter out when none of
      the tags match, or only some of them?
      5e13411a
  13. 24 Jan, 2017 1 commit
  14. 20 Jan, 2017 1 commit
  15. 19 Jan, 2017 2 commits
  16. 18 Jan, 2017 1 commit
  17. 15 Jan, 2017 2 commits
  18. 12 Jan, 2017 1 commit
  19. 11 Jan, 2017 2 commits
  20. 10 Jan, 2017 1 commit