You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, we can specify the output dir using output, but I want to be able to specify the file name.
The quickest way to implement this would be something like a output-file option or filename option.
But my further suggestion is to use --output to specify the file name, and --output-dir to specify the directory instead.
Even though this might be backwards incompatible, it follows the flag format of other CLI tools.
In addition, I 'd like the option to dump the file content into stdout by using --output -.
My main use case is that usually I have a link on my phone that I wish to transfer to my computer.
I don't need the link as a file, I only need it into my clipboard manager, so with this option, I can use qrcp receive --output - | clipboard_manager.
If this sounds ok, I can create a PR that adds this feature.
The text was updated successfully, but these errors were encountered:
I'm opening this issue because:
Suggestion to add file name as an option.
Right now, we can specify the output dir using
output
, but I want to be able to specify the file name.The quickest way to implement this would be something like a
output-file
option orfilename
option.But my further suggestion is to use
--output
to specify the file name, and--output-dir
to specify the directory instead.Even though this might be backwards incompatible, it follows the flag format of other CLI tools.
In addition, I 'd like the option to dump the file content into stdout by using
--output -
.My main use case is that usually I have a link on my phone that I wish to transfer to my computer.
I don't need the link as a file, I only need it into my clipboard manager, so with this option, I can use
qrcp receive --output - | clipboard_manager
.If this sounds ok, I can create a PR that adds this feature.
The text was updated successfully, but these errors were encountered: