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
{{ message }}
This repository has been archived by the owner on Apr 19, 2023. It is now read-only.
As you can see in #661, parsing the output of gdrive upload "$FILE" is quite complicated right now, because gdrive prints to stderr (which is fine and can be kept that way, just wanted to mention it) and uses \r to overwrite every newly printed line to make it look like only one output line is just being updated instead of printing to a new line. I think a logging option for upload and download would be beneficial (maybe --raw or --log).
The text was updated successfully, but these errors were encountered:
If anyone is interested in this, I created a script that handles everything I described in this issue called gdrive.sh, which uses the cli tool watchbind (which I wrote myself) to turn the gdrive command into a custom TUI (terminal user interface) with custom keybindings.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As you can see in #661, parsing the output of
gdrive upload "$FILE"
is quite complicated right now, becausegdrive
prints to stderr (which is fine and can be kept that way, just wanted to mention it) and uses\r
to overwrite every newly printed line to make it look like only one output line is just being updated instead of printing to a new line. I think a logging option forupload
anddownload
would be beneficial (maybe--raw
or--log
).The text was updated successfully, but these errors were encountered: