Re: Background jobs with no job control / disown bug?

[Richard Coleman <coleman@xxxxxxxxxxxxxxx>]

> It occurred to me that one way of avoiding a background job getting
> job control (disown is not a sufficient method in a function) is to
> unsetopt MONITOR, spawn the job, then setopt MONITOR again.  This
> nearly works.  Unfortunately,
> 
> % unsetopt monitor
> % sleep 30 &
> % setopt monitor
> % jobs
> [1] + running

I had thought that adding a new pre-command `nojob' would be
a good idea.  But to do this right would probably require some
work.

I was thinking that this and `noalias' would both be good ideas.
I havn't looked at how to implement them yet.

rc