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