Skip to content
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

NVM install errors on new machine #7

Open
heathflohre opened this issue Jan 5, 2019 · 2 comments · May be fixed by #19
Open

NVM install errors on new machine #7

heathflohre opened this issue Jan 5, 2019 · 2 comments · May be fixed by #19

Comments

@heathflohre
Copy link

Thank you so much for putting this together! I was wondering if this is safe for running on a fresh machine. First, always skips the NVM install, thinking it's already installed. If I switch the check to mimic the MAS install (placing the skip message after the if statement and moving the install steps after the else statement), it works. Also, should regular dotfiles like .bash_profile be created or cloned and synced first? When this is run on a fresh machine, the NVM install step errors when trying to add the path.

@chrisrowe
Copy link

+1 I'm also seeing this

@minamarkham
Copy link
Owner

Hi @heathflohre & @chrisrowe! Sorry for the ridiculous delay in getting back to you. If you're still experiencing this problem, can you please send me the logs after running sh slay 2>&1 | tee ~/slay.log?

@bongani-m bongani-m linked a pull request Aug 11, 2019 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants