📄 refile.man
字号:
REFILE(1) BSD Reference Manual REFILE(1)NNAAMMEE refile - file message in other foldersSSYYNNOOPPSSIISS refile [msgs] [-draft] [-link] [-nolink] [-preserve] [-nopreserve] [-src +folder] [-file file] [-rmmproc program] [-normmproc] +folder ... [-help]DDEESSCCRRIIPPTTIIOONN _R_e_f_i_l_e moves (_m_v (1)) or links (_l_n (1)) messages from a source folder into one or more destination folders. If you think of a message as a sheet of paper, this operation is not unlike filing the sheet of paper (or copies) in file cabinet folders. When a message is filed, it is linked into the destination folder(s) if possible, and is copied otherwise. As long as the destination folders are all on the same file system, multiple filing causes little storage overhead. This facility provides a good way to cross-file or multiply-index messages. For example, if a message is received from Jones about the ARPA Map Project, the command refile cur +jones +Map would allow the message to be found in either of the two folders `jones' or `Map'. The option `-file file' directs _r_e_f_i_l_e to use the speci- fied file as the source message to be filed, rather than a message from a folder. Note that the file should be a validly formatted message, just like any other _M_H message. It should NNOOTT be in mail drop format (to convert a file in mail drop format to a folder of _M_H messages, see _i_n_c (1)). If a destination folder doesn't exist, _r_e_f_i_l_e will ask if you want to create it. A negative response will abort the file operation. If the standard input for _r_e_f_i_l_e is _n_o_t a tty, then _r_e_f_i_l_e will not ask any questions and will pro- ceed as if the user answered "yes" to all questions. The option `-link' preserves the source folder copy of the message (i.e., it does a _l_n(1) rather than a _m_v(1)), whereas, `-nolink' deletes the filed messages from the source folder. Normally, when a message is filed, it is assigned the next highest number available in each of the destination folders. Use of the `-preserve' switch will override this message renaming, but name conflicts may occur, so use this switch cautiously. If `-link' is not specified (or `-nolink' is specified), the filed messages will be removed from the source folder,[mh.6] MH.6.8 1REFILE(1) BSD Reference Manual REFILE(1) by renaming them with a site-dependent prefix (usually a comma). If the user has a profile component such as rmmproc: /bin/rm then _r_e_f_i_l_e will instead call the named program to delete the message files. The user may specify `-rmmproc pro- gram' on the command line to override this profile speci- fication. The `-normmproc' option forces the message files to be deleted by renaming them as described above. The `-draft' switch tells _r_e_f_i_l_e to file the <mh-dir>/draft.FFIILLEESS $HOME/.mh_profile The user profilePPRROOFFIILLEE CCOOMMPPOONNEENNTTSS Path: To determine the user's MH directory Current-Folder: To find the default current folder Folder-Protect: To set mode when creating a new folder rmmproc: Program to delete the messageSSEEEE AALLSSOO folder(1)DDEEFFAAUULLTTSS `-src +folder' defaults to the current folder `msgs' defaults to cur `-nolink' `-nopreserve'CCOONNTTEEXXTT If `-src +folder' is given, it will become the current folder. If neither `-link' nor `all' is specified, the current message in the source folder will be set to the last message specified; otherwise, the current message won't be changed. If the Previous-Sequence profile entry is set, in addition to defining the named sequences from the source folder, _r_e_f_i_l_e will also define those sequences for the destina- tion folders. See _m_h_-_s_e_q_u_e_n_c_e (5) for information con- cerning the previous sequence.BBUUGGSS Since _r_e_f_i_l_e uses your _r_m_m_p_r_o_c to delete the message, the _r_m_m_p_r_o_c must NNOOTT call _r_e_f_i_l_e without specifying `-normm- proc', or you will create an infinte loop.[mh.6] MH.6.8 2
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -