When reviewing the captured data, you may want to refile or to copy some of the entries into a different list, for example into a project. Cutting, finding the right location, and then pasting the note is cumbersome. To simplify this process, you can use the following special command:
Refile the entry or region at point. This command offers possible
locations for refiling the entry and lets you select one with
completion. The item (or all items in the region) is filed below
the target heading as a subitem. Depending on
org-reverse-note-order, it is either the first or last subitem.
By default, all level 1 headlines in the current buffer are
considered to be targets, but you can have more complex definitions
across a number of files. See the variable
details. If you would like to select a location via
a file-path-like completion along the outline path, see the
org-outline-path-complete-in-steps. If you would like to be able
to create new nodes as new parents for refiling on the fly, check
org-refile-allow-creating-parent-nodes. When the
org-log-refile83 is set, a timestamp or a note is
recorded whenever an entry is refiled.
Use the refile interface to jump to a heading.
Jump to the location where
org-refile last moved a tree to.
Refile as the child of the item currently being clocked.
Refile and keep the entry in place. Also see
make this the default behavior, and beware that this may result in
duplicated ‘ID’ properties.
Clear the target cache. Caching of refile targets can be turned on
org-refile-use-cache. To make the command see new
possible targets, you have to clear the cache with this command.
Copying works like refiling, except that the original note is not deleted.
Works like refiling, except that it temporarily toggles how the
org-reverse-note-order applies to the current buffer. So
org-refile would append the entry as the last entry under the
org-refile-reverse will prepend it as the first
entry, and vice-versa.
Note the corresponding ‘STARTUP’ options ‘logrefile’, ‘lognoterefile’, and ‘nologrefile’.