From: Christian Moe <mail@christianmoe.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Stromeko@nexgo.de, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [BUG] adding new plain lists item changes previous one it it ends in a number on a single lijne followed by a dot
Date: Fri, 04 Feb 2011 20:09:35 +0100 [thread overview]
Message-ID: <4D4C4EEF.8010103@christianmoe.com> (raw)
In-Reply-To: <877hdh6wgf.wl%n.goaziou@gmail.com>
On 2/3/11 3:09 PM, Nicolas Goaziou wrote:
> Hello,
>
>>>>>> Christian Moe writes:
>
>> Numbers at the beginning of the line inadvertently starting a list
>> item is a bug.
>
> You call it a bug, but it is actually the Org definition of a numbered
> item. This is in the manual. Though, I think I understand what you
> mean: this definition can lead to surprising results. But the user is
> warned in the documentation.
I'm sorry, that was silly of me, and I take it back. You and Achim
Gratz are both right. If it follows from the specification, and the
manual warns about it, it's not a bug. I'm usually the first to point
that out to others... don't know what got into me.
>
>> It means you can mess up your exported document (it doesn't just
>> happen at M-RET) by just writing a perfectly normal text, and there
>> is no easy-to-remember escape. (I really don't like the
>> invisible-space workaround -- it's hard to remember how to insert
>> it, and it's a bizarre trick to have to tell newcomers.)
>> ReStructuredText provides a backslash-escape for this, even though
>> its more rigid structure reduces the chances of the error happening.
>> Could we borrow that trick, or would it conflict with something
>> else?
>
> I don't follow you here. Inserting a non-breaking space (it was only
> an example, by the way) is an unacceptable trick to tell to newcomers
> but adding a backslash in front of numbers isn't? It looks the same to
> me.
Sorry I put it that way, that wasn't helpful. Backslash too was just
an example. In this case, an example of a typical escape character
that's right there on my keyboard. I'm not saying it looks better than
what you get with `C-q 240' or similar, but it's easy to remember.
> As long as Org cannot tell between an ordered item and a number at the
> end of a sentence, those problems will persist. And I can't see any
> non-hackish solution about it.
Absolutely.
> We can always change `org-plain-list-ordered-item-terminator' default
> value to the safer ?), though.
As you've pointed out, there's a setting for us to tweak if we want
this, and changing the default would probably cause greater annoyances
for more people. So I'm not urging that.
I'll try to make friends with the invisible non-breaking space.
:)
Yours,
Christian
next prev parent reply other threads:[~2011-02-04 19:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 19:20 [BUG] adding new plain lists item changes previous one it it ends in a number on a single lijne followed by a dot Gregor Zattler
2011-02-02 19:24 ` Jeff Horn
2011-02-02 21:16 ` Nicolas Goaziou
2011-02-03 10:11 ` Christian Moe
2011-02-03 14:09 ` Nicolas Goaziou
2011-02-03 16:11 ` Jeff Horn
2011-02-03 16:47 ` Nicolas Goaziou
2011-02-03 21:22 ` Jeff Horn
2011-02-04 19:09 ` Christian Moe [this message]
2011-02-03 18:04 ` Achim Gratz
2011-02-04 16:16 ` Gregor Zattler
2011-02-05 21:04 ` Nicolas Goaziou
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=4D4C4EEF.8010103@christianmoe.com \
--to=mail@christianmoe.com \
--cc=Stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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 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).