Autoresume bug

[P.Stephenson@xxxxxxxxxxxxx]

I keep thinking I'm not going to make any more patches for a bit, then
another bug crops up...

With autoresume set, start a background job with `w', e.g.

% while true; do sleep 60; done &
[1] 20550

then try to execute the command w.  It will resume the previous
command.  Arguably this is correct (though I'd much prefer autoresume
to require an exact match on the first word and I'd like to hear other
opinions).

What's definitely wrong, though, is that `command w' (or `exec w' or
`noglob w' ...) do an autoresume as well.  This fixes that.  Yes, the
test is grotesque.

*** Src/exec.c~	Tue Jul  4 12:16:28 1995
--- Src/exec.c	Fri Jul  7 15:25:55 1995
***************
*** 1086,1092 ****
  	bkg = 0;
      }
      if (isset(AUTORESUME) && !bkg && empty(cmd->redir) && full(args) &&
! 	!input && type == SIMPLE && !nextnode(firstnode(args))) {
  	if (unset(NOTIFY))
  	    scanjobs();
  	if (findjobnam(peekfirst(args)) != -1)
--- 1086,1093 ----
  	bkg = 0;
      }
      if (isset(AUTORESUME) && !bkg && empty(cmd->redir) && full(args) &&
! 	!input && type == SIMPLE && !nextnode(firstnode(args)) &&
! 	!cmd->flags) {
  	if (unset(NOTIFY))
  	    scanjobs();
  	if (findjobnam(peekfirst(args)) != -1)

-- 
Peter Stephenson <P.Stephenson@xxxxxxxxxxxxx>  Tel: +44 1792 205678 extn. 4461
WWW:  http://python.swan.ac.uk/~pypeters/      Fax: +44 1792 295324
Department of Physics, University of Wales, Swansea,
Singleton Park, Swansea, SA2 8PP, U.K.