felixfoertsch/remind
1
0
Fork 0
mirror of https://salsa.debian.org/dskoll/remind.git synced 2026-04-16 06:18:47 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity

-- Updated man pages.

Browse Source
This commit is contained in:
dfs
1998-05-06 01:47:41 +00:00
parent 65f62d6012
commit e12462630e
2 changed files with 31 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
man/remind.1
View File

@@ -1,4 +1,4 @@
.\" $Id: remind.1,v 1.7 1998-04-29 02:50:24 dfs Exp $
.\" $Id: remind.1,v 1.8 1998-05-06 01:47:41 dfs Exp $
.TH REMIND 1 "1 February 1998"
.UC 4
.SH NAME
@@ -827,10 +827,14 @@ expressions and user-defined functions are explained. See the subsection
.PP
.B TAG AND DURATION
.PP
The \fBTAG\fR keyword lets you "tag" certain reminders. Currently,
this facility is not used, but it may be used by certain back-ends
or systems built around \fBRemind\fR. The \fBTAG\fR keyword should
be followed by a tag consisting of up to 32 characters.
The \fBTAG\fR keyword lets you "tag" certain reminders. This facility
is used by certain back-ends or systems built around \fBRemind\fR,
such as \fBTkRemind\fR. These back-ends have specific rules about
tags; you should \fInot\fR use the \fBTAG\fR keyword yourself, or
your script will interact badly with back-ends.
.PP
The \fBTAG\fR keyword is followed by a tag consisting of up to
32 characters.
.PP
The \fBDURATION\fR keyword makes sense only for timed reminders;
it specifies the duration of an event. Currently, this is not

25
man/tkremind.1
View File

@@ -1,4 +1,4 @@
.\" $Id: tkremind.1,v 1.4 1998-05-05 03:16:25 dfs Exp $ "
.\" $Id: tkremind.1,v 1.5 1998-05-06 01:47:42 dfs Exp $ "
.TH TKREMIND 1 "15 February 1998"
.UC 4
.SH NAME
@@ -209,12 +209,12 @@ preview a reminder. However, if you edit a reminder in the previewer,
\fBTkRemind\fR does \fInot\fR check the edited reminder. You can
produce illegal reminders which may cause problems. (This is one good
reason to isolate \fBTkRemind\fR's reminders in a separate file.)
.PP
\fBTkRemind\fR does \fInot\fR check the body of the reminder in any
way. You can use the normal \fBRemind\fR substitution sequences in
the body. Furthermore, if you use expression-pasting in the body,
\fBTkRemind\fR does \fInot\fR validate the expressions.
.PP
When \fBTkRemind\fR invokes \fBRemind\fR, it supplies the option:
.PP
.nf
@@ -231,6 +231,25 @@ on the command line. So, in your \fBRemind\fR file, you can include:
.PP
You can use this to activate certain reminders in different ways
for \fBTkRemind\fR (for example).
.PP
\fBTkRemind\fR uses tags to keep track of reminders in the
script file. It also places special comments in the reminder
file to store additional state. You can certainly mix
"hand-crafted" reminders with reminders created by \fBTkRemind\fR
if you are awared of the following rules and limitations:
.TP
o
Do not use the \fBTAG\fR keyword in hand-crafted reminders.
.TP
o
Do not edit lines starting with "# TKTAGnnn", "# TKEND", or any
lines in between. You can move such lines, but be careful to move
them as a single block.
.TP
o
Hand-crafted reminders cannot be edited with \fBTkRemind\fR, and
for hand-crafted timed reminders, you will not be presented with
the "Don't remind me again" option when they pop up.
.SH SERVER MODE