When does piping not work on Windows? It's always worked for me. If a redirect doesn't work, I don't know that doing the redirect inside the program will necessarily fix it...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Windows 11 Pro, piping doesn't work at all.
E.G.: xml val -e -s abc.xsd xyz.xml>result.txt
In result.txt I have the result (e.g. xyz.xml - invalid) but the other output (xyz.xml🔢20 Element...) is only to see in the cmd-box.
I wanted to interpret the output (for example jump directly to the appropiate line).
With the already mentiones options (-o or --output) the program could open a file instead of stdout.
Is there a chance?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I found a solution: In my example above, I have added the redirection from stderr to stdout!
xml val -e -s abc.xsd xyz.xml > result.txt 2>&1
"2>&1" does the job!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When does piping not work on Windows? It's always worked for me. If a redirect doesn't work, I don't know that doing the redirect inside the program will necessarily fix it...
Hi,
Windows 11 Pro, piping doesn't work at all.
E.G.: xml val -e -s abc.xsd xyz.xml>result.txt
In result.txt I have the result (e.g. xyz.xml - invalid) but the other output (xyz.xml🔢20 Element...) is only to see in the cmd-box.
I wanted to interpret the output (for example jump directly to the appropiate line).
With the already mentiones options (-o or --output) the program could open a file instead of stdout.
Is there a chance?
I found a solution: In my example above, I have added the redirection from stderr to stdout!
xml val -e -s abc.xsd xyz.xml > result.txt 2>&1
"2>&1" does the job!