-
Notifications
You must be signed in to change notification settings - Fork 66
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
--as-path <PATH> option skips empty string #1135
Comments
Thanks @F3-L1x for opening this issue! Can you please write how you did run the CLI command? |
Wow, what a fast reply.^^ I tried it different ways:
|
First, am I right that your original intend is to run Moreover, I think that in fact there shouldn't be a use-case where you need to use an empty Still, digging a bit into details: About 3: This is treated by clap like no |
Correct handling of paths starting with |
Yes that's what I was trying to do.
You mean, it should be automatically saved as a relative-path, when using Thanks for you tip with the:
That did the trick. (: Thank you for your super quick help and I'll try your fix soon. :) 👍 Edit:
It looks like, this has sth. to do with, how powershell handles parameters/arguments (probably discarding empty strings and gobbling the next available argument/option). I get a different output from cmd and msys-bash:
|
Exactly. This is also the current behavior if you backup a relative path without leading If you want to backup an absolute path, you can simply specify the full path. |
Hello wonderful people,
at first, I'm so grateful for this great project. :3
Just a minor thing.
I noticed, that using the '--as-path' cli-option (when creating a backup) doesn't recognize an empty path, while the configuration-option does.
It would be nice, if both had this ability.
Thank you for your time. (:
The text was updated successfully, but these errors were encountered: