summaryrefslogtreecommitdiff
path: root/lisp/mh-e/mh-funcs.el
diff options
context:
space:
mode:
authorBill Wohler <wohler@newt.com>2005-12-04 22:34:49 +0000
committerBill Wohler <wohler@newt.com>2005-12-04 22:34:49 +0000
commit2be362c2d561922b4c6603630165d8ef5e30a894 (patch)
treee2cc2277b682cedce57ef9e007e96a18501b0f15 /lisp/mh-e/mh-funcs.el
parent7b18d88fe2382d1fbc5f3a1d202c3d3efb7a93fe (diff)
downloademacs-2be362c2d561922b4c6603630165d8ef5e30a894.tar.gz
* mh-comp.el (mh-forward): Went over all uses of the word "RANGE" in
the docstrings and made usage consistent. Generally speaking, "messages in range" and "range of messages" is redundant and just "range" can be used in most circumstances. Also ensured that mh-interactive-range was mentioned in all interactive functions that use a range which describes the range argument for both users and programmers. * mh-e.el (mh-delete-msg-no-motion, mh-refile-msg) (mh-refile-or-write-again, mh-rescan-folder, mh-undo) (mh-visit-folder, mh-scan-folder, mh-regenerate-headers) (mh-notate-user-sequences, mh-delete-msg-from-seq, mh-catchup): Ditto. * mh-funcs.el (mh-copy-msg, mh-pack-folder, mh-pack-folder-1): Ditto. * mh-junk.el (mh-junk-blacklist, mh-junk-whitelist): Ditto. * mh-print.el (mh-ps-print-range, mh-ps-print-msg) (mh-ps-print-msg-file, mh-print-msg): Ditto. * mh-seq.el (mh-put-msg-in-seq, mh-range-to-msg-list) (mh-narrow-to-range, mh-toggle-tick): Ditto.
Diffstat (limited to 'lisp/mh-e/mh-funcs.el')
-rw-r--r--lisp/mh-e/mh-funcs.el27
1 files changed, 20 insertions, 7 deletions
diff --git a/lisp/mh-e/mh-funcs.el b/lisp/mh-e/mh-funcs.el
index 4f9adbe970b..ca2f7333eb8 100644
--- a/lisp/mh-e/mh-funcs.el
+++ b/lisp/mh-e/mh-funcs.el
@@ -79,7 +79,14 @@ field yourself."
;;;###mh-autoload
(defun mh-copy-msg (range folder)
- "Copy the specified RANGE to another FOLDER without deleting them.
+ "Copy RANGE to FOLDER\\<mh-folder-mode-map>.
+
+If you wish to copy a message to another folder, you can use this command
+\(see the \"-link\" argument to \"refile\"). Like the command
+\\[mh-refile-msg], this command prompts you for the name of the target folder
+and you can specify a range. Note that unlike the command \\[mh-refile-msg],
+the copy takes place immediately. The original copy remains in the current
+folder.
Check the documentation of `mh-interactive-range' to see how RANGE is read in
interactive use."
@@ -156,10 +163,16 @@ Display the results only if something went wrong."
;;;###mh-autoload
(defun mh-pack-folder (range)
- "Renumber the messages of a folder to be 1..n.
-First, offer to execute any outstanding commands for the current folder. If
-optional prefix argument provided, prompt for the RANGE of messages to display
-after packing. Otherwise, show the entire folder."
+ "Pack folder\\<mh-folder-mode-map>.
+
+This command packs the folder, removing gaps from the numbering sequence. If
+you don't want to rescan the entire folder afterward, this command will accept
+a RANGE. Check the documentation of `mh-interactive-range' to see how RANGE is
+read in interactive use.
+
+This command will ask if you want to process refiles or deletes first and then
+either run \\[mh-execute-commands] for you or undo the pending refiles and
+deletes, which are lost."
(interactive (list (if current-prefix-arg
(mh-read-range "Scan" mh-current-folder t nil t
mh-interpret-number-as-range-flag)
@@ -175,8 +188,8 @@ after packing. Otherwise, show the entire folder."
(defun mh-pack-folder-1 (range)
"Close and pack the current folder.
-Display the given RANGE of messages after packing. If RANGE is nil, show the
-entire folder."
+
+Display RANGE after packing, or the entire folder if RANGE is nil."
(mh-process-or-undo-commands mh-current-folder)
(message "Packing folder...")
(mh-set-folder-modified-p t) ; lock folder while packing