Re: fg call in function: bug?

["Matt Wozniski" <godlygeek@xxxxxxxxx>]

Crap.  I sent this to Bart at first.  My apologies, Bart.

If that were the case, wouldn't you expect to see different output
between "jobs" and "{ jobs }"?

~Matt

On 11/3/06, Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
> On Nov 3,  4:39pm, Matt Wozniski wrote:
> }
> } SpyderByte%   test() { fg %1 }
> } SpyderByte%   test
> } test: can't set tty pgrp: operation not permitted
>
> On Nov 3,  5:15pm, Matt Wozniski wrote:
> } Subject: fg call in function: bug?
> }
> } ~>{ jobs %1 }
> } ~>jobs %1
> } jobs: %1: no such job
>
> I believe both of these are happening because the { } construct creates
> a job table entry, which (in the first case) is attempting to put itself
> into the foreground when it already is, and (in the second case) is
> reporting nothing about itself.