From 86945c6e1837b96ff0b1ded16073bee30d264196 Mon Sep 17 00:00:00 2001 From: Dianne Skoll Date: Thu, 29 Aug 2024 08:39:55 -0400 Subject: [PATCH] Remove incorrect test obsoleted by changes in 05.00.04. --- man/remind.1.in | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/man/remind.1.in b/man/remind.1.in index 8716da78..816fd192 100644 --- a/man/remind.1.in +++ b/man/remind.1.in @@ -4706,10 +4706,7 @@ This is really useful only if \fIexpr\fR involves a call to the \fIexpr\fR will not change as \fBRemind\fR iterates. In fact, if \fIexpr\fR is not a constant and does not call \fBtrigdate()\fR or related functions or system variables, then \fBRemind\fR will issue a -warning. If you have a user-defined function that calls -\fBtrigdate()\fR, this can result in an unwanted warning. In that -case, pass \fBtrigdate()\fR or some related function or system -variable into your user-defined function from the SATISFY expression. +warning. .PP An example of the usefulness of \fBSATISFY\fR: Suppose you wish to be warned of every Friday the 13th. Your first attempt may be: