Re: bin/41762: at(1) fails to submit job if time has passed

[Robert Elz <kre%munnari.OZ.AU@localhost>]

The following reply was made to PR bin/41762; it has been noted by GNATS.

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: bin/41762: at(1) fails to submit job if time has passed 
Date: Thu, 23 Jul 2009 23:12:07 +0700

 While I certainly expect that the result you show is most likely
 due to a bug in the code, I always regarded it as a feature, not
 a bug.
 
 That is, if at 22:05 I do "at 22:00" there's a fairly good chance that
 I didn't realise that 22:00 had just passed, and intended for the job
 to run today (quite soon), rather than tomorrow (almost 24 hours away).
 
 If I really intended tomorrow, I just say "at 22:00 tomorrow" and it
 works like it should (whether the current time is just before, or
 just after 22:00, or anything else.)
 
 On the other hand, if I ask for a time that's much earlier than the current
 clock time, then it's much more likely that I intended "tomorrow" and having
 it default that way makes sense.
 
 What all this means is that I'd kind of prefer it if this bug was not fixed.
 
 kre