>
> Have you used the Leo import script mentioned in this thread?
Yes. Leo 4.11 devel, build 5816, 2013-07-01 08:32:23 Python 3.2.3, qt
version 4.8.2
Is there anything in particular you would like to have happen in the Leo
> world?
>
Long term? I'd like leo-editor, emacs org-mode, and ipython notebook[1] to
share a common storage format (or network protocol, if you think in those
terms--but I insist that they are the same thing). This would enable me to
use the right tool for the right job, all the time. It would also enable
groups of people to collaborate on literate programming projects and
reproducible research projects.
Short term goal? org-mode files have Properties. A property is like a
file-wide variable. You define properties by putting lines like this
somewhere in your org-file:
#+TITLE: FOOBAR document
#+AUTHOR: Dave Loyall
#+LANGUAGE: en
#+OPTIONS: H:1 num:t toc:1 \n:nil @:t ::t |:t ^:nil -:t f:t *:t <:t
#+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc
#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCLUDE_TAGS: noexport
#+BIND: org-export-html-postamble t
#+BIND: org-export-html-table-use-header-tags-for-first-column t
#+BIND: org-export-html-postamble-format (("en" "<hr /><p
class=\"creator\">Generated by %c on %d</p>\n"))
#+TODO: TODO WORKING | DONE POSTPONED CANCELLED
...In this case, in the resultant document, the property named TITLE has a
value of "FOOBAR document".
Note the BIND lines. These work differently... the resultant document gets
lisp variables named org-export-html-postamble,
org-export-html-table-use-header-tags-for-first-column, and
org-export-html-postamble-format, with values of TRUE, TRUE, and the
specified string, respectively.
Note the OPTION lines. These are space separated lists of key/value pairs.
So as you can tell, I'm suggesting that a good short term goal would be to
teach leo to read org-mode properties and save them in some appropriately
named variables. (or a dictionary? Is that the pythonic way?)
Of course, any attempt to parse org-mode properties will immediately reveal
that the syntax was established incrementally by committee over many years.
:)
Thus, here is a medium term goal: provide feedback to org-mode community
regarding rough edges in our .org specification. I believe that without
such feedback, the file format will always include such features as the
vertical bar in the TODO property[2], because they are easy for org-mode to
read, since it has existing code for the purpose, and indeed, in the
absence of third parties there is no reason to change.
Here is an additional medium term goal: I'd like org to learn from leo.
Specifically, I am not aware of an org feature that provides the 'clone a
node into anywhere' concept. (However, I believe that the underlying org
data model already supports this. I also expect that lots of parts of org
code would hang if they encountered a document that contained circular
references!)
I am hoping that this is fun and illuminating.
Cheers,
--Dave
1.
http://ipython.org/ipython-doc/stable/interactive/htmlnotebook.html#the-notebook-format
2.
http://orgmode.org/manual/Per_002dfile-keywords.html#Per_002dfile-keywords
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.
