-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Externalize $HOME/.tilde and make it configurable #165
Comments
My OMZ is intended to be edited in place. I do not wish to make the zshrc template massive. I use Perhaps, I'll remove |
I appreciate the overall approach -- these would be nice improvements indeed. |
Which one? |
Either of: One way or the other, they become This also brings in some sanity in terms of how one can group his/her local zsh behaviors by splitting stuff in multiple files (.zshrc, .zshenv etc.) instead of one giant .zshrc. |
Also, you'll keep the idea of templates/zshenv alive I hope. Having a default template for ~/.zshenv would always be nice :) |
Yes, see #171. I need $PATH before zshrc, not after. It's not working at the bottom of zshrc. |
Rightly, indeed :) |
Completion for middleman
$HOME/.tilde
is forced into$infopath
,$manpath
and$path
currently. The intent is nice, but it would be even nicer not to hard-code$HOME/.tilde
and expose it as configurable property (with$HOME/.tilde
as the default) intemplates/zshrc
.This way one can just override in one place and have the same effect :)
The text was updated successfully, but these errors were encountered: