| Age | Commit message (Collapse) | Author |
|---|
|
|
|
* 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
|
|
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
|
|
|
|
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.
|
|
|
|
See robbyrussell@b67961d
|
|
|
|
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
|
|
Fix install.sh/upgrade.sh for tput-less systems
|
|
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:
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.
|
|
@fcrozat's original fix assumes `which` not to output anything to STDOUT
in case the command is not found. That is not necessarily true on all
systems. A better solution is to check the return value instead.
Fixes #4376
|
|
This is a hack to keep the installer working on systems without tput/terminfo.
|
|
Add Cygwin support to installer.
|
|
Conflicts:
tools/install.sh
|
|
Fixes issue #4376
|
|
|
|
Repair `zsh` Path Permissions on `oh-my-zsh` Startup under Cygwin
|
|
Conflicts:
tools/install.sh
tools/upgrade.sh
|
|
* Balk at incompatible Windows/MSYS git
* Test for chsh presence before trying to use it
* Replace non-portable `[[ ... ]]` and `[ x = *pattern* ]` constructs
|
|
Check if Zsh is installed prior to installing Oh My Zsh
|
|
Installer: Remove "sed -i" for portability and hygiene
|
|
|
|
Check if Zsh is installed before installing anything else.
New-commers, or people who don't read the disclaimers(ex. me) will go
straight to stack overflow if chsh -s returns an error.
|
|
Installation previously assumed the existence of a "chsh" command in the current
${PATH}. Since Cygwin does *NOT* provide this command, installation now tests
for the existence of this command before attempting to run it.
|
|
For safety, a umask of 022 prohibiting both group and other writability is now
enforced during OMZ installation. In theory, this should reduce the likelihood
of subsequent compinit() failures due to insecure directory permissions under
all platforms except for default Cygwin installations (in which Windows ACLs
override POSIX umasks).
|
|
Do not use terminal visual effects if not connected to a terminal.
|
|
|
|
fix test for chsh in install
in case $SHELL is zsh but not the last one in /etc/shells
fixes #3026 fixes #3779 fixes #3780
|
|
portable to systems whose sed lacks "-i", like OpenBSD.
|
|
Save ZSH path in newly created .zshrc
|
|
Use `--depth=1` to clone just the lastest version rather than every version in git.
|
|
|
|
Prevent chsh from running when $SHELL is already zsh
|
|
|
|
|
|
Some environments (such as Android) does not have /usr/bin.
|
|
The intention of the redirection to /dev/null is to hide the output
'hash: no such command: git' since we rely on the exit status.
However, the output goes to stderr, so it's stderr that needs to be
redirected. For completeness, we redirect both stderr and stdout using
'2>&1'.
Example:
[~]$ hash git > /dev/null
[~]$ PATH=''
[~]$ hash git > /dev/null
hash: no such command: git
[~]$ hash git > /dev/null 2>&1
[~]$
|
|
/Users/robbyrussell/.oh-my-zsh and such). Also mentioining our twitter account after install
|
|
|
|
|
|
|
|
Fix install.sh compatibility with /bin/sh
|
|
Add configuration placeholders to installer template
|
|
Although the zshrc template adds a PATH= string, this is overwritten by the installer script.
This allows it to be placed anywhere in the file instead of having to append at the end.
|
|
|
