From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from math.gatech.edu (euclid.skiles.gatech.edu [130.207.146.50]) by werple.net.au (8.7/8.7.1) with SMTP id UAA19784 for ; Wed, 1 Nov 1995 20:21:59 +1100 (EST) Received: by math.gatech.edu (5.x/SMI-SVR4) id AA11342; Wed, 1 Nov 1995 04:14:22 -0500 Old-Return-Path: Resent-Date: Wed, 1 Nov 1995 10:14:20 +0100 Message-Id: <199511010914.AA25609@phys.uva.nl> Old-Return-Path: Date: Wed, 1 Nov 1995 10:14:20 +0100 To: zsh-users@math.gatech.edu In-Reply-To: <199510312213.XAA14119@nu.EMBL-Heidelberg.DE> (message from Rob Hooft on Tue, 31 Oct 1995 23:13:34 +0100) Subject: Re: sched waits for next prompt. Does it have to? From: bas@phys.uva.nl (Bas V. de Bakker) Resent-Message-Id: <"Ot88x3.0.xm2.Nfpbm"@euclid> Resent-From: zsh-users@math.gatech.edu X-Mailing-List: archive/latest/119 X-Loop: zsh-users@math.gatech.edu X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu Rob Hooft writes: > Isn't it possible to call the periodicals from an ALARM function? > If not now, then it should be relatively easy to add such > functionality? That would enable one to make "sched" behave like > "at" using a smart ALARM handler and "TMOUT=60". As I have mentioned before, you could indeed use TMOUT and TRAPALARM to build an at-like function. For "periodic", this is relatively easy, but to make a generic sched thing you would have to maintain some kind of priority queue. If someone would hack together a shell function for this purpose, it would be nice to include it in the distribution. For all my purposes, btw, "at" suffices. Bas.