Re: Using "source" in a function breaks job control

[Bart Schaefer <schaefer@brasslantern.com>]

On Apr 24,  4:25pm, Peter Stephenson wrote:
}
} Apparently a few more verses need adding to the [Elder Edda].

Indeed, now we just have to figure these two out:

torch% vi() { source =(<<<false); vim -u NONE -N; print "vim exited $?" }
torch% vi
zsh: suspended  

Note we don't have the jobtext there.  If there's no "source" then we
get the correct jobtext ("suspended  vi").  There may be one more global
not getting the right treatment in execlist()?  The jobtext as displayed
there comes from the loop over jn->procs in printjob().  Perhaps the
remaining issue is that list_pipe_job isn't restored soon enough.

And then:

torch% fg
[1]  + continued  
vim exited 148
torch% 

As you noted a few messages back, this is the exit status from the signal
stop rather than from the actual exit.