1. 15 Feb, 2017 1 commit
  2. 10 Feb, 2017 3 commits
  3. 09 Feb, 2017 6 commits
  4. 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
  5. 07 Feb, 2017 1 commit
  6. 06 Feb, 2017 2 commits
  7. 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
  8. 24 Jan, 2017 1 commit
  9. 20 Jan, 2017 1 commit
  10. 19 Jan, 2017 2 commits
  11. 18 Jan, 2017 1 commit
  12. 15 Jan, 2017 2 commits
  13. 12 Jan, 2017 1 commit
  14. 11 Jan, 2017 2 commits
  15. 10 Jan, 2017 2 commits
  16. 06 Jan, 2017 1 commit
    • Bram Schoenmakers's avatar
      Do not hide console output when pressing : after a command · 8737faa1
      Bram Schoenmakers authored
      Normally, pressing ':' after executing a command would hide the console
      (equivalent behavior to Escape or Enter). Now, : will focus the
      commandline while keeping the previous output visible. This makes it
      easier to compose a new command based on a todo shown in the previous
      output (for example perform an 'ls' and then a 'dep' with IDs
      afterwards).
      
      Escape and Enter still have the same behavior, which can be used to
      dismiss the last output.
      8737faa1
  17. 02 Jan, 2017 2 commits
  18. 28 Dec, 2016 2 commits
  19. 16 Dec, 2016 1 commit
  20. 15 Dec, 2016 4 commits
  21. 06 Dec, 2016 2 commits
  22. 02 Dec, 2016 1 commit