head     1.10;
branch   ;
access   ;
symbols  ;
locks    ; strict;
comment  @@;


1.10
date     91.01.25.15.22.28;  author mh;  state Exp;
branches ;
next     1.9;

1.9
date     91.01.14.16.42.57;  author mh;  state Exp;
branches ;
next     1.8;

1.8
date     90.12.18.15.46.24;  author mh;  state Exp;
branches ;
next     1.7;

1.7
date     90.12.18.15.38.47;  author mh;  state Exp;
branches ;
next     1.6;

1.6
date     90.12.18.15.27.24;  author mh;  state Exp;
branches ;
next     1.5;

1.5
date     90.04.05.15.15.12;  author sources;  state Exp;
branches ;
next     1.4;

1.4
date     90.03.22.11.31.49;  author sources;  state Exp;
branches ;
next     1.3;

1.3
date     90.03.20.19.42.31;  author sources;  state Exp;
branches ;
next     1.2;

1.2
date     90.03.20.17.36.46;  author sources;  state Exp;
branches ;
next     1.1;

1.1
date     90.03.20.17.21.28;  author sources;  state Exp;
branches ;
next     ;


desc
@@


1.10
log
@jlr
@
text
@.\"	@@(MHWARNING)
.\" @@(#)$Id: rmm.rf,v 1.9 91/01/14 16:42:57 mh Exp Locker: mh $
.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
@


1.9
log
@document refile -[no]rmmproc
jlr
@
text
@d2 1
a2 1
.\" @@(#)$Id: rmm.rf,v 1.8 90/12/18 15:46:24 mh Exp Locker: mh $
a53 14
.Hh
If you're not a csh user, and you have an \fIrmmproc\fP script
which \fIrefile\fP\|s messages,
be sure you use something like:

.ti +.5i
mv `mhpath msgs` `mhpath new +folder`

Other work-arounds are possible, such as:

.ti +.5i
cd `mhpath +`
.ti +.5i
MH=/dev/null MHCONTEXT=/dev/null refile $* +folder
@


1.8
log
@jlr
@
text
@d2 1
a2 1
.\" @@(#)$Id: rmm.rf,v 1.7 90/12/18 15:38:47 mh Exp Locker: mh $
d70 2
a71 1
the \fIrmmproc\fP must \fBNOT\fP call \fIrefile\fP,
@


1.7
log
@give tricky example rmmproc
jlr
@
text
@d2 1
a2 1
.\" @@(#)$Id: rmm.rf,v 1.6 90/12/18 15:27:24 mh Exp Locker: mh $
d55 1
a55 1
If you're not a csh user, and you have an \*(lqrmmproc\*(rq script
d69 2
a70 2
Since \fIrefile\fR uses your \*(lqrmmproc\*(rq to delete the message,
the \*(lqrmmproc\*(rq must \fBNOT\fP call \fIrefile\fP,
@


1.6
log
@mention not calling refile as rmmproc.
jlr
@
text
@d2 1
a2 1
.\" @@(#)$Id: rmm.rf,v 1.5 90/04/05 15:15:12 sources Exp Locker: mh $
d61 7
@


1.5
log
@add ID
@
text
@d2 1
a2 1
.\" @@(#)$Id:$
d54 11
@


1.4
log
@put things back, do .NA stuff another way
@
text
@d2 1
@


1.3
log
@typo
@
text
@d2 2
a3 2
.TH RMM 1 @@(MHCENTERFOOT) @@(MHLEFTFOOT)
.SH .NA
d5 1
a5 1
.SH .SY
@


1.2
log
@fixup for makewhatis
@
text
@d2 1
a2 1
.TH RMM 1 [mh.6] MH
@


1.1
log
@Initial revision
@
text
@d2 2
a3 2
.SC RMM 1
.NA
d5 1
a5 1
.SY
@