From: Carsten Dominik <carsten.dominik@gmail.com>
To: Baoqiu Cui <cbaoqiu@yahoo.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Feature request (org-empty-line-terminates-plain-lists)
Date: Mon, 8 Jun 2009 19:59:46 +0200 [thread overview]
Message-ID: <CF0080A5-7637-4D5B-B9E0-CC28B8ACDDF6@gmail.com> (raw)
In-Reply-To: <byctz5i3y6y.fsf@muchbodyking-lm.corp.yahoo.com>
On Mar 25, 2009, at 7:37 AM, Baoqiu Cui wrote:
> Hi Carsten,
>
> Carsten Dominik <carsten.dominik@gmail.com> 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
>> exporter.
>> It would also cause a lot of problems with the edit-source-code
>> stuff
>> with "C-c '", because we could then no longer use indentation
>> functionality while editing the examples.
Option (1) will be implemented in 6.28, option (2), which was
implemented
temporarily is deprecated or may be removed.
- Carsten
>>
>> 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
>> necessary.
>>
>> 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 ": ..."
> example lines.).
>
> 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
> lists.
>
> 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 `*'.
>
> Baoqiu
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2009-06-08 17:59 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
2009-06-08 17:59 ` Carsten Dominik [this message]
2009-03-25 6:49 ` Samuel Wales
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=CF0080A5-7637-4D5B-B9E0-CC28B8ACDDF6@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=cbaoqiu@yahoo.com \
--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).