Re: Bug in org-inlinetask - was: Re: Feature suggestion: highlights

[Bernt Hansen <bernt@norang.ca>]

Sebastian Rose <sebastian_rose@gmx.de> writes:

> Bernt Hansen <bernt@norang.ca> writes:
>> Sebastian Rose <sebastian_rose@gmx.de> writes:
>>
>>> Ali Tofigh <alix.tofigh@gmail.com> writes:
>>>> But you still have the problem that once you use a headline, on any
>>>> level, then you can't continue writing in the same section as before:
>>>>
>>>> * headling
>>>>   text text text
>>>> ********* some todo
>>>> and now what? Now I have to create a new headline to get out of the
>>>> deeply nested headline. So I can't continue wrting text after the todo
>>>> that is directly related to the text above it.
>>>
>>>
>>> Ahhrg - yes. I never use this kind of todo items.
>>>
>>> I don't know what the others think of this. But this feels wrong,
>>> doesn't it? I'd expect an empty line to break out of the todo. Am I
>>> missing a variable some where?
>>
>> I believe the 'empty line breaks out' idea is for exporting inline tasks
>> only - they don't behave that way in regular org files IIRC.
>
>
> That's exactly the term I meant and I was looking for: `inline tasks'
>
> But unfortunately empty lines do NOT break out of inline tasks.
> I thought they would...
>
> Why are they called `inline tasks' then?


I don't know :)  Maybe because they don't fold like regular tasks.  I've
really only played with this feature a little and didn't find it
particularly useful for my needs.

>
> If I do
>
>   `M-x org-inlinetask-insert-task'

Hmm I didn't know about this function.  I just make a regular task and
shift it to the right enough so that the stars change to indicate it's
inline (the few times I tried using it) ... so I had no end marker.
Someday I'll look at this again from a user-point-of-view.

-Bernt


>
> I get this:
>
>
> * Headline
>
>   Some text...
> *************** TODO inline task
>                 Some text
> *************** END
>
>   Back in original level.
>
>
>
> I am `Back in original level' after the `************* END'
> portion.
>
> BUT to be there, I have to adjust the depth of the nested headline AND
> it still will not work in ASCII export.
>
> Obviously, org-inlinetask.el does not regard the odd/even setting.
> And ASCII export does not reagard inline tasks.
>
>
>
>     Sebastian