From: Jambunathan K <firstname.lastname@example.org>
To: Eric Schulte <email@example.com>
Cc: Org Mode <firstname.lastname@example.org>
Subject: Re: [Babel] now understands org-mode lists
Date: Thu, 18 Nov 2010 07:18:28 +0530 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Jambunathan K.'s message of "Thu, 18 Nov 2010 06:23:35 +0530")
> Let's say one wants to number the lists using prime numbers. So one
> could have two lists.
> # list1 (may be generated programmatically)
> 1. 2
> 2. 3
> 3. 5
> 4. 7
> 5. 11
> 6. 13
> # list2 (user-typed)
> 1. Carsten
> 2. Bastien
> 3. Eric Schulte
> 4. Dan Davison
> 5. Eric S Faga
> 6. Samuel Wales
> and juxtapose them together to get a custom numbering as follows
> 2. Carsten
> 3. Bastien
> 5. Eric Schulte
> 7. Dan Davison
> 11. Eric S Faga
> 13. Samuel Wales
May be the juxtaposition happens as overlays. So basically the custom
bullets (2, 3, 5, 7, 11, 13 etc) are overlays over 1, 2, 3, 4, 5, 6 etc
so that Org still recognize them as lists.
Apologies for being so gross.
To summarize, what I am really thinking is this:
1. Use C-c C-c (org-dwim) with a prefix modifier key that makes it
2. The custom dwim pops up an easy menu that is context dependent. For
example, for the list case it could offer a choice of numbering
styles - alphabetical, subsection etc.
3. Make Babel recognize implicit arguments and results. So when on a
Orgmode list (or when the active region is a Ormode list), Babel
creates a virtual 'input' var that represents the textual list and
does 'replace-region' for the results block. So there is no more
'#+results' that the user sees in the text document
4. The easy menu keys in (2) maps to 'library of babel' calls that
behave as in (3) which creates needed overlays.
5. Make the exporters (specifically the ASCII exporter) to use overlays
to emit the custom-styled lists.
The above idea is more or less along the lines that I exchanges with you
a few months back where I (tried) articulating the idea of Babel as 'a
text manipulator' of Orgmode entities like headlines etc.
> All this with a C-c C-c on list2.
> What this example does is essentially relate a 'list of styles' to a
> 'list of text elements' and create a 'custom-styled list'.
> Jambunathan K.
>> Jambunathan K.
>>> This is just a quick first pass at this functionality, there are still
>>> some unanswered questions, such as if and how code blocks should
>>> differentiate between ordered and unordered lists (ordered get an index
>>> for each item?), how nested lists should be represented etc...
>>> Best -- Eric
>>> Emacs-orgmode mailing list
>>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
next prev parent reply other threads:[~2010-11-18 1:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 23:57 [Babel] now understands org-mode lists Eric Schulte
2010-11-18 0:42 ` Jambunathan K
2010-11-18 0:53 ` Jambunathan K
2010-11-18 1:20 ` Eric Schulte
2010-11-18 12:43 ` Nicolas Goaziou
2010-11-18 1:48 ` Jambunathan K [this message]
2010-11-18 15:27 ` Eric Schulte
2010-11-18 1:14 ` Eric Schulte
2010-11-18 2:17 ` Jambunathan K
2010-11-18 15:30 ` Eric Schulte
2010-11-18 15:55 ` Nicolas Goaziou
2010-11-18 16:34 ` Eric Schulte
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).