(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 actually wait
to satisfy that input. Seems like Fish should do the same thing, instead of
suspending the job and making it impossible to resume.
In any case, git svn find-rev doesn't prompt for input, and giving it some with
an echo doesn't work.
-Kevin
On Aug 13, 2012, at 6:13 AM, David Frascone <d...@frascone.com> wrote:
> Really looks like it's waiting for standard in. Did you try my command?
>
> On Sun, Aug 12, 2012 at 10:43 PM, Kevin Ballard <ke...@sb.org> wrote:
> 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
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> fish: An error occured while reading output from code block
>> read_try: Bad file descriptor
>
> And, weirdly enough, my input line now has [26;94R sitting on it as if I had
> typed that (which I didn't).
>
> -Kevin
>
> On Aug 12, 2012, at 7:41 PM, David Frascone <d...@frascone.com> wrote:
>
>> 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 <ke...@sb.org> wrote:
>> 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 2291 stopped git svn find-rev HEAD
>>
>> What could cause that?
>>
>> -Kevin
>>
>> On Aug 10, 2012, at 9:48 PM, Kevin Ballard <ke...@sb.org> wrote:
>>
>> > Running a git-svn subcommand in a "subshell" (I forget what the real name
>> > is for this) doesn't actually work. For example,
>> >
>> > echo (git svn find-rev HEAD)
>> >
>> > always emits an empty line instead of emitting the revision that HEAD
>> > corresponds to. Running the git-svn command directly at the prompt works
>> > just fine.
>> >
>> > I have no idea what could be causing this. The other git commands that
>> > I've tried work perfectly fine inside of subshells. And git-svn commands
>> > work perfectly fine inside of bash subshells (e.g `echo $(git svn find-rev
>> > HEAD)`).
>> >
>> > Does anyone have an idea what could possibly be going wrong?
>> >
>> > -Kevin
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Fish-users mailing list
>> Fish-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/fish-users
>>
>
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Fish-users mailing list
Fish-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fish-users
