10 date 91.01.25.15.22.28; author mh; state Exp;
15 date 91.01.14.16.42.57; author mh; state Exp;
20 date 90.12.18.15.46.24; author mh; state Exp;
25 date 90.12.18.15.38.47; author mh; state Exp;
30 date 90.12.18.15.27.24; author mh; state Exp;
35 date 90.04.05.15.15.12; author sources; state Exp;
40 date 90.03.22.11.31.49; author sources; state Exp;
45 date 90.03.20.19.42.31; author sources; state Exp;
50 date 90.03.20.17.36.46; author sources; state Exp;
55 date 90.03.20.17.21.28; author sources; state Exp;
70 .\" @@(#)$Id: rmm.rf,v 1.9 91/01/14 16:42:57 mh Exp Locker: mh $
73 rmm \- remove messages
79 \fIRmm\fR removes the specified messages by renaming the message
80 files with preceding commas. Many sites consider files that start with a
81 comma to be a temporary backup, and arrange for \fIcron\fR\0(8)
82 to remove such files once a day.
84 If the user has a profile component such as
88 then instead of simply renaming the message file,
90 will call the named program to delete the file.
91 Note that at most installations,
92 \fIcron\fR\0(8) is told to remove files that begin with a comma once a night.
94 Some users of csh prefer the following:
98 where folder +d is a folder for deleted messages, and
100 alias mexp 'rm `mhpath +d all`'
102 is used to \*(lqexpunge\*(rq deleted messages.
104 The current message is not changed by \fIrmm\fR, so a \fInext\fR will
105 advance to the next message in the folder as expected.
107 ^$HOME/\&.mh\(ruprofile~^The user profile
109 ^Path:~^To determine the user's MH directory
111 ^Current\-Folder:~^To find the default current folder
113 ^rmmproc:~^Program to delete the message
117 `+folder' defaults to the current folder
119 `msgs' defaults to cur
121 If a folder is given, it will become the current folder.
123 Since \fIrefile\fR uses your \fIrmmproc\fP to delete the message,
124 the \fIrmmproc\fP must \fBNOT\fP call \fIrefile\fP without
125 specifying `\-normmproc',
126 or you will create an infinte loop.
133 @document refile -[no]rmmproc
139 .\" @@(#)$Id: rmm.rf,v 1.8 90/12/18 15:46:24 mh Exp Locker: mh $
142 If you're not a csh user, and you have an \fIrmmproc\fP script
143 which \fIrefile\fP\|s messages,
144 be sure you use something like:
147 mv `mhpath msgs` `mhpath new +folder`
149 Other work-arounds are possible, such as:
154 MH=/dev/null MHCONTEXT=/dev/null refile $* +folder
165 .\" @@(#)$Id: rmm.rf,v 1.7 90/12/18 15:38:47 mh Exp Locker: mh $
168 the \fIrmmproc\fP must \fBNOT\fP call \fIrefile\fP,
174 @give tricky example rmmproc
180 .\" @@(#)$Id: rmm.rf,v 1.6 90/12/18 15:27:24 mh Exp Locker: mh $
183 If you're not a csh user, and you have an \*(lqrmmproc\*(rq script
186 Since \fIrefile\fR uses your \*(lqrmmproc\*(rq to delete the message,
187 the \*(lqrmmproc\*(rq must \fBNOT\fP call \fIrefile\fP,
193 @mention not calling refile as rmmproc.
199 .\" @@(#)$Id: rmm.rf,v 1.5 90/04/05 15:15:12 sources Exp Locker: mh $
218 @put things back, do .NA stuff another way
232 .TH RMM 1 @@(MHCENTERFOOT) @@(MHLEFTFOOT)
242 @fixup for makewhatis