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

[Zefram <A.Main@dcs.warwick.ac.uk>]

>> 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.
>
>Zefram posted a solution for that which I like quite much.  It is part of my
>releases sine it appeared.  I had to rewrite it for the latest test releases
>and now it is much simpler than the original.  The large patch to zsh.h only
>renumbers the symbols.

Indeed, that's a lot simpler than what I wrote.  Making the Z_* flags
ORable was a good move.

I think this functionality should get into zsh at some point, but I'm
not sure which syntax would be better.  I think nojob is a little
cleaner, but generally these prefixes indicate that the command will
actually be treated differently (cf. noglob, nocorrect).  &! is similar
in effect to &, so the similarity in form is appropriate.  But then
there's coproc...  On the whole I think I favour the &! syntax, partly
on the assumption that someone will implement an option to support the
ksh coprocess syntax (|&).  Then again, how will we do a disowned
coprocess?  (|&! is rather ugly.)

There's one more issue I'd like to resolve concerning this
functionality, which I didn't get working in my patch the way I wanted
it.  I think it actually adds the job to the job table and then deletes
it again, whereas it would be preferable to have the job never entered
into the table at all.  I think my patch is OK w.r.t. keeping %+ and %-
the same, though.

-zefram