5 .TH REFILE %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
7 refile \- file message in other folders
14 .RB [ \-link " | " \-nolink ]
15 .RB [ \-preserve " | " \-nopreserve ]
16 .RB [ \-unlink " | " \-nounlink ]
36 from a source folder into one or more destination folders.
38 If you think of a message as a sheet of paper, this operation is not
39 unlike filing the sheet of paper (or copies) in file cabinet folders.
40 When a message is filed, it is linked into the destination folder(s)
41 if possible, and is copied otherwise. As long as the destination
42 folders are all on the same file system, multiple filing causes little
43 storage overhead. This facility provides a good way to cross\-file or
44 multiply\-index messages. For example, if a message is received from
45 Jones about the ARPA Map Project, the command
48 refile\0cur\0+jones\0+Map
51 would allow the message to be found in either of the two folders `jones'
54 You may specify the source folder using
58 not given, the current folder is used by default. If no message is
59 specified, then `cur' is used by default.
66 to use the specified file
67 as the source message to be filed, rather than a message from a folder.
68 Note that the file should be a validly formatted message, just like
73 be in mail drop format
74 (to convert a file in mail drop format to a folder of
80 If a destination folder doesn't exist,
83 to create it. A negative response will abort the file operation. If the
90 will not ask any questions and will proceed as if the user answered
91 \*(lqyes\*(rq to all questions.
95 preserves the source folder copy of the message (i.e.,
102 (the default) deletes the filed messages from the source folder.
104 Normally when a message is refiled, for each destination folder it
105 is assigned the number which is one above the current highest message
106 number in that folder. Use of the
109 this message renaming, and try to preserve the number of the message.
110 If a conflict for a particular folder occurs when using the
114 will use the next available message number
115 which is above the message number you wish to preserve.
121 is specified), the filed
122 messages will be removed from the source folder. The default is to
123 remove these messages by renaming them with a site-dependent prefix
124 (usually a comma). Such files will then need to be removed in some
125 manner after a certain amount of time. Many sites arrange for
127 to remove these files once a day, so check with your
128 system administrator.
130 Alternately, if you wish for
132 to really remove the files
133 representing these messages from the source folder, you can use the
135 switch (not to be confused with the
138 messages removed by this method cannot be later recovered.
140 If you prefer a more sophisticated method of `removing' the messages
141 from the source folder, you can define the
144 component. For example, you can add a profile component such as
147 rmmproc: /home/coleman/bin/rmm_msgs
152 will instead call the named program or script to
153 handle the message files.
158 on the command line to
159 override this profile specification. The
162 the message files to be deleted by renaming or unlinking them as
169 to file the <mh\-dir>/draft.
174 .ta \w'%etcdir%/ExtraBigFileName 'u
175 ^$HOME/\&.mh\(ruprofile~^The user profile
178 .SH "PROFILE COMPONENTS"
182 .ta \w'ExtraBigProfileName 'u
183 ^Path:~^To determine the user's nmh directory
184 ^Current\-Folder:~^To find the default current folder
185 ^Folder\-Protect:~^To set mode when creating a new folder
186 ^rmmproc:~^Program to delete the message
190 folder(1), rmf(1), rmm(1)
194 .RB ` "\-src\ +folder" "' defaults to the current folder"
195 .RB ` msgs "' defaults to cur"
205 is given, it will become the current folder.
208 nor `all' is specified, the current message in the
209 source folder will be set to the last message specified; otherwise, the
210 current message won't be changed.
212 If the \*(lqPrevious\-Sequence\*(rq profile entry is set, in addition to defining
213 the named sequences from the source folder,
216 those sequences for the destination folders. See
218 for information concerning the previous sequence.
225 to delete the message,
234 or you will create an infinite loop.