summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBastien Guerry <bzg@altern.org>2011-07-17 08:16:59 +0200
committerBastien Guerry <bzg@altern.org>2011-07-17 08:16:59 +0200
commit5dec19fe5b5c14bfb23ff9d7a411b354070d60de (patch)
tree8063b3556b2cbc048f1dc799a2e6f3b9cb4c53ea
parentc59da42c4ecc35f9181fbc7972af0999d66919fd (diff)
downloadorg-mode-5dec19fe5b5c14bfb23ff9d7a411b354070d60de.tar.gz
* org.el (org-refile): minor rewriting.
-rw-r--r--lisp/org.el23
1 files changed, 12 insertions, 11 deletions
diff --git a/lisp/org.el b/lisp/org.el
index c66eb06..8c10534 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -10331,25 +10331,24 @@ the *old* location.")
(defvar org-capture-last-stored-marker)
(defun org-refile (&optional goto default-buffer rfloc)
- "Move the entry at point to another heading.
+ "Move the entry or entries at point to another heading.
The list of target headings is compiled using the information in
-`org-refile-targets', which see. This list is created before each use
-and will therefore always be up-to-date.
+`org-refile-targets', which see.
-At the target location, the entry is filed as a subitem of the target heading.
-Depending on `org-reverse-note-order', the new subitem will either be the
-first or the last subitem.
+At the target location, the entry is filed as a subitem of the target
+heading. Depending on `org-reverse-note-order', the new subitem will
+either be the first or the last subitem.
If there is an active region, all entries in that region will be moved.
However, the region must fulfill the requirement that the first heading
is the first one sets the top-level of the moved text - at most siblings
below it are allowed.
-With prefix arg GOTO, the command will only visit the target location,
-not actually move anything.
+With prefix arg GOTO, the command will only visit the target location
+and not actually move anything.
+
With a double prefix arg \\[universal-argument] \\[universal-argument], \
-go to the location where the last refiling
-operation has put the subtree.
+go to the location where the last refiling operation has put the subtree.
With a prefix argument of `2', refile to the running clock.
RFLOC can be a refile location obtained in a different way.
@@ -10358,7 +10357,9 @@ See also `org-refile-use-outline-path' and `org-completion-use-ido'.
If you are using target caching (see `org-refile-use-cache'),
You have to clear the target cache in order to find new targets.
-This can be done with a 0 prefix: `C-0 C-c C-w'"
+This can be done with a 0 prefix (`C-0 C-c C-w') or a triple
+prefix argument (`C-u C-u C-u C-c C-w')."
+
(interactive "P")
(if (member goto '(0 (64)))
(org-refile-cache-clear)