From: "Eric Schulte" <email@example.com>
To: Jambunathan K <firstname.lastname@example.org>
Cc: Org Mode <email@example.com>
Subject: Re: [Babel] now understands org-mode lists
Date: Wed, 17 Nov 2010 18:14:52 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Jambunathan K <email@example.com> writes:
> "Eric Schulte" <firstname.lastname@example.org> writes:
>> I've just pushed up a small commit (including minimal documentation)
>> which teaches code blocks how to read and write Org-mode lists. The
>> following example should demonstrate the new behavior.
>> #+results: a-list
>> - org-mode
>> - and
>> - babel
>> #+source: a-list
>> #+begin_src emacs-lisp :var lst=a-list :results list
>> (reverse lst)
> Why not call the underlying type an 'orglist'. One can for example think
> of orgpropeties etc etc.
I was just thinking that list is simpler and shorter, we need not prefix
everything in the Org domain with the prefix org. Is there a regular
list that you are concerned this name will conflate with.
> Btw, for the sake of illustration, how would one convert a numbered list
> to an alphabetical list or an unordered list. Convert some thing like
> 1. One
> 1. OneOne
> 3. Two
> 4. Three
> - One
> - One
> - Two
> - Three
> 1. One
> 1.1 OneOne
> 2. Two
> 3. Three
> C-c C-c on a list currently renumbers the list which I find quite
> useful. May be there is a way to 'rebind' it so that it not only
> renumbers but renumbers with a different style (that the user is
> comfortable with). Think 'replace-region' for example.
I haven't thought of how these `meta' or `style' properties of lists
should be represented, I am hoping that some good ideas for this will
come from the list (the mailing list).
The most obvious solution seems to be a new header argument
":list-style" or somesuch, which could take options for all org-mode
list style types. The backend uses the `org-list-to-generic' function
which already exists inside of Org-mode and has a great deal of options
so ideally any solution will serve as a thin layer to pass options
directly from the user through to this function. The main question is
"what's the best syntax".
Thanks -- Eric
> 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.
next prev parent reply other threads:[~2010-11-18 1:23 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
2010-11-18 15:27 ` Eric Schulte
2010-11-18 1:14 ` Eric Schulte [this message]
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).