If you have a Fortran 2003 compiler, the intrinsic module iso_fortran_env defines the variables input_unit, output_unit and error_unit which point to standard in, standard out and standard error respectively. I tend to use something like #ifdef f2003 use, intrinsic :: iso_fortran_env, only : stdin=>input_unit, & stdout=>output_unit, & stderr=>error_unit #else #define stdin 5 #define stdout 6 … Read more
I solved this problem the following way: var access = fs.createWriteStream(‘/var/log/node/api.access.log’); process.stdout.write = process.stderr.write = access.write.bind(access); Of course you can also separate stdout and stderr if you want. I also would strongly recommend to handle uncaught exceptions: process.on(‘uncaughtException’, function(err) { console.error((err && err.stack) ? err.stack : err); }); This will cover the following situations: process.stdout.write … Read more
One thing to also remember, there’s nothing stopping you from writing functions to avoid the boilerplate. For example I have a command line app that uses log and I wrote this function: func captureOutput(f func()) string { var buf bytes.Buffer log.SetOutput(&buf) f() log.SetOutput(os.Stderr) return buf.String() } Then used it like this: output := captureOutput(func() { … Read more
To redirect the stdout to stderr, use your command as follows :- $ command-name 1>&2 where command-name is the command you’re going to feed, 1 represents stdout and 2 represents stderr .
I can’t think of a way to do this in a cross-platform manner, but on GNU/Linux systems (and maybe other POSIX-compliant ones, too) you can freopen (“/dev/tty”, “a”, stdout). Is this what you were trying to do?
It’s not manipulating stdout — it’s overwriting the characters which have already been displayed by the terminal. Try this: #include <stdio.h> #include <unistd.h> static char bar[] = “=======================================” “======================================>”; int main() { int i; for (i = 77; i >= 0; i–) { printf(“[%s]\r”, &bar[i]); fflush(stdout); sleep(1); } printf(“\n”); return 0; } That’s pretty close … Read more
To alter the program to exit successfully in the case of a closed pipe, try: process.stdout.on(‘error’, function( err ) { if (err.code == “EPIPE”) { process.exit(0); } });
Perhaps you could put the exit value from PIPESTATUS into $? command 2>&1 | tee -a file.txt ; ( exit ${PIPESTATUS} )
Which platform are you on? You could try this recipe if you’re on Windows (the link suggests it’s Windows specific anyway). if sys.platform == “win32”: import os, msvcrt msvcrt.setmode(sys.stdout.fileno(), os.O_BINARY) There are some references on the web that there would/should be a function in Python 3.1 to reopen sys.stdout in binary mode but I don’t … Read more
CrazyCoder’s comment is the right way to go. I just formalize his comment as an answer here. Step1: Go to Run —> Edit Configurations Step2: Check the option: Emulate terminal in output console Voilà