1. 10 Dec, 2019 1 commit
  2. 13 Nov, 2019 2 commits
  3. 12 Nov, 2019 2 commits
  4. 16 Oct, 2019 2 commits
  5. 14 Oct, 2019 1 commit
  6. 13 Oct, 2019 1 commit
  7. 23 Aug, 2019 1 commit
  8. 18 Aug, 2019 2 commits
  9. 05 Aug, 2019 1 commit
  10. 11 Jul, 2019 3 commits
  11. 21 May, 2019 2 commits
  12. 09 May, 2019 1 commit
  13. 08 May, 2019 1 commit
  14. 14 Apr, 2019 3 commits
  15. 19 Mar, 2019 2 commits
  16. 11 Mar, 2019 1 commit
  17. 09 Mar, 2019 2 commits
  18. 05 Mar, 2019 1 commit
  19. 21 Feb, 2019 1 commit
  20. 19 Feb, 2019 1 commit
    • Max Battcher's avatar
      Use environment variables in Windows paths · 124d4ec3
      Max Battcher authored
      This better mimics the Unix like `~` usage for the others, removing the need for "variable replacement" by the user. Paths in this format are supported in a lot of places in Windows, such as File Explorer, the classic Run dialog, and traditional CMD.EXE. PowerShell users should already know how to convert these already, so not including that here. (For reference: `%USERPROFILE%` is supported as `~` in PowerShell, and `$env:LocalAppData` is the variable format for `%LocalAppData%`.)
      124d4ec3
  21. 04 Jan, 2019 2 commits
  22. 22 Nov, 2018 5 commits
  23. 03 Nov, 2018 2 commits