From: Baoqiu Cui <firstname.lastname@example.org>
Subject: Re: Feature request (org-empty-line-terminates-plain-lists)
Date: Tue, 24 Mar 2009 23:37:25 -0700 [thread overview]
Message-ID: <email@example.com> (raw)
Carsten Dominik <firstname.lastname@example.org> writes:
> Possible solutions:
> 1. Allow #+begin_example and friends to be indented and remove the same
> amount of whitespace from all example lines as the #+begin line has.
> This is possible, but would require a lot of work in the LaTeX
> It would also cause a lot of problems with the edit-source-code
> with "C-c '", because we could then no longer use indentation
> functionality while editing the examples.
> 2. Adapt the LaTeX exporter to work like the HTML exporter, ignoring
> indentation of tables and example. The, introduce a special list
> item like "- ___" to explicitly terminate a list if this should be
> I welcome comments on this issue.
Thanks for looking into this problem! Personally I would prefer option
1) if it does not require too much work. Supporting indented tables and
#+begin_example etc. in Org-mode plain lists not only makes list
structure look cleaner, but also fits well in Org-mode's powerful
structure editing functionality (org-do-promote/demote already supports
lot of automatic indentation today, including tables and ": ..."
Option 2) is a very good compromise, because it is cheap to implement,
and, for *most* of the times, people do not need to use "- ___" in their
The only problem with option 2) is that, to terminate an ordered list
that has N items, do we have to use something like "(N+1). ___"? Number
N+1 here makes the list look a little bad. Also, "+ ___" and "* ___"
may be required for list item starting with `+' or `*'.
next prev parent reply other threads:[~2009-03-25 6:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 21:28 Feature request (org-empty-line-terminates-plain-lists) Matthew Lundin
2009-03-23 23:08 ` Matthew Lundin
2009-03-24 6:15 ` Baoqiu Cui
2009-03-24 8:48 ` Carsten Dominik
2009-03-24 23:13 ` Matthew Lundin
2009-03-25 6:37 ` Baoqiu Cui [this message]
2009-06-08 17:59 ` Carsten Dominik
2009-03-25 6:49 ` Samuel Wales
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 \
* 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).