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
I don't think there is a valid usecase for the --stdout download option sending the downloaded files to STDOUT while creating empty directories? That is the behavior I am observing.
I am trying to download a lot of text files from many items and concatenate them to a single output file:
while read identifier; do ia download $identifier ${identifier}_suffix.txt --stdout ; done >> combined.txt < list-of-identifiers.tsv
Which does what I want, but creates a lot of empty directories.
I get the behavior I want by adding --no-directories to the command, but I think it's always safe to assume no directories with --stdout.
If this is deemed a good suggestion, I'd be prepared to implement it. I haven't looked at the code in a while, but I'm assuming it's pretty straightforward to pass another option.
The text was updated successfully, but these errors were encountered:
This is a suggestion / enhancement.
I don't think there is a valid usecase for the
--stdout
download option sending the downloaded files to STDOUT while creating empty directories? That is the behavior I am observing.I am trying to download a lot of text files from many items and concatenate them to a single output file:
Which does what I want, but creates a lot of empty directories.
I get the behavior I want by adding
--no-directories
to the command, but I think it's always safe to assume no directories with--stdout
.If this is deemed a good suggestion, I'd be prepared to implement it. I haven't looked at the code in a while, but I'm assuming it's pretty straightforward to pass another option.
The text was updated successfully, but these errors were encountered: