From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Tim Cross <theophilusx@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: 'false' list item
Date: Mon, 22 Feb 2021 01:21:51 +0100 [thread overview]
Message-ID: <87v9alq7ds.fsf@posteo.net> (raw)
In-Reply-To: <87wnv1do1t.fsf@gmail.com> (Tim Cross's message of "Mon, 22 Feb 2021 09:31:57 +1100")
Tim Cross <theophilusx@gmail.com> writes:
> The issue is, if we decide this is a bug, can we fix it? Is it a bug or
> is it just an accepted limitation of the org document format and what we
> have to do is ensure either no line starts with a '1. ' or we use
> something like a unicode character so that it doesn't look like a
> number+period+space and therefore not a list item?
Interesting all the points you comment, and this paragraph is important.
I'm thinking that without a clear and explicit environment (a begin/end
marks), any possible solution will always have its exceptions. However,
IMHO, I would not find desirable two explicit marks environment in the
style of LaTeX, since this would go against the virtue of legibility and
lightness in Org. I don't know if Markdown (on what it has in common
with Org as a lightweight markup language) also has similar problems in
lists formatting, since I hardly use Markdown and am not aware of its
many implementations...
I still think that highlighting the items would at least be a preventive
solution for Org.
Best regards,
Juan Manuel
next prev parent reply other threads:[~2021-02-22 0:23 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
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 [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9alq7ds.fsf@posteo.net \
--to=maciaschain@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=theophilusx@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.