Re: Orgalist notes

[Gregor Zattler <telegraph@gmx.net>]

Hi Nicolas,
* Nicolas Goaziou <mail@nicolasgoaziou.fr> [2018-05-07; 22:29]:
> Gregor Zattler <telegraph@gmx.net> writes:
>
>> Yes, I used the customization interface and choose "2)".  [This
>> produces 41 as value of this variable.  I did so, because
>> sometimes a sentence ends in a number and a period but these
>> happen to be after a auto-fill line break and org would assume
>> it's a list, indenting the following lines.
>
[...]
> This shouldn't happen. Org has guards against this kind of auto
> filling.

OK.  Back then, when I customized this I used fill-adapt-mode, perhaps this
was the culpruit.  I do not use it anymore so after this test I
will switch it to t and see what happens.   Thanks for this hint.

>> And I now see, orgalist does not recognize
>>
>> 1) as a list.  Neither does it indent succeeding lines after the
>> first one, nor begin a new numbered item after M-RET
>>
>> If it's not possible to use "2)", then perhaps this should be
>> documented?
>
> This is documented. In `orgalist-mode' docstring:
>
>   When Orgalist mode is enabled, any line beginning with "-", "+", "1."
>   or "a." followed by a space starts a list.
>
> However, setting `org-plain-list-ordered-item-terminator' for Org mode
> should not affect Orgalist minor mode. IOW, activating Orgalist should
> set the variable to ?. unconditionally.
>
> So... here comes Orgalist 1.7.

1. zhfsiu zhuihg uidzhrg idzhg uidhr ihgi udhrg kuidh giudrhui
   tgui ui h iM-RET
2. hae foihfje ohfe oirh gesellschaftlich


Works now without a glitch!

Thanks a bundle for your fast help.

Ciao; Gregor