Re: Interrupting globs (Re: Something rotten in tar completion)

[Bart Schaefer <schaefer@brasslantern.com>]

On Dec 6,  8:45pm, Bart Schaefer wrote:
} 
} } -        /* Commenting this out makes ^C-ing a job started by a function
} } -           stop the whole function again.  But I guess it will stop
} } -           something else from working properly, we have to find out
} } -           what this might be.  --oberon
} } -
} } -        errflag = 0; */
} } +        errflag &= ~ERRFLAG_ERROR;
} } 
} } And commenting that line back out fixes my chpwd() hook ctrl-c thing.
} } (or changing it to errflag &= ~ERRFLAG_INT; but I have no idea if that
} } makes any sense).
} 
} Both things fit with Oberon's comment, actually.  Based on the comment,
} what we do NOT want to do there is clear ERRFLAG_INT.

Wait ... I think I have something backward there.

errflag &= ~ERRFLAG_ERROR should leave ERRFLAG_INT unaffected, which is
what seems to be wanted.  So if ~ERRFLAG_INT (or no change at all) works,
then the important value of errflag there *is* ERRFLAG_ERR.

Which means something changed errflag from ERRFLAG_INT to ERRFLAG_ERR ?
But that doesn't make sense, looking at the patch.

OK, now I'm just confused.  Sorry.