Sebastian Fischmeister writes:
>>> This causes problems, when the level has semantic meaning beyond
>>> defining the hierarchy (e.g., level 3 always indicates a task while
>>> levels 2 and 1 are project headings).
>>
>> Why don't you simply refile into the parent, then?
>
> Because there might no
>> This causes problems, when the level has semantic meaning beyond
>> defining the hierarchy (e.g., level 3 always indicates a task while
>> levels 2 and 1 are project headings).
>
> Why don't you simply refile into the parent, then?
Because there might not be a lvl 2 heading, but still lvl 3 are
Hello,
Sebastian Fischmeister writes:
> This allows to specify via a variable whether org-refile should keep the
> level of the item when refiling. At the moment, org-refile automatically
> creates a sub-item at the next level. This causes problems, when the
> level has semantic meaning beyond d
Hi,
This allows to specify via a variable whether org-refile should keep the
level of the item when refiling. At the moment, org-refile automatically
creates a sub-item at the next level. This causes problems, when the
level has semantic meaning beyond defining the hierarchy (e.g., level 3
always