-
-
Notifications
You must be signed in to change notification settings - Fork 149
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
Space characters in bind-hooks #433
Comments
Hi! can you please confirm this issue is solved using latest version from git? |
Hi @jaromil. It did not work for me. I downloaded the latest version from git, installed it using
Output:
I created symlink with bind-hooks file: output: Am I doing something wrong? |
Hello again. As a workaround, I could make it work for me using symlink and then just before closing the tomb, I enter: |
Could you run tomb with -D for debug output? Just curious if it breaks in the region of line 2501 |
I tried it and it does not give any line numbers, and I don't know how to debug a bash script. But you could try this by creating this folder structure "/home/user/.config/Example Folder" and try to bind-hook to "media/ExampleFolder" in tomb. |
No, it doesn't give line numbers, but in that region are verbose messages which maybe can tell the state of vars. |
This does seem to be fixed by #500, at least as a workaround; you can now escape spaces in the target directory with a backslash. I just tested it and it seems to work. |
How can I implement bind-hooks if there is a space character in the path relative to $HOME? I enclosed the path names with "" but it did not work. Then I tried using symlink. Tomb opened without problem, but I was unable to close it with
tomb close
andtomb slam
. I am using Tomb 2.9.0. I can not remove the space character from the folder name, because it was created by a software and it won't work if I change it.The text was updated successfully, but these errors were encountered: