Return to sortm.me CVS log

Up to [CSRG BSD Unix] / 43BSD / contrib / mh / doc

Annotation of 43BSD/contrib/mh/doc/sortm.me, revision 1.1

1.1     ! root        1: .\"    This file is automatically generated.  Do not edit!
        !             2: .TH SORTM 1 "April 22, 1986" MH [mh.6]
        !             3: .UC 6
        !             4: .SH NAME
        !             5: sortm \- sort messages
        !             6: .SH SYNOPSIS
        !             7: .in +.5i
        !             8: .ti -.5i
        !             9: sortm
        !            10: \%[+folder] \%[msgs]
        !            11: \%[\-datefield\ field]
        !            12: \%[\-verbose] \%[\-noverbose]
        !            13: \%[\-help]
        !            14: .in -.5i
        !            15: .SH DESCRIPTION
        !            16: \fISortm\fR sorts the specified messages in the named folder according
        !            17: to the chronological order of the \*(lqDate:\*(rq field of each message.
        !            18: Messages which are in the folder, but not specified by `msgs',
        !            19: are moved to the end of the folder.
        !            20: If a message does not exist (the folder has a gap),
        !            21: \fIsortm\fR may fill the gap if convenient.
        !            22: 
        !            23: The `\-verbose' switch directs \fIsortm\fR to tell the user the general
        !            24: actions that it is taking to place the folder in sorted order.
        !            25: 
        !            26: The `\-datefield\ field' switch tells \fIsortm\fR the name of the field
        !            27: to use when making the date comparison.
        !            28: If the user has a special field in each message,
        !            29: such as \*(lqBB\-Posted:\*(rq or \*(lqDelivery\-Date:\*(rq,
        !            30: then the `\-datefield' switch can be used to direct \fIsortm\fR which
        !            31: field to examine.
        !            32: .Fi
        !            33: ^$HOME/\&.mh\(ruprofile~^The user profile
        !            34: .Pr
        !            35: ^Path:~^To determine the user's MH directory
        !            36: .Ps
        !            37: ^Current\-Folder:~^To find the default current folder
        !            38: .Sa
        !            39: folder (1)
        !            40: .De
        !            41: `+folder' defaults to the current folder
        !            42: .Ds
        !            43: `msgs' defaults to all
        !            44: .Ds
        !            45: `\-datefield date'
        !            46: .Ds
        !            47: `\-noverbose'
        !            48: .Co
        !            49: If a folder is given, it will become the current folder.
        !            50: If the current message is moved, \fIsortm\fR will preserve its status
        !            51: as current.
        !            52: .Hi
        !            53: Timezones used to be ignored when comparing dates:
        !            54: they aren't any more.
        !            55: .Bu
        !            56: If \fIsortm\fR encounters a message without a date\-field,
        !            57: or if the message has a date\-field that \fIsortm\fR cannot parse,
        !            58: then \fIsortm\fR attempts to keep the message in the same relative
        !            59: position.
        !            60: This does not always work.
        !            61: For instance, if the first message encountered lacks a date which can be
        !            62: parsed,
        !            63: then it will usually be placed at the end of the messages being sorted.
        !            64: 
        !            65: When \fIsortm\fR complains about a message which it can't temporarlly order,
        !            66: it complains about the message number \fIprior\fR to sorting.
        !            67: It should indicate what the message number will be \fIafter\fR sorting.
        !            68: .En

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.