Return to refile.me CVS log

Up to [CSRG BSD Unix] / 43BSDReno / share / doc / usd / 08.mh

Annotation of 43BSDReno/share/doc/usd/08.mh/refile.me, revision 1.1

1.1     ! root        1: .\"    This file is automatically generated.  Do not edit!
        !             2: .SC REFILE 1
        !             3: .NA
        !             4: refile \- file message in other folders
        !             5: .SY
        !             6: refile 
        !             7: \%[msgs] 
        !             8: \%[\-draft]
        !             9: \%[\-link] \%[\-nolink] 
        !            10: \%[\-preserve] \%[\-nopreserve]
        !            11: \%[\-src\ +folder] 
        !            12: \%[\-file\ file] 
        !            13: +folder ...
        !            14: \%[\-help]
        !            15: .DE
        !            16: \fIRefile\fR moves (\fImv\fR\0(1)) or links (\fIln\fR\0(1)) messages from a
        !            17: source folder into one or more destination folders.
        !            18: If you think
        !            19: of a message as a sheet of paper, this operation is not
        !            20: unlike filing the sheet of paper (or copies) in file cabinet
        !            21: folders.
        !            22: When a message is filed, it is linked into the
        !            23: destination folder(s) if possible, and is copied otherwise.
        !            24: As long
        !            25: as the destination folders are all on the same file system, multiple filing
        !            26: causes little storage overhead.
        !            27: This facility provides a good way to cross\-file or multiply\-index
        !            28: messages.
        !            29: For example, if a message is received from Jones about
        !            30: the ARPA Map Project, the command
        !            31: 
        !            32:      refile\0cur\0+jones\0+Map
        !            33: 
        !            34: would allow the message to be found in either of the two
        !            35: folders `jones' or `Map'.
        !            36: 
        !            37: The option `\-file\ file' directs \fIrefile\fR to use the specified
        !            38: file as the source message to be filed, rather than a message from
        !            39: a folder.
        !            40: Note that the file should be a validly formatted message,
        !            41: just like any other \fIMH\fR message.
        !            42: It should \fBNOT\fR be in mail drop format
        !            43: (to convert a file in mail drop format to a folder of \fIMH\fR messages,
        !            44: see \fIinc\fR\0(1)).
        !            45: 
        !            46: If a destination folder doesn't exist, \fIrefile\fR will ask if you
        !            47: want to create it.
        !            48: A negative response will abort the file operation.
        !            49: 
        !            50: The option `\-link' preserves the source folder copy of the message
        !            51: (i.e., it does a \fIln\fR(1) rather than a \fImv\fR(1)), whereas,
        !            52: `\-nolink' deletes the filed messages from the source
        !            53: folder.
        !            54: Normally, when a message is filed, it is assigned the
        !            55: next highest number available in each of the destination folders.
        !            56: Use of the `\-preserve' switch will override this message
        !            57: renaming, but name conflicts may occur, so
        !            58: use this switch cautiously.
        !            59: 
        !            60: If `\-link' is not specified (or `\-nolink' is specified),
        !            61: the filed messages will be removed (\fIunlink\fR\0(2)) from the
        !            62: source folder,
        !            63: similar to the way \fImv\fR\0(1) works.
        !            64: 
        !            65: If the user has a profile component such as
        !            66: 
        !            67:        rmmproc:        /bin/rm
        !            68: 
        !            69: then instead of simply renaming the message file,
        !            70: \fIrefile\fR
        !            71: will call the named program to delete the file.
        !            72: 
        !            73: The `\-draft' switch tells \fIrefile\fR to file the <mh\-dir>/draft.
        !            74: .Fi
        !            75: ^$HOME/\&.mh\(ruprofile~^The user profile
        !            76: .Pr
        !            77: ^Path:~^To determine the user's MH directory
        !            78: .Ps
        !            79: ^Current\-Folder:~^To find the default current folder
        !            80: .Ps
        !            81: ^Folder\-Protect:~^To set mode when creating a new folder
        !            82: .Ps
        !            83: ^rmmproc:~^Program to delete the message
        !            84: .Sa
        !            85: folder(1)
        !            86: .De
        !            87: `\-src\ +folder' defaults to the current folder
        !            88: .Ds
        !            89: `msgs' defaults to cur
        !            90: .Ds
        !            91: `\-nolink'
        !            92: .Ds
        !            93: `\-nopreserve'
        !            94: .Co
        !            95: If `\-src\ +folder' is given, it will become the
        !            96: current folder.
        !            97: If neither `\-link' nor `all' is specified,
        !            98: the current message in the source
        !            99: folder will be set to the last message specified; otherwise, the
        !           100: current message won't be changed.
        !           101: 
        !           102: If the Previous\-Sequence profile entry is set,
        !           103: in addition to defining the named sequences from the source folder,
        !           104: \fIrefile\fR will also define those sequences for the destination folders.
        !           105: See \fImh\-profile\fR\0(1) for information concerning the previous sequence.
        !           106: .En

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