|
|
1.1 root 1: .\" @(MHWARNING)
2: .TH RMM 1 "April 22, 1986" MH [mh.6]
3: .UC 6
4: .SH NAME
5: rmm \- remove messages
6: .SH SYNOPSIS
7: .in +.5i
8: .ti -.5i
9: rmm
10: \%[+folder] \%[msgs]
11: \%[\-help]
12: .in -.5i
13: .SH DESCRIPTION
14: \fIRmm\fR removes the specified messages by renaming the message
15: files with preceding commas. Many sites consider files that start with a
16: comma to be a temporary backup, and arrange for \fIcron\fR\0(8)
17: to remove such files once a day.
18:
19: If the user has a profile component such as
20:
21: rmmproc: /bin/rm
22:
23: then instead of simply renaming the message file,
24: \fIrmm\fR
25: will call the named program to delete the file.
26: Note that at most installations,
27: \fIcron\fR\0(8) is told to remove files that begin with a comma once a night.
28:
29: Some users of csh prefer the following:
30:
31: alias rmm 'refile +d'
32:
33: where folder +d is a folder for deleted messages, and
34:
35: alias mexp 'rm `mhpath +d all`'
36:
37: is used to \*(lqexpunge\*(rq deleted messages.
38:
39: The current message is not changed by \fIrmm\fR, so a \fInext\fR will
40: advance to the next message in the folder as expected.
41: .Fi
42: ^$HOME/\&.mh\(ruprofile~^The user profile
43: .Pr
44: ^Path:~^To determine the user's MH directory
45: .Ps
46: ^Current\-Folder:~^To find the default current folder
47: .Ps
48: ^rmmproc:~^Program to delete the message
49: .Sa
50: rmf(1)
51: .De
52: `+folder' defaults to the current folder
53: .Ds
54: `msgs' defaults to cur
55: .Co
56: If a folder is given, it will become the current folder.
57: .En
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.