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 Sep 3, 2020. It is now read-only.
Currently drive pull downloaded files end up where they should relative to the top level drive directory. It would be really useful if the file could be streamed to stdout as well. Here is how I envision this working:
An additional -O (output specifier) switch would specify the output file location, anywhere on the local file system. In recursive mode this would be a different top level drive directory. This destination could be specified as - and the file would stream to stdout.
That's just one idea, but anything that you come up with/is easiest for saving a file to stdout would be very much appreciated.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently
drive pull
downloaded files end up where they should relative to the top level drive directory. It would be really useful if the file could be streamed to stdout as well. Here is how I envision this working:An additional -O (output specifier) switch would specify the output file location, anywhere on the local file system. In recursive mode this would be a different top level drive directory. This destination could be specified as
-
and the file would stream to stdout.That's just one idea, but anything that you come up with/is easiest for saving a file to stdout would be very much appreciated.
The text was updated successfully, but these errors were encountered: