[Remind-Fans] Can't compute trigdate for bridging days
Jens Mueller
jens.k.mueller at gmx.de
Sat Sep 26 16:05:39 EDT 2020
Dianne Skoll via Remind-fans wrote:
> Hi, again...
>
> On 2020-09-25 20:05, Dianne Skoll via Remind-fans wrote:
> > On 2020-09-25 19:53, Jens Mueller wrote:
>
> >> rem mon SKIP SATISFY [isomitted(trigdate()+1)] msg Bridging day
> >> rem fri SKIP SATISFY [isomitted(trigdate()-1)] msg Bridging day
>
> > One reason it can fail is if there are no omitted days around today
> > or at any point in the future. Try this:
>
> The more I thought about it, the more I thought it *should* be possible to
> do this in Remind and tell it you don't care about uncomputable triggers.
>
> So I added a keyword MAYBE-UNCOMPUTABLE. That tells Remind that this
> specific reminder may never be satisfied, and if it isn't, to continue
> without error (and without triggering the reminder.) The latest git
> master HEAD at https://dianne.skoll.ca/projects/remind/git/Remind.git/
> has this keyword; read the man page for details.
>
> In this particular case:
>
> rem MAYBE-UNCOMPUTABLE Mon SKIP SATISFY [isomitted(trigdate()+1)] msg Bridging day
> rem MAYBE-UNCOMPUTABLE Fri SKIP SATISFY [isomitted(trigdate()-1)] msg Bridging day
>
> work as expected.
Looks reasonable. I was surprised to see that my old way of computing
bridging days reported errors after upgrading. I added the above lines
as comments for now to include them once I install a new version of
remind.
Thank you.
Jens
More information about the Remind-fans
mailing list