Hi! Thanks for your interest and your question! :)
If you follow the link, you can see from the first paragraph that starts the 'readme', that there is a line giving links to the official site and documentation:
See Leo, the Literate Editor with Outline, at leoeditor.com or on github, and VS Code at code.visualstudio.com.
Also, this is not 'language specific' tool, so I didn't think about posting in 'programmingLanguages' but you might be right in that it may reach people who still might have an interest in something like 'Leo'. So thanks again!
I'm sure this is great, but what actually is the Leo editor's selling point? Looking through the links it's a bit hard to see.
Going to https://leoeditor.com/ I see this:
> Leo is a PIM, IDE and outliner that accelerates the work flow of programmers, authors and web designers. Outline nodes may appear in more than one place, allowing multiple organizations of data within a single outline.
which doesn't really mean anything, and on https://leoeditor.com/preface.html I get the impression it's Emacs but written in Python instead of Emacs Lisp? I already use Emacs...
This in particular is very cryptic:
> An outliner. Everything in Leo is an outline.
If you are looking for another example of a projection editor with ideas you can still and aren't aware of it you should check out Leo, which structures an entire program as an outline. The idea is simple: everything is a node in the outline and nodes can have arbitrary child nodes so, which includes clones (all peers, rather than symbolic links) so you can organize your file nodes however you want, and when a file node is written all of its children are combined and written to a flat file with sentinels so that the outline can be reconstructed; furthermore, you can put named sections which cause the correspondingly labeled subnode to be substituted in that spot so that you can write code that looks like:
<<First do A>> << Now do B>>
and break out the code for each into a separate node.
The clones mechanism is in particular pretty cool because it means that you can have, say, a WORKING ON node where you put clones of all the parts of the files you are working on so you can keep them in one compact space.
I used Leo for a while but at some point it just felt too lacking as a text editor so I moved away from it, but I would love to see the ideas in it spread more widely.
I use Leo editor leoeditor.com
It doesn't has basic support for rust (syntax coloring only), but it allows superb organization of code using outlines. Using Leo to edit a function with 200 lines or more is as easy as editing function with 20 lines of code using some other ordinary editor.
Leo can be scripted using Python and it can be great help and time-saver.
> org-mode is perfect suitable for reproducible research.
I think the Leo Editor is better for that. Plus Leo is easier to come to grips with.
Org-mode is tossed into the jungle/jumble that Emacs (Lisp) is. Leo is a very focused product.
What combination do you envision given these fundamental differences, with the most basic difference being that Leo is based around Python objects and Org-mode is based around text.