And of course, bring them to the foreground when you attach.
See FIXME in the code.
I think the general strategy here is:
- Some code in
beam-init to forward the process group, at the moment a beamctl client request a file descriptor for it
- After
fn attach() exits, it right now uses the /show endpoint to retrieve the new status of the process. That could be turned into a /background endpoint that gives the same info as /show but also puts the process group back into the background.
And of course, bring them to the foreground when you attach.
See FIXME in the code.
I think the general strategy here is:
beam-initto forward the process group, at the moment a beamctl client request a file descriptor for itfn attach()exits, it right now uses the /show endpoint to retrieve the new status of the process. That could be turned into a/backgroundendpoint that gives the same info as /show but also puts the process group back into the background.