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

What is the purpose of ~/.dotfiles: in README.md's example? #224

Closed
jennydaman opened this issue Jun 17, 2020 · 3 comments
Closed

What is the purpose of ~/.dotfiles: in README.md's example? #224

jennydaman opened this issue Jun 17, 2020 · 3 comments

Comments

@jennydaman
Copy link

https://github.com/anishathalye/dotbot/blob/f5e019105ec5a70a71d5afa78dc44baa0e87b721/README.md#full-example

- link:
    ~/.dotfiles: ''
@anishathalye
Copy link
Owner

That's a good question, perhaps I should amend the README to explain this.

Suppose I clone my dotfiles repo in /home/anish/stuff/src/dotfiles. This will create a symlink ~/.dotfiles -> /home/anish/stuff/src/dotfiles. This is convenient for having other stuff reference contents within the dotfiles directory. For example, I have a bin/ directory in my dotfiles, where I keep shell scripts, and then I add ~/.dotfiles/bin to my $PATH.

@jennydaman
Copy link
Author

Thank you for the explanation! With that line, ./install throws a warning if the repo is cloned to ~/.dotfiles (as also suggested in README.md) so it was confusing to me.

anishathalye added a commit that referenced this issue Jun 20, 2020
Without an explanation of what's going on here, this example is
unnecessarily confusing. It's a neat example, but probably not worth
explaining this in Dotbot's README.

See #224.
@anishathalye
Copy link
Owner

Thanks again for raising this issue -- I removed the confusing example from the documentation in 8f136ee (it was confusing without the explanation, and I figured that it wasn't worth explaining in the readme).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants