felixfoertsch/remind
1
0
Fork 0
mirror of https://salsa.debian.org/dskoll/remind.git synced 2026-04-17 23:08:40 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity

Clearify how $DedupeReminders works.
Some checks failed
Remind unit tests / tests (push) Failing after 28s
Details

Browse Source
This commit is contained in:
Dianne Skoll
2024-11-12 09:32:11 -05:00
parent e0fde98410
commit 5b892eba8e
1 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
man/remind.1.in
View File

@@ -2529,6 +2529,7 @@ not suppress duplicate reminders.
.RS .RS
.PP .PP
As an example, consider the following reminder file: As an example, consider the following reminder file:
.PP
.nf .nf
SET $DedupeReminders 1 SET $DedupeReminders 1
REM Wednesday MSG Phooey REM Wednesday MSG Phooey
@@ -2538,6 +2539,19 @@ As an example, consider the following reminder file:
On Wednesday, 20 November 2024, only \fIone\fR "Phooey" will be issued. On Wednesday, 20 November 2024, only \fIone\fR "Phooey" will be issued.
In December of 2024, "Phooey" will be issued every Wednesday as well In December of 2024, "Phooey" will be issued every Wednesday as well
as on Friday, 20 December 2024 as on Friday, 20 December 2024
.PP
If you set $DedupeReminders to 0, then \fBRemind\fR does not even track
reminders to detect duplicates. Consider the following example:
.PP
.nf
SET $DedupeReminders 0
REM Wednesday MSG Hello
SET $DedupeReminders 1
REM Wednesday MSG Hello
.PP
Every Wednesday, \fBRemind\fR will issue \fItwo\fR "Hello" reminders.
Because $DedupeReminders was 0 when the first "Hello" was issued, it
won't be tracked for potential duplicates.
.RE .RE
.TP .TP
.B $DefaultColor .B $DefaultColor