Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
$ calabash -i[port] input_file.xml -o[port] output_file.xml pipeline.xpl
$ calabash --input source=input_file.xml --output result=output_file.xml pipeline.xpl
(I have a script, /usr/local/bin/calabash, to take care of all the command-line Java weirdness that I am seemingly incapable of remembering no matter how many times I look it up. ☺)
Since XProc requires one primary input and one primary output, would it be possible to support using standard *nix redirect characters to specify the primary I/O ports? (< and > respectively)
$ calabash < input_file.xml > output_file.xml pipeline.xpl
The idea seems very appealing to me somehow.
A couple of ideas come to mind:
< "input1.xml input2.xml"
The text was updated successfully, but these errors were encountered:
You can do that. Sort of. The magic filename "-" stands for STDIN or STDOUT.
calabash -isource=- -oresult=- < input_file.xml > output_file.xml pipeline.xpl
Is that sufficient for your needs, or would you really like it to be totally implicit: if there's no binding for the primary input port, assume it's STDIN. (I think STDOUT is already handled this way.)
I don't think that would be unreasonable.
Sorry, something went wrong.
@ndw : Yep, implicit STDIN would be awesome!
Since I’m not a command-line guru, I just want to make sure: implicit STDIN means I could pipe things into calabash, or use < some-file.xml to specify the input—right?
Yes. And because I think STDOUT is already handled that way, I'll try to get this into the next release.
Just curious if/how this is doing.
It's on my list. There's a performance/memory leak bug that I've given a slightly higher priority. And I've been distracted by my day job and other things just recently.
(re) Ping! ☺
Fixed for 1.0.6, I believe.
Attempt to resolve issue #39, use STDIN by default if there's no bind…
…ing for the primary input port
w00t w00t w00t!
Thanks, Norm! 😄
No branches or pull requests