1. 06 Feb, 2017 2 commits
  2. 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
  3. 24 Jan, 2017 1 commit
  4. 20 Jan, 2017 1 commit
  5. 19 Jan, 2017 2 commits
  6. 18 Jan, 2017 1 commit
  7. 15 Jan, 2017 2 commits
  8. 12 Jan, 2017 1 commit
  9. 11 Jan, 2017 2 commits
  10. 10 Jan, 2017 2 commits
  11. 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
  12. 02 Jan, 2017 2 commits
  13. 28 Dec, 2016 2 commits
  14. 16 Dec, 2016 1 commit
  15. 15 Dec, 2016 4 commits
  16. 06 Dec, 2016 2 commits
  17. 02 Dec, 2016 1 commit
  18. 30 Nov, 2016 1 commit
    • Bram Schoenmakers's avatar
      Second attempt to make humanize_date() more deterministic · d9ba2172
      Bram Schoenmakers authored
      This reverts the first attempt (commit
      8310b029), because relative dates in terms of
      hours were printed.
      
      This attempt passes the now object that we just created to humanize(), so that
      will be used as a offset. If we don't supply that object, arrow will create a
      different datetime object representing 'now', which might be slightly off
      w.r.t. the now object we created.  Therefore the floating point arithmetic done
      within the arrow library might not produce the desired results (delta / 86400).
      
      By passing the offset ourselves I was able to produce reliable
      results.
      d9ba2172
  19. 29 Nov, 2016 6 commits
  20. 28 Nov, 2016 2 commits
  21. 27 Nov, 2016 3 commits