Mercurial > hg > Applications > mh
diff conf/doc/rmm.rf @ 0:bce86c4163a3
Initial revision
author | kono |
---|---|
date | Mon, 18 Apr 2005 23:46:02 +0900 |
parents | |
children | 441a2190cfae |
line wrap: on
line diff
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/conf/doc/rmm.rf Mon Apr 18 23:46:02 2005 +0900 @@ -0,0 +1,59 @@ +.\" @(MHWARNING) +.\" @(#)$Id$ +.SC RMM 1 +.NA +rmm \- remove messages +.SY +rmm +\%[+folder] \%[msgs] +\%[\-help] +.DE +\fIRmm\fR removes the specified messages by renaming the message +files with preceding commas. Many sites consider files that start with a +comma to be a temporary backup, and arrange for \fIcron\fR\0(8) +to remove such files once a day. + +If the user has a profile component such as + + rmmproc: /bin/rm + +then instead of simply renaming the message file, +\fIrmm\fR +will call the named program to delete the file. +Note that at most installations, +\fIcron\fR\0(8) is told to remove files that begin with a comma once a night. + +Some users of csh prefer the following: + + alias rmm 'refile +d' + +where folder +d is a folder for deleted messages, and + + alias mexp 'rm `mhpath +d all`' + +is used to \*(lqexpunge\*(rq deleted messages. + +The current message is not changed by \fIrmm\fR, so a \fInext\fR will +advance to the next message in the folder as expected. +.Fi +^$HOME/\&.mh\(ruprofile~^The user profile +.Pr +^Path:~^To determine the user's MH directory +.Ps +^Current\-Folder:~^To find the default current folder +.Ps +^rmmproc:~^Program to delete the message +.Sa +rmf(1) +.De +`+folder' defaults to the current folder +.Ds +`msgs' defaults to cur +.Co +If a folder is given, it will become the current folder. +.Bu +Since \fIrefile\fR uses your \fIrmmproc\fP to delete the message, +the \fIrmmproc\fP must \fBNOT\fP call \fIrefile\fP without +specifying `\-normmproc', +or you will create an infinte loop. +.En