-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add link to hstow #43
Comments
Looks great! I'm pretty close to archiving stowsh as I find shell pretty much unmaintanable, and I'm happy to see someone else working on this use case! Couple of questions:
|
I was previously using a wrapper for GNU Stow, written by the GNU Stow maintainer, which arranged things this way. By using the same scheme I don't have to try to migrate my symlinks on all the hosts I've got my dotfiles checked out on. Independently, I like how it makes it easy to identify the symlinks created by hstow, and means the unstow() routine can be simple.
It's unfortunate an XDG-compatible location wasn't chosen originally. But unfortunately I can't change it now without losing the two advantages noted above.
Strange, can you 'set -x' for more info, please? |
|
Hello,
Thanks. Does it fix it if you replace the dir_pat line with this:
dir_pat="^.$(echo $DIR | cut -c$(echo $HOME | wc -m | tr -d ' ')-)/"
…--
Sean Whitton
|
... and then nothing. The process is stuck. No output and I have to ctrl-c to get back a prompt. |
Hello Mike,
Thank you for your reply. It confirms my previous fix is correct, at
least, even if you have now stumbled upon another problem. I'm afraid I
have no idea why it would get stuck there, and I don't have access to an
OS X machine myself to look into it further. If you do figure it out,
please let me know.
…--
Sean Whitton
|
Hello,
Thanks for this script. I recently implemented something similar, except it truly has no dependencies other than POSIX sh. Perhaps you'd consider adding a link to my script to the README?
https://git.spwhitton.name/dotfiles/tree/bin/hstow
The text was updated successfully, but these errors were encountered: