From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Kyle Meyer <kyle@kyleam.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: 'false' list item
Date: Sun, 21 Feb 2021 20:33:36 +0100 [thread overview]
Message-ID: <87mtvxrzan.fsf@posteo.net> (raw)
In-Reply-To: <87pn0tj4dt.fsf@kyleam.com> (Kyle Meyer's message of "Sun, 21 Feb 2021 01:56:14 -0500")
Kyle Meyer <kyle@kyleam.com> writes:
> It seems that your approach would do a good job of helping you catch
> cases that you don't want to be treated as lists. I'm not aware of any
> related functionality in Org, so I don't think you're missing something
> there.
>
> Once you know that there is a particular spot that you want to prevent
> from being interpreted as a list, you could add a zero-width space in
> front of it:
>
> (info "(org)Escape Character")
>
> I'm not sure if that's the sort of solution you're asking for, though.
Thanks for your advice, Kyle. Adding the U+200B char. works fine to
avoid false positives. Anyway, like Tim Cross says, that situation
maybe should be considered as a bug. I think the ideal behavior would
be for Org to consider a list only when there is a blank line above.
But, well thought out, I am afraid that it would not prevent false
positives, as one may want perfectly write a list at the beginning of
the document, or start a plain paragraph with (for example) a digit + a
period + a space...
Best regards,
Juan Manuel
next prev parent reply other threads:[~2021-02-21 19: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
2021-02-22 6:08 ` Greg Minshall
2021-02-21 19:33 ` Juan Manuel Macías [this message]
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:
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=87mtvxrzan.fsf@posteo.net \
--to=maciaschain@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=kyle@kyleam.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 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).