orgalist list item spacing

orgalist list item spacing

[Eric Abrahamsen]

I'm a happy user of orgalist, it's very nice to be able to have basic
Org structures in email.

One thing I noticed is that if a paragraph line wraps so that the last
line has a number followed by a full stop, orgalist treats that as a
list item. It seems to me that text should not be considered a list item
unless there's a blank line above it. Ie, this is currently considered a
list item:

This is an email talking about some future plans that will take place in
2020. This line with the 2020<full stop> is considered a list item.

      As evidenced by the indent automatically applied to this line.
      
C-j fixes it, as usual.

Is this a bug, or a configurable option, or just the way it's supposed
to work?

Thanks,
Eric

Re: orgalist list item spacing

[Eric S Fraga]

On Friday, 14 Sep 2018 at 14:47, Eric Abrahamsen wrote:
> One thing I noticed is that if a paragraph line wraps so that the last
> line has a number followed by a full stop, orgalist treats that as a
> list item. It seems to me that text should not be considered a list item
> unless there's a blank line above it. Ie, this is currently considered a
> list item:

[...]

> Is this a bug, or a configurable option, or just the way it's supposed
> to work?

Long standing "feature" of org.  Unless you do require a blank line
between items, it is impossible to differentiate between the start of a
numbered item and the continuation of the previous item in this case.

It's an annoyance sometimes but usually minor.

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.13-783-g97fac4

Re: orgalist list item spacing

[Eric Abrahamsen]

Eric S Fraga <esflists@gmail.com> writes:

> On Friday, 14 Sep 2018 at 14:47, Eric Abrahamsen wrote:
>> One thing I noticed is that if a paragraph line wraps so that the last
>> line has a number followed by a full stop, orgalist treats that as a
>> list item. It seems to me that text should not be considered a list item
>> unless there's a blank line above it. Ie, this is currently considered a
>> list item:
>
> [...]
>
>> Is this a bug, or a configurable option, or just the way it's supposed
>> to work?
>
> Long standing "feature" of org.  Unless you do require a blank line
> between items, it is impossible to differentiate between the start of a
> numbered item and the continuation of the previous item in this case.
>
> It's an annoyance sometimes but usually minor.

Huh, I've never seen this in org-mode proper. I just went and did a bit
of testing, and it looks like wrapping in org-mode involves some
cleverness where it "over-wraps" lines that would otherwise start with a
number, making sure the previous word always comes down to start the
next line. Orgalist isn't that clever, which I guess is by design, and
probably a good thing.

Eric

Re: orgalist list item spacing

[Nicolas Goaziou]

Hello,

Eric S Fraga <esflists@gmail.com> writes:

> On Friday, 14 Sep 2018 at 14:47, Eric Abrahamsen wrote:
>> One thing I noticed is that if a paragraph line wraps so that the last
>> line has a number followed by a full stop, orgalist treats that as a
>> list item. It seems to me that text should not be considered a list item
>> unless there's a blank line above it. Ie, this is currently considered a
>> list item:
>
> [...]
>
>> Is this a bug, or a configurable option, or just the way it's supposed
>> to work?
>
> Long standing "feature" of org.  Unless you do require a blank line
> between items, it is impossible to differentiate between the start of a
> numbered item and the continuation of the previous item in this case.

Correct.

I released Orgalist 1.9, which should hopefully mitigate this issue. In
particular, it is now impossible for auto fill to create these wrong
items.

Regards,

-- 
Nicolas Goaziou

Re: orgalist list item spacing

[Eric Abrahamsen]

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> Eric S Fraga <esflists@gmail.com> writes:
>
>> On Friday, 14 Sep 2018 at 14:47, Eric Abrahamsen wrote:
>>> One thing I noticed is that if a paragraph line wraps so that the last
>>> line has a number followed by a full stop, orgalist treats that as a
>>> list item. It seems to me that text should not be considered a list item
>>> unless there's a blank line above it. Ie, this is currently considered a
>>> list item:
>>
>> [...]
>>
>>> Is this a bug, or a configurable option, or just the way it's supposed
>>> to work?
>>
>> Long standing "feature" of org.  Unless you do require a blank line
>> between items, it is impossible to differentiate between the start of a
>> numbered item and the continuation of the previous item in this case.
>
> Correct.
>
> I released Orgalist 1.9, which should hopefully mitigate this issue. In
> particular, it is now impossible for auto fill to create these wrong
> items.

Thanks! Maybe I was misinterpreting what I was seeing in Org mode buffers.

Re: orgalist list item spacing

[Eric S Fraga]

On Saturday, 15 Sep 2018 at 11:03, Eric Abrahamsen wrote:
> Eric S Fraga <esflists@gmail.com> writes:
>> Long standing "feature" of org.  Unless you do require a blank line
>> between items, it is impossible to differentiate between the start of a
>> numbered item and the continuation of the previous item in this case.
>
> Huh, I've never seen this in org-mode proper. 

Silly me.  I was comparing apples and oranges.  In org mode, I use
visual-line-mode and no filling; in message mode, I use
auto-fill.  Sorry for my intervention!

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.13-783-g97fac4

Re: orgalist list item spacing

[Eric Abrahamsen]

Eric S Fraga <esflists@gmail.com> writes:

> On Saturday, 15 Sep 2018 at 11:03, Eric Abrahamsen wrote:
>> Eric S Fraga <esflists@gmail.com> writes:
>>> Long standing "feature" of org.  Unless you do require a blank line
>>> between items, it is impossible to differentiate between the start of a
>>> numbered item and the continuation of the previous item in this case.
>>
>> Huh, I've never seen this in org-mode proper. 
>
> Silly me.  I was comparing apples and oranges.  In org mode, I use
> visual-line-mode and no filling; in message mode, I use
> auto-fill.  Sorry for my intervention!

No worries, I still ended up learning something :)