fork download
copy 
  1. #!/bin/bash
  2.  
  3. # This command is designed to take input from stdin
  4. somecommand --someoption
  5.  
  6. read r s yourinput <<EOF
  7. "$yourinput"
  8. EOF
Success #stdin #stdout #stderr 0.02s 5312KB
comments (?)
stdin
copy 
Standard input is empty
stdout
copy 
Standard output is empty
stderr
copy 
prog.sh: line 4: somecommand: command not found
https://ideone.com/7JFdpR
The above code is a script which asks for stdin, and passes it through to a program expecting stdin.
Why does the read happen after the command? Why not capture stdin first, then invoke the command with what's captured?
If I wanted to run 'somecommand' several times in a loop, generating each input rather than reading it from the user, what would that look like?
language:
Bash (bash 5.0.3)
created:
12 years ago
visibility:
public

Share or Embed source code

Discover > Sphere Engine API

The brand new service which powers Ideone!

Discover > IDE Widget

Widget for compiling and running the source code in a web browser!