This is called process substitution: Process substitution is a form of redirection where the input or output of a process (some sequence of commands) appear as a temporary file. Also from Bash Reference Manual → 3.5.6 Process Substitution: Process substitution allows a process’s input or output to be referred to using a filename. It takes … Read more
The problem is, the redirection character (>) is a shell-based construct, not an executable. So unless you’re running this command through something like bash (which you’re not), it’s going to be interpreted as a literal character argument to your exiftool invocation. If you want to get this to work, you have two options: Get bash … Read more
Using redirection sends the contents of the input file to stdin, so you need to read from stdin inside your code, so something like (error checking omitted for clarity) #include <stdio.h> #define BUFFERSIZE 100 int main (int argc, char *argv[]) { char buffer[BUFFERSIZE]; fgets(buffer, BUFFERSIZE , stdin); printf(“Read: %s”, buffer); return 0; }
The simple naive way that is slow because it opens and positions the file pointer to End-Of-File multiple times. @echo off command1 >output.txt command2 >>output.txt … commandN >>output.txt A better way – easier to write, and faster because the file is opened and positioned only once. @echo off >output.txt ( command1 command2 … commandN ) … Read more
You can use one-line heredoc cat <<< “This is coming from the stdin” the above is the same as cat <<EOF This is coming from the stdin EOF or you can redirect output from a command, like diff <(ls /bin) <(ls /usr/bin) or you can read as while read line do echo =$line= done < … Read more
You can use the following: C:\>type nul > C:\does\not\exist\file.txt && echo ok || echo fail The system cannot find the path specified. fail C:\>echo %errorlevel% 1 I always assumed the && and || operators used ERRORLEVEL, but apparently not. Very curious that ERRORLEVEL is set after redirection error only if you use the || operator. … Read more
>> /dev/null redirects standard output (stdout) to /dev/null, which discards it. (The >> seems sort of superfluous, since >> means append while > means truncate and write, and either appending to or writing to /dev/null has the same net effect. I usually just use > for that reason.) 2>&1 redirects standard error (2) to standard … Read more
Here is a class I have written in order to handle that kind of stuff. Feel free to use it. Its purpose is to start a console application and “talk” to it. It has the ability to receive output as well. Good luck. using System; using System.Diagnostics; using System.Text; using System.Threading; using System.Threading.Tasks; public class … Read more
This was not supported in PowerShell v1 [and as of v5, it’s still not…] An example workaround is: Get-Content test.full | .\test_cfdp.exe | tee test.log
The Bash manual has a clear example (similar to yours) to show that the order matters and also explains the difference. Here’s the relevant part excerpted (emphasis mine): Note that the order of redirections is significant. For example, the command ls > dirlist 2>&1 directs both standard output (file descriptor 1) and standard error (file … Read more