emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Tom Alexander <tom@fizz.buzz>, Timothy <orgmode@tec.tecosaur.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Consecutive plain list items of different types
Date: Fri, 22 Sep 2023 09:24:12 +0000	[thread overview]
Message-ID: <871qeqzhkz.fsf@localhost> (raw)
In-Reply-To: <da2eb361-5397-4205-b223-8f2e7518d4ad@app.fastmail.com>

"Tom Alexander" <tom@fizz.buzz> writes:

> The org-mode documentation[1] states for plain lists that:
>> List types are mutually exclusive at the same level of indentation, if both types are present consecutively then they parse as separate lists.
>
> first a minor nit-pick that "both" is probably not the correct word here since there are 3 types of lists, not two (unordered, ordered, and descriptive). I'd go with "multiple" instead IMO.

Fixed.
https://git.sr.ht/~bzg/worg/commit/c7445f84

> but more importantly, based on that description I would expect the following test document to parse into three separate plain lists, but it parses as a single plain list with 3 items:
>
> ```
> 1. foo
> - bar
> - lorem :: ipsum
> ```
>
> [1] https://orgmode.org/worg/org-syntax.html#Plain_Lists

AFAIK, the first item determines the list type in our parser.
Timothy, do you remember why you wrote about different list types being
parsed separately?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2023-09-22  9:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-22  0:41 Consecutive plain list items of different types Tom Alexander
2023-09-22  9:24 ` Ihor Radchenko [this message]
2024-05-03 11:07   ` Ihor Radchenko
2024-05-03 16:39     ` Tom Gillespie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871qeqzhkz.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=orgmode@tec.tecosaur.net \
    --cc=tom@fizz.buzz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).