Hi,
Just retaking/expanding the discussion here.
I think that we need a better way to make syntax coloring easier for
Leo. I don't know which are the details in leo/modes but would be nice
to have some kind of compatibility layer to some syntax coloring files.
For example importing the 200plus languages (including yaml) of jEdit
would be handy (If I remember well, there is a relationship in this
aspect between jEdit and leo, but I don't remember which one). Being Leo
such a a versatile tool, wich is also code editor, having such
limitation on syntax coloring support is really annoying.
On the argument about support for yaml as a storage format, I have
talked about it in the past. Yaml is as good as XML handling unicode and
Leo could be version control system friendlier with a light markup
language. I think that IPython people made a smart decision using JSON
as a human readable format for their notebooks, instead of the
ugly/unreadable, popular and machine oriented XML. I can imagine myself
solving merging conflicts on a human readable JSON IPython Notebook, but
now I'm having problems trying to make sense of this:
http://mutabit.com/deltas/repos.fossil/doctorado-offray/artifact/2f7866207b0301f9b6b07a9a311b9b5bbe1a79a3
which is a Leo notebook having all my research notes for my phD (and now
I'm unable to open it). I started a new notebook for other related phD
related matters (I wont' give up on Leo "meta-cognitive" features for
writing!) and now that I'm starting to express my ideas in code may be I
can made a more vocal case for this kind of feature. Having human
readable plain text format for Leo metadata structure would be a way to
support the things discussed in the recent threads of a distributed Leo
(without going in the way of some ZODB o git storage options).
Cheers,
Offray
El 25/04/12 13:58, Edward K. Ream escribió:
On Wed, Apr 25, 2012 at 3:28 AM, Exaos Lee <[email protected]> wrote:
在 2012年4月25日星期三UTC+8上午6时41分38秒，Edward K. Ream写道：
Could I request the support of YAML? :-)
Python supports yaml internally since 3.0.
Sure. If you like, you could file an official wish-list bug.
As I mentioned previously, there are really two separate kinds of support:
1. syntax coloring
It's not clear what should be done. Almost all of yaml is key: value
pairs. It's not obvious to me what kind of coloring should be done.
2. importing
I found this in a to-do item:
QQQ
Import/Export to yaml
Need a good yaml parser first: I don't want to write another parser by hand.
QQQ
Googling "python yaml" yields: http://pyyaml.org/
which claims to be a "YAML parser and emitter for Python."
So this looks like the way to go. In fact, a case can be made for
representing .leo files as yaml files rather than xml files. This
isn't urgent, and can't be done at all unless yaml does as good a job
of handling Unicode as does xml.
Edward
--
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.
