8 date 92.12.19.00.20.58; author jromine; state Exp;
13 date 92.02.10.20.27.30; author jromine; state Exp;
18 date 92.02.06.00.50.51; author jromine; state Exp;
23 date 92.02.05.20.36.53; author jromine; state Exp;
28 date 91.01.14.16.43.06; author mh; state Exp;
33 date 90.12.18.15.46.28; author mh; state Exp;
38 date 90.12.18.15.27.36; author mh; state Exp;
43 date 90.04.05.15.14.54; author sources; state Exp;
48 date 90.03.22.11.31.45; author sources; state Exp;
53 date 90.03.20.19.42.26; author sources; state Exp;
58 date 90.03.20.17.36.41; author sources; state Exp;
63 date 90.03.20.17.21.25; author sources; state Exp;
78 .\" @@(#)$Id: refile.rf,v 1.11 1992/02/10 20:27:30 jromine Exp jromine $
81 refile \- file message in other folders
86 \%[\-link] \%[\-nolink]
87 \%[\-preserve] \%[\-nopreserve]
90 \%[\-rmmproc program] \%[\-normmproc]
94 \fIRefile\fR moves (\fImv\fR\0(1)) or links (\fIln\fR\0(1)) messages from a
95 source folder into one or more destination folders.
97 of a message as a sheet of paper, this operation is not
98 unlike filing the sheet of paper (or copies) in file cabinet
100 When a message is filed, it is linked into the
101 destination folder(s) if possible, and is copied otherwise.
103 as the destination folders are all on the same file system, multiple filing
104 causes little storage overhead.
105 This facility provides a good way to cross\-file or multiply\-index
107 For example, if a message is received from Jones about
108 the ARPA Map Project, the command
110 refile\0cur\0+jones\0+Map
112 would allow the message to be found in either of the two
113 folders `jones' or `Map'.
115 The option `\-file\ file' directs \fIrefile\fR to use the specified
116 file as the source message to be filed, rather than a message from
118 Note that the file should be a validly formatted message,
119 just like any other \fIMH\fR message.
120 It should \fBNOT\fR be in mail drop format
121 (to convert a file in mail drop format to a folder of \fIMH\fR messages,
124 If a destination folder doesn't exist, \fIrefile\fR will ask if you
126 A negative response will abort the file operation.
127 If the standard input for \fIrefile\fR is \fInot\fR a tty,
128 then \fIrefile\fR will not ask any questions and will proceed as if
129 the user answered \*(lqyes\*(rq to all questions.
131 The option `\-link' preserves the source folder copy of the message
132 (i.e., it does a \fIln\fR(1) rather than a \fImv\fR(1)), whereas,
133 `\-nolink' deletes the filed messages from the source
135 Normally, when a message is filed, it is assigned the
136 next highest number available in each of the destination folders.
137 Use of the `\-preserve' switch will override this message
138 renaming, but name conflicts may occur, so
139 use this switch cautiously.
141 If `\-link' is not specified (or `\-nolink' is specified),
142 the filed messages will be removed from the
143 source folder, by renaming them with a site-dependent prefix (usually
147 If the user has a profile component such as
152 will instead call the named program to delete the message files.
153 The user may specify `\-rmmproc program' on the command line
154 to override this profile specification.
155 The \`-normmproc' option forces
156 the message files to be deleted
157 by renaming them as described above.
159 The `\-draft' switch tells \fIrefile\fR to file the <mh\-dir>/draft.
161 ^$HOME/\&.mh\(ruprofile~^The user profile
163 ^Path:~^To determine the user's MH directory
165 ^Current\-Folder:~^To find the default current folder
167 ^Folder\-Protect:~^To set mode when creating a new folder
169 ^rmmproc:~^Program to delete the message
173 `\-src\ +folder' defaults to the current folder
175 `msgs' defaults to cur
181 If `\-src\ +folder' is given, it will become the
183 If neither `\-link' nor `all' is specified,
184 the current message in the source
185 folder will be set to the last message specified; otherwise, the
186 current message won't be changed.
188 If the Previous\-Sequence profile entry is set,
189 in addition to defining the named sequences from the source folder,
190 \fIrefile\fR will also define those sequences for the destination folders.
191 See \fImh\-sequence\fR\0(5) for information concerning the previous sequence.
193 Since \fIrefile\fR uses your \fIrmmproc\fP to delete the message,
194 the \fIrmmproc\fP must \fBNOT\fP call \fIrefile\fP without
195 specifying `\-normmproc',
196 or you will create an infinte loop.
203 @previous-sequence docs in mh-sequence
208 .\" @@(#)$Id: refile.rf,v 1.10 1992/02/06 00:50:51 jromine Exp jromine $
211 the user's answer was \*(lqyes\*(rq for all questions.
217 @document no prompting when stdin is not a tty
222 .\" @@(#)$Id: refile.rf,v 1.9 1992/02/05 20:36:53 jromine Exp jromine $
225 See \fImh\-profile\fR\0(5) for information concerning the previous sequence.
236 .\" @@(#)$Id: refile.rf,v 1.8 1991/01/14 16:43:06 mh Exp jromine $
243 @document refile -[no]rmmproc
249 .\" @@(#)$Id: refile.rf,v 1.7 90/12/18 15:46:28 mh Exp Locker: mh $
252 See \fImh\-profile\fR\0(1) for information concerning the previous sequence.
263 .\" @@(#)$Id: refile.rf,v 1.6 90/12/18 15:27:36 mh Exp Locker: mh $
267 the filed messages will be removed (\fIunlink\fR\0(2)) from the
269 similar to the way \fImv\fR\0(1) works.
273 then instead of simply renaming the message file,
275 will call the named program to delete the file.
278 the \fIrmmproc\fP must \fBNOT\fP call \fIrefile\fP,
284 @mention not calling refile as rmmproc.
290 .\" @@(#)$Id: refile.rf,v 1.5 90/04/05 15:14:54 sources Exp Locker: mh $
293 Since \fIrefile\fR uses your \*(lqrmmproc\*(rq to delete the message,
294 the \*(lqrmmproc\*(rq must \fBNOT\fP call \fIrefile\fP,
312 @put things back, do .NA stuff another way
326 .TH REFILE 1 @@(MHCENTERFOOT) @@(MHLEFTFOOT)
336 @fixup for makewhatis
341 .TH REFILE 1 [mh.6] MH