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).
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.
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
).