emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Lists made stronger: lists within lists
Date: Mon, 13 Dec 2010 08:49:17 +0100	[thread overview]
Message-ID: <AANLkTikm7iA1Qq0LoQ8+9LoV_404pCtRg8wzuvuhDLf+@mail.gmail.com> (raw)
In-Reply-To: <87bp4qc2sc.wl%n.goaziou@gmail.com>

Hi Nicolas,

On Sun, Dec 12, 2010 at 6:35 PM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> Hello,
>
> As I had promised it here a few days ago, I just pushed a testing
> branch allowing to have lists in blocks, drawers and inline tasks.
> These constructs can themselves be located in lists.
>
> Basically, lists are allowed in every block but "src", "example" and
> "verse". Inline tasks will not end lists, even though they start at
> column 0. Exporters should understand quite intricate situations. Here
> is an example of this:
>

I have started trying it. So far looks pretty good (with src and
example blocks). I do use inline tasks, I'll try with them in the next
few days.

>
> -----
> * Let's stress-test lists
>
>  - a list
>
>    1. Sub-item with both example and quote blocks
>       #+begin_example
>       + here is a false list
>       #+end_example
>
>       #+begin_quote
>       1. followed by a real list
>       2. of two items
>          1. and a sub-item
>
>
>       And some other text afterwards.
>       #+end_quote
>
>    2. Sub-item with src block
>       #+begin_src emacs-lisp
>       (message "Am I appearing?")
>       #+end_src
>
>    3. Sub-item with a drawer
>       :LOGBOOK:
>       * One
>         * One dot one
>         * One dot two
>       :END:
>
>  - and now some centering
>
>    #+begin_center
>    1. One
>    2. Two
>    #+end_center
>
>
>  The end.
> -----
>
> This is not a trivial patch, so it needs careful testing (and maybe
> some re-factoring). The branch can be found at:
>
>  git://github.com/ngz/org-mode-lists.git recursive-lists
>
>
> I still think inline tasks shouldn't be included in lists, but for
> now, let's see it as a proof of concept. I can always remove it later
> if it is "too much". The same idea applies to this whole patch: if it
> is not really needed, it will not reach master branch.
>
> Regards,
>
> -- Nicolas
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>



-- 
Suvayu

Open source is the future. It sets us free.

  parent reply	other threads:[~2010-12-13  7:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12 17:35 Lists made stronger: lists within lists Nicolas Goaziou
2010-12-13  5:28 ` Samuel Wales
2010-12-13  7:49 ` suvayu ali [this message]
2010-12-13 14:49 ` Karl Maihofer
2010-12-13 14:50   ` Carsten Dominik

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=AANLkTikm7iA1Qq0LoQ8+9LoV_404pCtRg8wzuvuhDLf+@mail.gmail.com \
    --to=fatkasuvayu+linux@gmail.com \
    --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).