emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: 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: Thu, 03 Feb 2011 19:04:20 +0100	[thread overview]
Message-ID: <87lj1x0zbv.fsf@Rainer.invalid> (raw)
In-Reply-To: 4D4A7F61.4010202@christianmoe.com

Christian Moe <mail@christianmoe.com> writes:
> For once, I have to disagree: Numbers at the beginning of the line
> inadvertently starting a list item is a bug.

Something that is a direct result of the specification can't be usefully
called a bug of the implementation.  It may still be unexpected and/or
unwanted behaviour, so I like to call it an accidental feature.

Please not that it can (by specification) happen to other list
constructs just as well - and given the chance, it will.  Let me try:

--8<---------------cut here---------------start------------->8---
1. This is an awfully constructed example of how I might mess up (1, 2,
  3) - oops, I just did.  I might have triggered a different accidental
  feature if my linewrap would have been set two columns later.  How's
  that looking to you?
--8<---------------cut here---------------end--------------->8---

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

Again, this is the result of syntactic convenience for the common case.
This sort of thing tends to break less common cases, which is precisely
the reason TeX macros are sprinkled with seemingly superfluous {} at
every conceivable word boundary.


Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

  parent reply	other threads:[~2011-02-03 18:04 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
2011-02-03 18:04     ` Achim Gratz [this message]
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=87lj1x0zbv.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \
    /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).