{"push_id":666370883,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"0fc5a482f3b863ee622af1aaf1b2b49cd432e28a","before":"8450744a8353aff480c9f78fb1f75aab3d90443a","commits":[{"sha":"0fc5a482f3b863ee622af1aaf1b2b49cd432e28a","author":{"email":"1a73af9e7ae00182733b2292511b814be66f065f@marvinkturner.com","name":"Marvin T"},"message":"improved zshrc && zsh-theme\n\ndoubleend.zsh-theme:\n- more colors\n- tells venv AND python version\n    added echo `python -c \"import sys; print(sys.version[:5])\"' '`.\n    This displays the numeric version of python, without the other\n    stuff. Since this is my main language, it is important that this\n    info is available regardless of whether a venv is active or not.\n\nzshrc:\n- disable default `$PS1` modification entirely\n    pyenv-virtualenv automatically activates venvs when you switch\n    into a related dir, but the venv was being added both at the\n    beginning of $PS1 and at my custom location (due to custom\n    `activate` function). Now, when it automatically activates, venv\n    info is only displayed where I want it to be.\n- refactored `zshconfig` into a fuction\n    before it was an alias, and it wasn't very smart. Now, it waits\n    for you to save/close the .zshrc and then it reloads it into your\n    shell (source ~/.zshrc). This is done by issuing -w (wait)\n    parameter to the subl executable.\n- moved pyenv config back\n    Was adding pyenv to `$PATH` in .profile. BAD idea. Due to the\n    load order of startup files, the pyenv shims directory was behind\n    `/usr/local/bin` (system python location). Nasty things were\n    happening in venvs as a result. Ensuring pyenv shims are added to\n    path after `/usr/local/bin` fixes this","distinct":true,"url":"https://api.github.com/repos/mkturner/zsh-config/commits/0fc5a482f3b863ee622af1aaf1b2b49cd432e28a"}]}