Hi,


On Thu, Oct 31 2013, Nicolas Goaziou wrote:

> coroa@online.de (Jonas Hörsch) writes:
>>
>> +  (cond ((eq state 'contents)
>
> I suggest to use `case' here, but it's really a matter of style.

fine with me. i wasn't sure about the usage convention for cl. i
switched to the namespaced cl-case variant, for now.

>> +	   (hide-sublevels (1- org-inlinetask-min-level))))
>> +	     (while (and (outline-next-heading)
>> +			 (org-inlinetask-at-task-p))
>
> I think it is more efficient to directly look for inlinetasks since you
> can use `org-inlinetask-outline-regexp'.

hmm ... i'm not so sure. as you can see in the attached patch, now i
have to perform an extra search on each headline to find the boundary
for the inline task search. it feels to me like this would be faster for
a situation with more than one inline task per headline in the mean?
(which i don't think is the likely situation).

well, what do you think?