{ "content": [ { "type": "text", "text": "# REFILE (man)\n\n## NAME\n\nrefile - file message in nmh folders\n\n## SYNOPSIS\n\nrefile [-help] [-version] [msgs] [-draft] [-link | -nolink] [-preserve | -nopreserve] [-re‐\ntainsequences | -noretainsequences] [-unlink | -nounlink] [-src +folder] [-file file]\n[-rmmproc program] [-normmproc] +folder1 ...\n\n## DESCRIPTION\n\nrefile moves (see mv(1)) or links (see ln(1)) messages from a source folder into one or more\ndestination folders.\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **FILES**\n- **PROFILE COMPONENTS**\n- **SEE ALSO**\n- **DEFAULTS**\n- **CONTEXT**\n- **BUGS**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "REFILE", "section": "", "mode": "man", "summary": "refile - file message in nmh folders", "synopsis": "refile [-help] [-version] [msgs] [-draft] [-link | -nolink] [-preserve | -nopreserve] [-re‐\ntainsequences | -noretainsequences] [-unlink | -nounlink] [-src +folder] [-file file]\n[-rmmproc program] [-normmproc] +folder1 ...", "tldr_summary": null, "tldr_examples": [], "tldr_source": null, "flags": [], "examples": [], "see_also": [ { "name": "folder", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/folder/1/json" }, { "name": "mh-sequence", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/mh-sequence/5/json" }, { "name": "rmf", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/rmf/1/json" }, { "name": "rmm", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/rmm/1/json" } ], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 4, "subsections": [] }, { "name": "DESCRIPTION", "lines": 67, "subsections": [] }, { "name": "FILES", "lines": 2, "subsections": [] }, { "name": "PROFILE COMPONENTS", "lines": 5, "subsections": [] }, { "name": "SEE ALSO", "lines": 2, "subsections": [] }, { "name": "DEFAULTS", "lines": 7, "subsections": [] }, { "name": "CONTEXT", "lines": 8, "subsections": [] }, { "name": "BUGS", "lines": 4, "subsections": [] } ], "sections": { "NAME": { "content": "refile - file message in nmh folders\n", "subsections": [] }, "SYNOPSIS": { "content": "refile [-help] [-version] [msgs] [-draft] [-link | -nolink] [-preserve | -nopreserve] [-re‐\ntainsequences | -noretainsequences] [-unlink | -nounlink] [-src +folder] [-file file]\n[-rmmproc program] [-normmproc] +folder1 ...\n", "subsections": [] }, "DESCRIPTION": { "content": "refile moves (see mv(1)) or links (see ln(1)) messages from a source folder into one or more\ndestination folders.\n\nIf you think of a message as a sheet of paper, this operation is not unlike filing the sheet\nof paper (or copies) in file cabinet folders. When a message is filed, it is linked into the\ndestination folder(s) if possible, and is copied otherwise. As long as the destination fold‐\ners are all on the same file system, multiple filing causes little storage overhead. This\nfacility provides a good way to cross-file or multiple-index messages. For example, if a\nmessage is received from Jones about the ARPA Map Project, the command\n\nrefile cur +jones +Map\n\nwould allow the message to be found in either of the two folders `jones' or `Map'.\n\nYou may specify the source folder using -src +folder. If this is not given, the current\nfolder is used by default. If no message is specified, then `cur' is used by default.\n\nThe option -file file directs refile to use the specified file as the source message to be\nfiled, rather than a message from a folder. Note that the file should be a validly formatted\nmessage, just like any other nmh message. It should not be in mail drop format (to convert a\nfile in mail drop format to a folder of nmh messages, see inc(1)).\n\nIf a destination folder doesn't exist, refile will ask if you want to create it. A negative\nresponse will abort the file operation. If the standard input for refile is not a tty, then\nrefile will not ask any questions and will proceed as if the user answered “yes” to all ques‐\ntions.\n\nThe option -link preserves the source folder copy of the message (i.e., it does an ln(1)\nrather than a mv(1)), whereas, -nolink (the default) deletes the filed messages from the\nsource folder.\n\nNormally when a message is refiled, for each destination folder it is assigned the number\nwhich is one above the current highest message number in that folder. Use of the -preserve\nswitch will override this message renaming, and try to preserve the number of the message.\nIf a conflict for a particular folder occurs when using the -preserve switch, then refile\nwill use the next available message number which is above the message number you wish to pre‐\nserve.\n\nAs message sequences are folder-specific, moving the message from the source folder removes\nit from all its sequences in that folder. -retainsequences adds it to those same sequences\nin the destination folder, creating any that don't exist. This adding does not apply for the\n“cur” sequence.\n\nIf -link is not specified (or -nolink is specified), the filed messages will be removed from\nthe source folder. The default is to remove these messages by renaming them with a site-de‐\npendent prefix (usually a comma). Such files will then need to be removed in some manner af‐\nter a certain amount of time. Many sites arrange for cron to remove these files once a day,\nso check with your system administrator.\n\nAlternately, if you wish for refile to really remove the files representing these messages\nfrom the source folder, you can use the -unlink switch (not to be confused with the -link\nswitch). But messages removed by this method cannot be later recovered.\n\nIf you prefer a more sophisticated method of `removing' the messages from the source folder,\nyou can define the rmmproc profile component. For example, you can add a profile component\nsuch as\n\nrmmproc: /home/coleman/bin/rmmmsgs\n\nthen refile will instead call the named program or script to handle the message files.\n\nThe user may specify -rmmproc program on the command line to override this profile specifica‐\ntion. The -normmproc option forces the message files to be deleted by renaming or unlinking\nthem as described above.\n\nThe -draft switch tells refile to file the /draft.\n", "subsections": [] }, "FILES": { "content": "$HOME/.mhprofile The user profile\n", "subsections": [] }, "PROFILE COMPONENTS": { "content": "Path: To determine the user's nmh directory\nCurrent-Folder: To find the default current folder\nFolder-Protect: To set mode when creating a new folder\nrmmproc: Program to delete the message\n", "subsections": [] }, "SEE ALSO": { "content": "folder(1), mh-sequence(5), rmf(1), rmm(1)\n", "subsections": [] }, "DEFAULTS": { "content": "`-src +folder' defaults to the current folder\n`msgs' defaults to cur\n`-nolink'\n`-nounlink'\n`-nopreserve'\n`-noretainsequences'\n", "subsections": [] }, "CONTEXT": { "content": "If -src +folder is given, it will become the current folder. If neither -link nor `all' is\nspecified, the current message in the source folder will be set to the last message speci‐\nfied; otherwise, the current message won't be changed.\n\nIf the “Previous-Sequence” profile entry is set, in addition to defining the named sequences\nfrom the source folder, refile will also define those sequences for the destination folders.\nSee mh-sequence(5) for information concerning the previous sequence.\n", "subsections": [] }, "BUGS": { "content": "Since refile and rmm use your rmmproc to delete the message, the rmmproc must not call refile\nor rmm without specifying -normmproc, or you will create an infinite loop.\n\nnmh-1.8 2013-03-19 REFILE(1mh)", "subsections": [] } } } }