Q1: Why inline the global .git_config in the setup script?
Wouldn't it be better to add .gitconfig to the same folder as the rest of the dotfiles and then symlink it? Then you can run the following as part of the setup script:
git config --global user.name $full_name
git config --global user.email $email
The main advantage of this is at the .gitconfig is part of the dotfiles. If you change the file, the changes are automatically a part of the repo.
Q2: Why is z listed in both BREW_PACKAGES and OMF_PACKAGES?
BREW_PACKAGES="fish coreutils node pyenv python3 z yarn wget vim"
[...]
OMF_PACKAGES="z pure"
Also: The repo looks great. Definitely stealing parts of this 😄
Q1: Why inline the global .git_config in the setup script?
Wouldn't it be better to add
.gitconfigto the same folder as the rest of the dotfiles and then symlink it? Then you can run the following as part of the setup script:The main advantage of this is at the .gitconfig is part of the dotfiles. If you change the file, the changes are automatically a part of the repo.
Q2: Why is
zlisted in both BREW_PACKAGES and OMF_PACKAGES?Also: The repo looks great. Definitely stealing parts of this 😄