-
Notifications
You must be signed in to change notification settings - Fork 116
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
understanding gnu stow #14
Comments
hey, no worries. stow is an on demand tool. when you run the command it looks in the specified directory for files then symlinks them into the target location. if you edit one of the source files already linked the changes are immediate. but if you create a new file the symlinks are not created yet until you run stow (again). hope that helps! i wrote a blog post about my workflow that includes a number of stow examples. ok, here's a little example i cooked up for ya: this is our tree of dotfiles and a
enter the dotfiles directory, stow the motd file and look at the results:
repeat the process with the cron directory:
create a new file in the cron directory and notice the
run stow again, and the new file is linked into place:
|
Hi,
I'm new to Stow and I'm having difficulties understanding how to manage the dotfiles properly.
My quest is: If you have to add a file, do you create it in the repo and then relaunch stow every time?
I know my question is off topic and I will remove it if you don't want to answare me but I really appreciate any kind of help.
The text was updated successfully, but these errors were encountered: