1 .\" This file is automatically generated. Do not edit!
2 .\" include the -mh macro file
3 .so /usr/local/lib/mh/tmac.h
4 .\" This file is automatically generated. Do not edit!
7 sortf, sorts \- sort messages by fields that do not contain dates
10 \%[-verbose] \%[-noverbose]
16 \%[-verbose] \%[-noverbose]
20 \fISortf\fR sorts the specified messages in the named
21 folder according to the alphabetical order of the
22 \*(lqFrom:\*(rq field or the \*(lqTo:\*(rq field of each
23 message, depending on whether the message is incoming or
24 outgoing, repectively.
26 \fISorts\fR sorts the specified messages in the named
27 folder according to the alphabetical order of the
28 \*(lqSubject:\*(rq of each message.
30 The messages are remapped onto the same set of message
31 numbers that they originally occupied, so if you only have
32 messages numbered 27, 38, and 192 in the selected folder
33 before the sort, that's what you'll have afterwards too.
34 Thus messages which are in the folder, but not specified by
35 `msgs', are left in place, and if a message does not exist
36 (the folder has a gap), \fIsortf\fR and \fIsortf\fR will
39 The `\-verbose' switch directs \fIsortf\fR and \fIsorts\fR
40 to tell the user the general actions that they are taking
41 to place the folder in sorted order.
43 The `\-nofold' switch makes the sort case-sensitive.
45 ^$HOME/\&.mh\(ruprofile~^The user profile
47 ^Path:~^To determine the user's MH directory
49 ^Current\-Folder:~^To find the default current folder
51 folder (1), scan (1), sortm (1)
53 `+folder' defaults to the current folder
55 `msgs' defaults to all
61 If a folder is given, it will become the current folder.
62 If the current message is moved, \fIsortf\fR and
63 \fIsorts\fR will not preserve its status as current.
65 \fIsortf\fR and \fIsorts\fR are rather slow, especially if
66 you really do receive 200 mail messages a day.
68 \fIsortf\fR and \fIsorts\fR create a temporary folder named
69 MaIlSoRt\fInnnn\fR, where \fInnnn\fR is a numeral, under
70 the folder in which you're sorting. If a file with this
71 name already exists, \fIsortf\fR or \fIsorts\fR will fail.
73 Interrupt handling is really terrible (nonexistent).
74 If an interrupt is encountered, such as a BREAK or a system crash,
75 some or all of the messages will be left
76 in the temporary subfolder.
78 \fIsortf\fR's and \fIsorts\fR's behaviors are inconsistent
79 with \fIsortm\fR's when sorting a folder with gaps between
80 the messages or when sorting a noncontiguous set of