Re: `org-refile' doc string

[Nick Dokos <nicholas.dokos@hp.com>]

Štěpán Němec <stepnem@gmail.com> wrote:

> Nick Dokos <nicholas.dokos@hp.com> writes:
> 
> > ...
> > Maybe the doc string should say:
> >
> >   ... However, the region must satisfy some constraints: it has to be
> >   a subtree (or a sequence of subtrees).
> >
> > Would that be clear enough?
> 
> Clear enough for me to understand at least, thanks!
> An alternative and more verbose wording could be something like:
> 
>   However, the region must fulfil the requirement that all the included
>   headings are on the same level as the first one or below (i.e.
>   a subtree or sequence of subtrees).
> 
> Best,
> 
>   Štěpán
> 

OK - here's a patch - mostly Štěpán's wording.

Thanks,
Nick

diff --git a/lisp/org.el b/lisp/org.el
index 9920504..748c140 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -9556,9 +9556,9 @@ 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 fulfil 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.
+However, the region must fulfill the requirement that all the included
+headings are on the same level as the first one or below (i.e. it must
+be a subtree or a sequence of subtrees.)
 
 With prefix arg GOTO, the command will only visit the target location,
 not actually move anything.