(reply back to the list)
I did. It made no difference. Although it appears that using a command that
genuinely wants input has the same behavior (e.g. `echo (bash -c 'read; echo
$REPLY')`), so I can see why you thought that.
Incidentally, Bash's behavior when a subshell needs input is to actual
Git is not asking for input. If you run it at the CLI directly it works fine
without ever consulting stdin.
What's more, I can't think of any good reason why a subcommand would ever leave
a suspended job. And if I try to `fg` it I get
> Send job 3, 'git svn find-rev HEAD' to foreground
>
>
>
Maybe git is asking for input? Try giving it an eof or something:
echo (yes | git svn find-rev HEAD)
-Dave
On Sat, Aug 11, 2012 at 3:26 PM, Kevin Ballard wrote:
> Well this is interesting. I just noticed that after running `echo (git svn
> find-rev HEAD)` it actually leaves a stopped job behi
Well this is interesting. I just noticed that after running `echo (git svn
find-rev HEAD)` it actually leaves a stopped job behind.
> jobs
Job Group State Command
2 2291stopped git svn find-rev HEAD
What could cause that?
-Kevin
On Aug 10, 2012, at 9:48 PM, Kevin Ballard wro
