Nicolas Goaziou writes:
>> The tab indent is treating the list in the :LOGBOOK: as active even
>> though I'm not in the drawer.
>
> It is now fixed.
>
> Thank you very much for testing this branch and reporting this bug.
Thanks for the quick fix and for also fixing the other two issues I
reporte
Hello,
> Bernt Hansen writes:
> Today I entered an org-capture task like this
> ,
> | ** NEXT Investigate errors in log
> |:CLOCK:
> |CLOCK: [2010-08-21 Sat 07:00]
> |:END:
> |:LOGBOOK:
> |- State "NEXT" from "TODO" [2010-08-21 Sat 07:00]
> |:END:
> |
Nicolas Goaziou writes:
Hi Nicolas,
I just started trying out your new list code in one of my org-mode
setups and I think I found a problem.
Today I entered an org-capture task like this
,
| ** NEXT Investigate errors in log
|:CLOCK:
|CLOCK: [2010-08-21 Sat 07:00]
|:END:
|:
Hello,
I introduced in this branch a new variable, namely
`org-list-ending-method', to allow fine-grained control on list
endings.
Here is its docstring:
Determine where plain lists should end.
Valid values are symbols 'regexp, 'indent or 'both.
When set to 'regexp, Org will look into
I have the opposite view.
I did not tried yet the code because I am a naive git user and worry about
messing things up adding another complex branch.
However I must say that all my lists (and I have a lot of them!) do not
satisfy me completely. The problem of breaking indentation and changing
pat
Hi Carsten and Nicolas,
Carsten Dominik wrote:
> On Jul 22, 2010, at 11:08 PM, Nicolas Goaziou wrote:
>
> 2. Some existing documents will break because we now need an end-of-list
> that is clearly defined, and not by indentation. Nicolas proposes a
> double empty line or some special string t
Hello,
> Carsten Dominik writes:
> 1. The ability to have several sublists separated by text, for example
>- item1
>- subitem A1
>- subitem A2
>some text in between the lists, identified as such by indentation
>- subitem B1
>- subitem B2
> Such
