That'd be the approach I'd take, probably. I haven't played around with oh-my-zsh in particular, myself, but you could probably be more specific about what you'd like to source.

Closing this out since it's not an issue per se, but definitely feel free to continue to discuss this here. :)

Thanks, definitely not an issue. I have a bad habit of treating the issue tracker as a project forum. Thanks for the reply. I'll give this some more thought and link a pull request/patch if I do anything. In the meantime, I'd be interested to hear what others have to say. There was astoundingly little in a Google search on this, but then again googling "dotfiles" isn't fun.

Depending on which is smaller, you can make an include/exclude list of which plugins you want/don't want in oh-my-zsh. On line 17-21 of zshrc is where the magic happens. You'll want to manage the exclude/include at this point to parse out which of the oh-my-zsh plugins you want to include/exclude.

from http://aniketpant.com/2013/04/get-your-dotfiles-straight/

"I had to make some changes for Holman's dotfiles to work for me. The major problem I faced was the fact that I use oh-my-zsh and it has it's own set of features to take care of. And then, Holman's dotfiles work from the your cloned repo. To fix it, I changed one variable and introduced my own. $ZSH was changed to $ZSHDOT everywhere and I changed $ZSH to point to .oh-my-zsh and everything became peaceful."

--> https://github.com/aniketpant/dotfiles/blob/master/zsh/config.zsh

Thanks @gaboesquivel

Both the @holman dotfiles and oh-my-zsh seem to use the $ZSH env variable.

Maybe setting the var before any oh-my-zsh commands?

ZSH=~/.oh-my-zsh upgrade_oh_my_zsh

I think it makes sense for both projects to not name it $ZSH, but something more specific: $ZSHDOT here, and maybe $OMZSH there. What do others think? Should I submit a PR?

That makes sense to me. I was surprised to see the variable named like that for two separate systems. Wondered if it was some convention i didn't understand.