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 thought that it might be useful if the CLI had a way of passing its output directly to stdout, rather than into an intermediate file. That way it could be used directly on the command line without having to use a file which then has to be cleaned up, and also would make embedding it in other applications easier.
This seems (at least to my naive view) a pretty decent output and will always be in line with what one would expect from the CSV too. I get comma separated values in the output which I can then pipe around.
I don't mind passing stdout to -indices, actually it makes sense in a way to have lots of different things you can pass to this flag, maybe .JSON in the future :) but the only issue is other things are emitted into stdout also, like the percentage. This could be solved with something like what is proposed in #10
Hello,
I thought that it might be useful if the CLI had a way of passing its output directly to stdout, rather than into an intermediate file. That way it could be used directly on the command line without having to use a file which then has to be cleaned up, and also would make embedding it in other applications easier.
For example:
If you still wanted an intermediary file:
but you could also unlock some cool inline scripting like grabbing the first six slices only
Again, available to PR this sort of thing if its within scope and if I had some direction :)
The text was updated successfully, but these errors were encountered: