mirror of
https://salsa.debian.org/dskoll/remind.git
synced 2026-04-17 23:08:40 +02:00
Document DO
This commit is contained in:
@@ -2,6 +2,16 @@ CHANGES TO REMIND
|
|||||||
|
|
||||||
* VERSION 3.3 Patch 12 - 2021-??-??
|
* VERSION 3.3 Patch 12 - 2021-??-??
|
||||||
|
|
||||||
|
- NEW FEATURE: Add a DO command. This is just like INCLUDE, but relative
|
||||||
|
paths are interpreted relative to the directory containing the current
|
||||||
|
file. That is:
|
||||||
|
|
||||||
|
DO somefile.rem
|
||||||
|
|
||||||
|
is equivalent to:
|
||||||
|
|
||||||
|
INCLUDE [filedir()]/somefile.rem
|
||||||
|
|
||||||
- NEW FEATURE: Add the $DefaultTDelta system variable and associated
|
- NEW FEATURE: Add the $DefaultTDelta system variable and associated
|
||||||
-tt[N] command-line option to set a default time delta for timed
|
-tt[N] command-line option to set a default time delta for timed
|
||||||
reminder without an explicit +N delta.
|
reminder without an explicit +N delta.
|
||||||
|
|||||||
25
man/remind.1
25
man/remind.1
@@ -1551,7 +1551,7 @@ the first day of the month. The local \fBOMIT\fR keyword causes the
|
|||||||
Finally, the \fBAFTER\fR keyword will keep moving the reminder forward
|
Finally, the \fBAFTER\fR keyword will keep moving the reminder forward
|
||||||
until it has passed any holidays specified with global \fBOMIT\fR
|
until it has passed any holidays specified with global \fBOMIT\fR
|
||||||
commands.
|
commands.
|
||||||
.SH THE INCLUDE COMMAND
|
.SH THE DO AND INCLUDE COMMANDS
|
||||||
.PP
|
.PP
|
||||||
\fBRemind\fR allows you to include other files in your reminder script,
|
\fBRemind\fR allows you to include other files in your reminder script,
|
||||||
similar to the C preprocessor #include directive. For example, your
|
similar to the C preprocessor #include directive. For example, your
|
||||||
@@ -1575,7 +1575,26 @@ If you specify a \fIdirectory\fR as the argument to \fBINCLUDE\fR, then
|
|||||||
\fBRemind\fR will process all files in that directory that match the shell
|
\fBRemind\fR will process all files in that directory that match the shell
|
||||||
patterm "*.rem". The files are processed in sorted order; the sort order
|
patterm "*.rem". The files are processed in sorted order; the sort order
|
||||||
matches that used by the shell when it expands "*.rem".
|
matches that used by the shell when it expands "*.rem".
|
||||||
|
.PP
|
||||||
|
Note that the file specified by an \fBINCLUDE\fR command is interpreted
|
||||||
|
relative to the \fIcurrent working directory of the Remind process\fR.
|
||||||
|
If you want to include a file relative to the directory containing the
|
||||||
|
currently-processing file, use \fBDO\fR instead. For example,
|
||||||
|
if the current file is \fB/home/user/.reminders/foo.rem\fR and Remind's
|
||||||
|
working directory is \fB/home/user\fR, then:
|
||||||
|
.PP
|
||||||
|
.nf
|
||||||
|
# Read /home/user/.reminders/bar.rem
|
||||||
|
DO bar.rem
|
||||||
|
|
||||||
|
# Read /home/user/bar.rem
|
||||||
|
INCLUDE bar.rem
|
||||||
|
.fi
|
||||||
|
.PP
|
||||||
|
Arguably, the \fBINCLUDE\fR command should have worked the way \fBDO\fR
|
||||||
|
does right from the start, but changing it would have broken
|
||||||
|
backward-compatibility, hence the introduction of \fBDO\fR.
|
||||||
|
.PP
|
||||||
.SH THE RUN COMMAND
|
.SH THE RUN COMMAND
|
||||||
.PP
|
.PP
|
||||||
If you include other files in your reminder script, you may not always
|
If you include other files in your reminder script, you may not always
|
||||||
@@ -2630,7 +2649,9 @@ follows:
|
|||||||
.PP
|
.PP
|
||||||
.RS
|
.RS
|
||||||
This includes the file "stuff" in the same directory as the
|
This includes the file "stuff" in the same directory as the
|
||||||
current file being processed.
|
current file being processed. Note that this workaround is
|
||||||
|
no longer necessary because \fBDO stuff\fR will achieve the
|
||||||
|
same goal.
|
||||||
.RE
|
.RE
|
||||||
.TP
|
.TP
|
||||||
.B filename()
|
.B filename()
|
||||||
|
|||||||
Reference in New Issue
Block a user