emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [Babel] now understands org-mode lists
Date: Thu, 18 Nov 2010 07:47:56 +0530	[thread overview]
Message-ID: <814obf4bor.fsf@gmail.com> (raw)
In-Reply-To: <87d3q3h1b2.fsf@gmail.com> (Eric Schulte's message of "Wed, 17 Nov 2010 18:14:52 -0700")

"Eric Schulte" <schulte.eric@gmail.com> writes:

> Jambunathan K <kjambunathan@gmail.com> writes:
>> "Eric Schulte" <schulte.eric@gmail.com> writes:
>>> Hi,
>>> 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)
>>> #+end_src
>> 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.

Probably I just jumped to a quick conclusion based on a naive
understanding of the description.

I thought that `results' are `output' as `orgmode lists'.

Our mails have crossed. I have tried answering in the last of my
previous mails most of the questions that you have raised.

Ignore me if I don't make any sense :-). 

To reiterate:
1. Alphabetical lists has already surfaced and a patch is in
2. ascii backend is the dumbest one that doesn't offer any custom style
   associations like HTML or OpenOffice. I find the ASCII backend the
   most useful of all the backends.
3. The easy menu map is one Orgmode already uses to capture
   'polymorphic' behaviour as in C-c C-e binding and may be this could
   be used for choosing styles (from the user side).
4. The new feature could be used for 'ingestion' of custom-styles. So a
   power-user has better control.

Jambunathan K.

  reply	other threads:[~2010-11-18  2:18 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
2010-11-18  2:17     ` Jambunathan K [this message]
2010-11-18 15:30       ` Eric Schulte
2010-11-18 15:55 ` Nicolas Goaziou
2010-11-18 16:34   ` Eric Schulte

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:

  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=814obf4bor.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@gmail.com \


* 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).