[go-nuts] Wrapping executable that takes input and output files such that it uses stdin and stdout instead (using named pipes)

Hi! I asked this previously on Stack Overflow but so far have not received a response, so I figured I will try here as well. I'm trying to wrap an executable that takes an input and output file paths as arguments, such that it will be possible to provide the input and output as stdin and stdou

Re: [go-nuts] Wrapping executable that takes input and output files such that it uses stdin and stdout instead (using named pipes)

fIn.Close() > happens after io.Copy(os.Stdout, buf), which completes after your cat > command finishes. But cat won't finish until its input pipe returns EOF, > which happens after fIn.Close(). > > On Wed, Feb 7, 2018 at 5:46 PM Or Rikon wrote: > >> Hi! >> >> I

Re: [go-nuts] Wrapping executable that takes input and output files such that it uses stdin and stdout instead (using named pipes)

s://en.wikipedia.org/wiki/Process_substitution>. >> > > Mike. > > > On Saturday, February 10, 2018 at 12:57:52 PM UTC, Or Rikon wrote: >> >> I actually fixed this a couple of days ago (see here >> <http://github.com/rikonor/stdio-wrapper>) without r