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

Update examples to refer to contrib/source-build.sh #151

Open
jasoncodes opened this issue Apr 8, 2018 · 3 comments
Open

Update examples to refer to contrib/source-build.sh #151

jasoncodes opened this issue Apr 8, 2018 · 3 comments

Comments

@jasoncodes
Copy link
Member

The install script output and generated example .freshrc file should reference contrib/source-build.sh. When $SHELL is bash we should output something like the following:

fresh freshshell/fresh bin/fresh --bin

fresh freshshell/fresh contrib/source-build.sh --file=~/.bash_profile
fresh freshshell/fresh contrib/source-build.sh --file=~/.bashrc

We should also output a different message if we did not generate a .freshrc file that omits mentioning initial setup and only outputs the message about opening a new shell for everything to take effect.

@jasoncodes
Copy link
Member Author

I think we could also get away with removing the default ~/.bashrc if it’s a file and the contents match /etc/skel/.bashrc. This would streamline setup on new Debian/Ubuntu user accounts.

@jasoncodes
Copy link
Member Author

It might also make sense for the install script to create ~/.dotfiles if it doesn’t exist, create ~/.dotfiles/freshrc if it doesn’t exist (instead of the current ~/.freshrc), then create the ~/.freshrc symlink to ~/.dotfiles/freshrc before invoking fresh for the first time. This would make the recommended setup more obvious. We could also go ahead and create an initial commit if ~/.dotfiles is not yet a git repo.

@jasoncodes
Copy link
Member Author

It might be worth revisiting the example section too to see if we can make it more obvious as to what each of the example lines does. Maybe add a link to the relevant documentation section for each.

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

No branches or pull requests

1 participant