| Age | Commit message (Collapse) | Author | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Co-authored-by: Liquidsoul <liquidsoul@liquidsoul.fr>
Co-authored-by: Alexander Polynomdivision <digitalmail555@googlemail.com>
Co-authored-by: loket <loket@cruftlab.io>
Co-authored-by: Connor Demille <subtlepseudonym@gmail.com>
 | 
 | 
Co-authored-by: Joel Kuzmarski <leoj3n@gmail.com>
 | 
 | 
Co-authored-by: Marshall Ford <inbox@marshallford.me>
Co-authored-by: Joel Kuzmarski <leoj3n@gmail.com>
 | 
 | 
 | 
 | 
Supposed to be POSIX-compatible. Proved to work in dash, yash and whatever
alpine uses. See https://unix.stackexchange.com/a/371873
 | 
 | 
 | 
 | 
This facilitates testing of changes to the core installation code: you'll be
able to do a roundtrip test of install and uninstall using the working code on
your branch.
Controlled by passing $REPO and $BRANCH environment variables to install.sh.
 | 
 | 
This changes the behavior to default to the binary found first in $PATH,
then checking it's actually in the shells file (/etc/shells).
If that fails go back to the previous behavior, but actually check that
the path obtained exists in the filesystem.
Co-authored-by: Joel Kuzmarski <leoj3n@gmail.com>
 | 
 | 
Co-authored-by: Fredrik Fornwall <fredrik@fornwall.net>
 | 
 | 
Guard clauses are if constructs that return early if there is an error
that prevents continuing. This way there isn't a big nesting of if
expressions.
 | 
 | 
Otherwise we risk a situation where a full path to `zsh` is commented, i.e.:
    #/usr/local/bin/zsh
 | 
 | 
This replaces the currently running process with the new one using `exec`
instead of creating a new process. This way, when the user `exit`s out of
the new shell it will not pop them back into the shell from which ohmyzsh
was installed from.
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
This will allow us to use tab stripping heredocs with `<<-'.
See http://www.tldp.org/LDP/abs/html/here-docs.html#EX71A
Add editorconfig file to enforce this style.
See http://editorconfig.org for more information.
 | 
 | 
 | 
 | 
 | 
 | 
This early return made it so the lock wasn't removed, therefore locking out
the upgrade script from ever entering the upgrade routine.
Fixes #6138 
Note: the logic needs some rework.
 | 
 | 
* 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
 | 
 | 
Fixes #7492
 | 
 | 
* use https everywhere
* use https links on the files that are left
Also, removed some broken links and updated redirections.
 | 
 | 
Otherwise these files are not sourced:
  1. /etc/zprofile
  2. ~/.zprofile
  3. /etc/zlogin
  4. ~/.zlogin
  5. ~/.zlogout
  6. /etc/zlogout
 | 
 | 
 | 
 | 
Quote $ZSH where necessary in install script
 | 
 | 
`[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.
 | 
 | 
 | 
 | 
Fixes #4955
Closes #5931
Closes #6398
Co-authored-by: Void <vst4rbot@gmail.com>
Co-authored-by: Kaleb Elwert <belak@coded.io>
 | 
 | 
Quick fix to the script not finding git due to hash.
Solves #6697.
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
This makes things work even on system lacking /bin/sh, such as on
non-rooted Android systems.
 | 
 | 
See robbyrussell@b67961d
 | 
 | 
 | 
 | 
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.
 | 
 | 
Also accept any forms of yes as an answer to the "do you want to update?" prompt
 | 
 | 
 | 
 | 
 | 
 | 
- Need dot `.` for POSIX compliant instead of `source`
 - Use modern syntax for command substitution
 - Fix missing double quotes
 | 
 | 
Really this time :P
Fixes #4533
 | 
 | 
 | 
 | 
We need to use POSIX syntax. This file is no longer executed with zsh.
Fixes #4483.
 | 
 | 
Drops the `function` keyword and uses only `func(){}` syntax as per the
POSIX specification:
http://pubs.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_09_05
Related: #4531
 | 
 | 
This reverts commit c9d93757e82785a0fd1e0d1222f5d61e01849703, which
makes it fail with a syntax error:
  sh: 1: Syntax error: "(" unexpected
 |