Re: fg call in function: bug?

[Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>]

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.