1. 03 Jun, 2019 5 commits
  2. 18 Apr, 2019 1 commit
  3. 07 Apr, 2019 1 commit
  4. 26 Feb, 2019 1 commit
    • Robby Russell's avatar
      Updating Oh My Zsh shop URLs (#7619) · f319aa84
      Robby Russell authored
      * Updating Oh My Zsh shop URLs
      
      Linking directly to the Oh My Zsh inventory vs the top-level store with non-OMZ items.
      
      * Updating link to Oh My Zsh products in the install script
      
      * Updating link to Oh My Zsh shop products in the upgrade script
      
      * Getting rid of 't-' in shirts for now
      f319aa84
  5. 15 Jan, 2019 1 commit
  6. 07 Aug, 2018 1 commit
    • Janosch Schwalm's avatar
      use https everywhere (#6574) · 19b925e7
      Janosch Schwalm authored
      * use https everywhere
      
      * use https links on the files that are left
      
      Also, removed some broken links and updated redirections.
      19b925e7
  7. 01 Jul, 2018 1 commit
  8. 15 Jun, 2018 1 commit
  9. 13 Jun, 2018 1 commit
  10. 15 May, 2018 1 commit
    • Gert de Pagter's avatar
      Update the update prompt (#6825) · 2b7a41b0
      Gert de Pagter authored
      `[Oh My Zsh] Would you like to check for updates? [Y/n]: ` does not make sense, 
      since answering yes will download/apply the new updates instead of checking for them.
      2b7a41b0
  11. 06 May, 2018 1 commit
  12. 05 May, 2018 1 commit
  13. 17 Apr, 2018 1 commit
  14. 01 Nov, 2017 1 commit
  15. 03 Oct, 2016 3 commits
  16. 09 Aug, 2016 1 commit
  17. 16 Jun, 2016 1 commit
  18. 30 May, 2016 1 commit
  19. 15 Dec, 2015 1 commit
    • Robin Hallabro's avatar
      Use consistent wording when updating · 18ca953f
      Robin Hallabro authored
      When the user is asked to update oh-my-zsh it says "[Oh My Zsh] Would
      you like to check for updates? [Y/n]:". When the user agreed to update
      the next text would say "Upgrading Oh My Zsh" which is inconsistent
      with the question.
      18ca953f
  20. 04 Nov, 2015 1 commit
  21. 23 Oct, 2015 2 commits
  22. 21 Oct, 2015 5 commits
  23. 20 Oct, 2015 1 commit
    • Brian J Brennan's avatar
      Make install script safer · c9d93757
      Brian J Brennan authored
      This changeset wraps all of the commands in tools/install.sh in a
      function and then calls that function as the last line of the
      script.
      
      The current install instructions ask the user to download the install
      script using `curl` and pass the result to `sh`. This is totally
      fine (as long as both the instructions and the script itself are served
      using HTTPS), but the script should be written in a way such that it
      doesn't start trying to actually *do* anything until the very last line.
      
      The reason is due to the way `curl` work: if the socket drops before the
      request is complete (server abruptly hangs up, client's internet flakes
      out, etc.), `curl` will return the partial data that it received. Here
      is an example of that:
      
      ![partial file execution](https://cldup.com/qU_Mnh2GmT.png)
      
      A way this might cause issues for tools/install.sh is if the connection drops
      after cloning but before the repository (L53-56). The .zshrc
      configuration will not be copied and the shell will not be changed, but
      if the user tries to run the install script again it will claim
      oh-my-zsh is already installed (L31-39).
      
      While this is not a particularly dangerous error condition (the user can
      just delete .oh-my-zsh and re-run), it can certainly be confusing for
      new users. This also helps future-proof the script for a time when it
      might need to use a "dangerous" command, e.g. `rm`, and we want to make
      sure it happens in the most transactional way possible.
      c9d93757
  24. 16 Oct, 2015 2 commits
  25. 05 Oct, 2015 1 commit
  26. 28 Sep, 2015 1 commit
  27. 22 Sep, 2015 1 commit
  28. 21 Sep, 2015 1 commit