You have to create duplicate of the stream by piping it to two streams. You can create a simple stream with a PassThrough stream, it simply passes the input to the output. const spawn = require(‘child_process’).spawn; const PassThrough = require(‘stream’).PassThrough; const a = spawn(‘echo’, [‘hi user’]); const b = new PassThrough(); const c = new … Read more
For simple scenarios, you could use this approach: bash -c “echo ‘your command goes here'” For example, this function retrieves the CPU model name using piped commands: func getCPUmodel() string { cmd := “cat /proc/cpuinfo | egrep ‘^model name’ | uniq | awk ‘{print substr($0, index($0,$4))}'” out, err := exec.Command(“bash”,”-c”,cmd).Output() if err != nil { … Read more
I spent a while trying to figure this out and got it working with the following: cat data.json | curl -H “Content-Type: application/json” -X POST –data-binary @- http://api
In Angular a good technique for sharing common directives, components, pipes, etc. is to use a so called shared module. Those modules declare and export common parts, to make them usable for any of your other modules. The fundamentals section of the angular documentation is a very good read about shared modules. Let’s take as … Read more
The correct notation for Process Substitution is: while read i; do echo $i; done < <(echo “$FILECONTENT”) The last value of i assigned in the loop is then available when the loop terminates. An alternative is: echo $FILECONTENT | { while read i; do echo $i; done …do other things using $i here… } The … Read more
A Unix pipe connects the STDOUT (standard output) file descriptor of the first process to the STDIN (standard input) of the second. What happens then is that when the first process writes to its STDOUT, that output can be immediately read (from STDIN) by the second process. Using multiple pipes is no different than using … Read more
You can use :w !cmd to write the current buffer to the stdin of an external command. From :help :w_c: :w_c :write_c :[range]w[rite] [++opt] !{cmd} Execute {cmd} with [range] lines as standard input (note the space in front of the ‘!’). {cmd} is executed like with “:!{cmd}”, any ‘!’ is replaced with the previous command … Read more
One easy way is to add a pass of tr to squeeze any repeated field separators out: $ ps | egrep 11383 | tr -s ‘ ‘ | cut -d ‘ ‘ -f 4
The eval command exists for this very purpose. eval “$( ls | sed… )” More from the bash manual: eval eval [arguments] The arguments are concatenated together into a single command, which is then read and executed, and its exit status returned as the exit status of eval. If there are no arguments or only … Read more
In the Windows Powershell console, type [System.IO.Directory]::GetFiles(“\\.\\pipe\\”) If your OS version is greater than Windows 7, you can also type get-childitem \\.\pipe\ This returns a list of objects. If you want the name only: (get-childitem \\.\pipe\).FullName In Powershell 7, the second example \\.\pipe\ does not work (see this known bug), so you will have to … Read more