emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: Greg Minshall <minshall@umich.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: 'false' list item
Date: Mon, 22 Feb 2021 14:26:03 +1100	[thread overview]
Message-ID: <874ki47p4m.fsf@gmail.com> (raw)
In-Reply-To: <678485.1613962105@apollo2.minshall.org>

Greg Minshall <minshall@umich.edu> writes:

> Tim,
>> If a line starts with a number, period and space, but that line is
>> within a paragraph (i.e. no blank line above), then I don't think it
>> should be interpreted as an enumerated list item. If this is what the OP
>> is referring to, I would argue it is a bug. If it is a 'paragraph'
>> starting with a number, period and space, then being interpreted as a
>> list item would be 'normal'.
> i know this isn't precisely the discussion, but i use *unnumbered*
> lists, and i most often have no blank line separating the list from the
> paragraph above (or, indeed, below).  i could get used to a modified
> requirement, to reduce the false positives, but, would want heads up
> (or, maybe, sigh, an option?).

There is no plans to change anything as far as I know. What I wrote was
mainly to show why we have the situation and that any proposed solution
has its own drawbacks.

Bottom line, we cannot easily prevent the 'false' list item issue
without introducing either other issues or adding some additional syntax
to indicate list items, which defeats the 'plain' aspects which many
appreciate in org. Even the proposed 'solutions' still suffer from false

The question is probably, how can we 'flag' possible false positives in
a convenient manner. For example, it has been suggested that some form
of highlighting for list elements might make it easier to spot a false
element lurking in a paragraph of text. this could possibly be useful,
but I also worry about adding more font-locking and highlighting due to
the potential to degrade performance further. We already have people
running into issue with performance in large org files.

Tim Cross

  reply	other threads:[~2021-02-22  3:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 17:37 'false' list item Juan Manuel Macías
2021-02-21  6:56 ` Kyle Meyer
2021-02-21  7:05   ` Tim Cross
2021-02-21 14:49     ` Juan Manuel Macías
2021-02-22  2:48     ` Greg Minshall
2021-02-22  3:26       ` Tim Cross [this message]
2021-02-22  6:08         ` Greg Minshall
2021-02-21 19:33   ` Juan Manuel Macías
2021-02-21 19:40     ` Diego Zamboni
2021-02-21 21:27       ` Samuel Wales
2021-02-21 22:25         ` Juan Manuel Macías
2021-02-21 22:31         ` Tim Cross
2021-02-22  0:21           ` Juan Manuel Macías
2021-02-21 22:45       ` Kyle Meyer
2021-02-22 11:56       ` Eric S Fraga
2021-02-21 22:55     ` Kyle Meyer

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:

  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=874ki47p4m.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=minshall@umich.edu \


* 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


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).