Re: after ids
- From: Alexandre Ferrieux <alexandre.ferrieux@xxxxxxxxx>
- Date: Fri, 4 Jul 2008 00:15:55 -0700 (PDT)
On Jul 4, 7:33 am, Fredderic <my-name-h...@xxxxxxxxxx> wrote:
On Fri, 18 Apr 2008 12:35:58 -0400, Kevin Kenny wrote:
This is a ***-old thread, I know, for some reason a few messages
accidentally got marked as unread, so I've ended up reading it over
again... But something just jumped out at me...
(1) this is closer in my view to an [at] command, rather than anIndeed, and I'm all in favour of implementing [at] - just haven't
[after]
had the time to do it myself (and it *does* need a TIP).
Would [clock alarm] make sense, rather than adding a new [at] command?
Its placement as a sub-command of [clock] also points directly at the
fact that this command is based on wall-clock time, rather than elapsed
time.
An alias is always possible of course, but keep in mind that this wall-
clock semantics has been attached to [after] since the beginning, so
it must stay that way. So you also should invent a nice name for the
new, truly relative timers...
-Alex
.
- Follow-Ups:
- Re: after ids
- From: Donald Arseneau
- Re: after ids
- From: Andreas Leitgeb
- Re: after ids
- References:
- Re: after ids
- From: Fredderic
- Re: after ids
- Prev by Date: Re: Events on Serial port
- Next by Date: Ann: kbs 0.2.3
- Previous by thread: Re: after ids
- Next by thread: Re: after ids
- Index(es):