You can’t get the filename exactly as input; the shell will handle all that redirection stuff without telling you. In the case of a direct < file redirection, you can retrieve a filepath associated with stdin by using fstat to get an inode number for it then walking the file hierarchy similarly to find / … Read more
The csh shell has never been known for its extensive ability to manipulate file handles in the redirection process. You can redirect both standard output and error to a file with: xxx >& filename but that’s not quite what you were after, redirecting standard error to the current standard output. However, if your underlying operating … Read more
Use another file descriptor { command1 2>&3 | command2; } 3>&1 1>&2 | command3 You can use up to 7 other file descriptors: from 3 to 9. If you want more explanation, please ask, I can explain 😉 Test { { echo a; echo >&2 b; } 2>&3 | sed >&2 ‘s/$/1/’; } 3>&1 1>&2 … Read more
command 2>&1 1>nul doesn’t work is not correct. It works. But as usual, it does what you asked not what you wanted From left to right: 2>&1 data to stream 2 (stderr) will be sent to a copy/duplicate of the handle that stream 1 (stdout) is using. 1>nul data to stream 1 will be sent … Read more
PowerShell CLI fundamentals: PowerShell editions: The CLI of the legacy, bundled-with-Windows Windows PowerShell edition is powershell.exe, whereas that of the cross-platform, install-on-demand PowerShell (Core) 7+ edition is pwsh.exe (just pwsh on Unix-like platforms). Interactive use: By default, unless code to execute is specified (via -Command (-c) or -File (-f, see below), an interactive session is … Read more
Little-known feature: The redirection operator can go anywhere on the line. >>file.txt echo 2
You need to escape the | character to prevent its being interpreted at the time of parsing the loop command. Use ^ to escape it: FOR /f “delims=” %%A in (‘dir /b “my_dir\*.csv” ^| find /V “summary”‘) do ( rem do what you want with %%A here ) Once escaped, the | becomes part of … Read more
no need to launch sub shell. Use a code block will do as well. { time ls; } 2> out.txt or { time ls > /dev/null 2>&1 ; } 2> out.txt
The code below creates a console-less process with stdout and stderr redirected to the specified file. #include <windows.h> int _tmain(int argc, _TCHAR* argv[]) { SECURITY_ATTRIBUTES sa; sa.nLength = sizeof(sa); sa.lpSecurityDescriptor = NULL; sa.bInheritHandle = TRUE; HANDLE h = CreateFile(_T(“out.log”), FILE_APPEND_DATA, FILE_SHARE_WRITE | FILE_SHARE_READ, &sa, OPEN_ALWAYS, FILE_ATTRIBUTE_NORMAL, NULL ); PROCESS_INFORMATION pi; STARTUPINFO si; BOOL ret = … Read more
Not an expert on encoding, but after reading these… http://blogs.msdn.com/b/powershell/archive/2006/12/11/outputencoding-to-the-rescue.aspx http://technet.microsoft.com/en-us/library/hh847796.aspx http://www.johndcook.com/blog/2008/08/25/powershell-output-redirection-unicode-or-ascii/ … it seems fairly clear that the $OutputEncoding variable only affects data piped to native applications. If sending to a file from withing PowerShell, the encoding can be controlled by the -encoding parameter on the out-file cmdlet e.g. write-output “hello” | out-file “enctest.txt” … Read more