Fix initial setup scenario #17
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some fixes to problems I ran into on a new initial setup: - Homebrew has a new install script… It requires TTY, so it's hard to run it from another script. - With Homebrew not loaded into the shell via the zprofile file, it's not available in the other topics further down the line. Manually loading it with the `use_brew` helper should fix this - On brand new machines, the `~/.config` directory may not exist, which breaks symlinking there. So create it as part of the `setup` script
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some fixes to problems I ran into on a new initial setup:
Homebrew has a new install script… It requires TTY, so it's hard to
run it from another script.
With Homebrew not loaded into the shell via the zprofile file, it's
not available in the other topics further down the line. Manually
loading it with the
use_brewhelper should fix thisOn brand new machines, the
~/.configdirectory may not exist, whichbreaks symlinking there. So create it as part of the
setupscript