bulia byak wrote:
> Devs, (and Bob especially,)
> Our efforts to make Inkscape's Windows port not output errors on the
> console have been way too successful. Now it never ouputs ANYTHING to
> the console, ever. Not even if I redirect it to file (> file).
> Now, however, I have a project that critically depends on querying SVG
> files with Inkscape using --query* command line options. Worst of all,
> this must run on Windows.
> So my question is, is there any simple fix I can do to make this work
> (I don't mind to run a custom version of Inkscape for this project)?
> Or, should I just add --query-output=file option which would make it
> write the output to a file, which I can then parse?
It would be much better to fix this properly. --query-output=file IMHO
would be evil. If you need a quick work around try `inkscape
--query-whatnot > file`.