From: Rob Hooft <Rob.Hooft@EMBL-Heidelberg.de>
To: Richard Coleman <coleman@math.gatech.edu>
Cc: hware@a.cs.wvu.edu (Henry Ware), zsh-users@math.gatech.edu
Subject: Re: sched waits for next prompt. Does it have to?
Date: Tue, 31 Oct 1995 23:13:34 +0100 [thread overview]
Message-ID: <199510312213.XAA14119@nu.EMBL-Heidelberg.DE> (raw)
In-Reply-To: <199510311902.OAA11276@redwood.skiles.gatech.edu>
>>>>> "RC" == Richard Coleman <coleman@math.gatech.edu> writes:
>> ... I'm having a little
>> trouble with the sched commend. I'd like it to perform the action
>> at the specified time rather than at the next prompt: for example,
>> when I want it to act as an alarm clock, or as "at", etc.
RC> Currently zsh's handling of `sched' and the shell function
RC> `periodic' (if defined) are very simple. Zsh just checks time
RC> stamps in the function preprompt() and executes scheduled
RC> commands or `periodic' if it has been long enough. To do
RC> anything better would require setting up signals, etc...
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".
Rob.
--
Rob W. W. Hooft ====== You have a computational protein problem? Try WHAT IF!
= Rob.Hooft@EMBL-Heidelberg.DE, Meyerhofstr. 1, 69117 Heidelberg, Germany. ==
3.0GS$ d-(?) s: a28 C++ UAIOS++(-) UL++++ P++ L++(+++) E++ W++(-) N++(+++) K?
w-- O? M-(--) V(-) PS PE+ Y+ PGP t 5? X+ R tv+ b+ DI? D+ G+ e++++ h(*) !r !y+
next prev parent reply other threads:[~1995-10-31 22:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-10-31 14:42 Henry Ware
1995-10-31 19:02 ` Richard Coleman
1995-10-31 22:13 ` Rob Hooft [this message]
1995-11-01 9:14 ` Bas V. de Bakker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199510312213.XAA14119@nu.EMBL-Heidelberg.DE \
--to=rob.hooft@embl-heidelberg.de \
--cc=coleman@math.gatech.edu \
--cc=hware@a.cs.wvu.edu \
--cc=zsh-users@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).