Leo is a hierarchical editor with a tree view of nodes, which can be in Markdown, ReST, code, and create compound docs a la literate programming from nodes, etc.
The killer feature imo is nodes can be cloned to multiple places in the tree. So you could have, for example, group notes by project in one master last, plus another sub-tree for clones from the master list of your own current projects.
Leo's web site may look clunky and old-fashioned. But don't let that put you off!
-- EDIT --
For what it's worth, I do oscillate between Leo and Emacs org-mode. I'd probably stay 100% with org-mode if there were a way to clone nodes. Does anyone know if this is possible?
I believe that what you are explaining is essentially the equivalent to a symbolic/hard link.
As far as I know, one of the goals of org-mode is to have a format that does not diverge from pain text.
Similar to markdown, an org-mode file is always completely readable as pain text, whether using emacs it not.
That means the only way to have an updated "copy" (reference) of a tree would be to automatically copy any changes made to every copy of that tree. That would either require some sort of run-time mark (that would disappear as soon as you kill the buffer), or special syntax.
As far as I know, org-mode does not have such a feature.
From http://leoeditor.com/tutorial-pim.html, it looks like a 'clone' means that the node is presented in several places in the document, but each of those several places bring you back to one, single node.
It seems like org-mode ought to be able to do this, too.
At least, it's weird that emacs/vim _can't_ do something. I can't remember the last time anyone said that about, well, anything :)
A clone is not a copy. When you clone a node in leo, the same node can appear in multiple places at once. If you edit any of the clones, the original is updated.
One use case: You're trying to fix a big in code. You can create a new node and place under it clones of all relevant code (which may exist across multiple files) for the bug. And not just code but also collateral for tests (e.g. unit test or input files that reproduce the bug etc). Oh and might as well clone the bug report as well.
So all that you need to work with the bug conveniently under one node. Just edit there and all relevant files get updated.
Leo is powerful and has a decent user base. It is the closest thing I've found to Emacs in the Python world. Unfortunately the documentation is really bad and I just don't have time to learn it without good documentation. I toyes with the idea of becoming a master at it just so I can write proper docs but life is too short.
With all respect, leo looks like it is an editor from the 90's with its windows 95-looks. For me, that's mostly a sign that the developers do not adhere to modern development standards. As such, why would I invest time in using a dying product/project?
With all respect, a lot of design has devolved, and was actually better in the nineties. In my humble and absolutely personal opinion this goes for software UIs, and for cars (exteriors, not technology). Leo is fine. Atom is not (to name a random example, whre not even the technology holds up).
No, I wasn't even young in the nineties. Just youngerish.
You're just making assumptions. Why does a UI have to be trendy to be good? Seems like a big leap to get from the UI to the development method to the health of the project.
That's not far from the truth. Leo has a horrible broken codebase and the devs are not the most competent around. The project is a prime example of everything bad going in software-development.
But, while lacking, they have the right spirit and are constantly trying to do better. If someone can adapt to the myriad of quirks and failures, it can be a very powerful tool. As an outliner it's definitly better than org-mode. But it might be good to have profund python-knowledge to take advantage of the scripting-ability to make it really useful.
Fun fact. Nulis means zero (0) in Lithuanian. I wonder what other product names unintentionally hit some word in some exotic language. One from top of my head was https://en.wikipedia.org/wiki/Mazda_Laputa (we know what "la puta" means in Spanish)
I actually wrote a quick web app [1] to translate a word from a ton of languages into english (so writers could see if their "made up" words would have any meaning to any demographic), but it could be used here by just putting your product/brand name in. (Please note it's actually hitting Google Translate 50 times since they don't have bulk translate, so results may take a second.)
Fun fact: Nullis seems to mean zero in Ukrainian, Pesian, Latvian, and Estonian as well, while also meaning "no" in Welsh, Latin, and Irish.
I'm not a Vim user anymore,
but this is definitely the most interesting (also, peculiar) approach
to a non-coder's writing tool I've come across over many years of text editor geekery.
I tried to hack together something similar for Plan9's Acme and Sam,
but unfortunately those efforts led nowhere.
I don't like markdown either though, the extra markup interferes with my thinking. Though there is no UI modality, I feel it adds a cognitive modality where I need to switch between thinking about the actual content, and the translation from text semantics to markdown syntax.
But I suppose I could stick to plaintext with these apps. A subtle rich text editing possibility would be appreciated too though.
Edit: Scandinavian keyboards require pressing shift to get /. So accessing the search bar doesn't seem to work at all.
Oh! There is an edit/preview mode, it's just global. I think I like it.
I'm not sure what good the Affero GPL license is good for in this case. The resulting software cannot be distributed under it: It depends on React as a critical and integral component to its functionality. I cannot distribute the resulting software under AGPL, because it contains known patents I lack the right to distribute under the terms of the AGPL license.
Fun fact: nulis/menulis in Bahasa Indonesia is 'writing'
Author replied:I think this is where I got the idea for the name from =) Was looking for something that sounds awesome and relevant, and somehow stumbled upon this word.
Leo is a hierarchical editor with a tree view of nodes, which can be in Markdown, ReST, code, and create compound docs a la literate programming from nodes, etc.
The killer feature imo is nodes can be cloned to multiple places in the tree. So you could have, for example, group notes by project in one master last, plus another sub-tree for clones from the master list of your own current projects.
Leo's web site may look clunky and old-fashioned. But don't let that put you off!
-- EDIT --
For what it's worth, I do oscillate between Leo and Emacs org-mode. I'd probably stay 100% with org-mode if there were a way to clone nodes. Does anyone know if this is possible?
I believe that what you are explaining is essentially the equivalent to a symbolic/hard link.
As far as I know, one of the goals of org-mode is to have a format that does not diverge from pain text.
Similar to markdown, an org-mode file is always completely readable as pain text, whether using emacs it not.
That means the only way to have an updated "copy" (reference) of a tree would be to automatically copy any changes made to every copy of that tree. That would either require some sort of run-time mark (that would disappear as soon as you kill the buffer), or special syntax.
As far as I know, org-mode does not have such a feature.
https://www.gnu.org/software/emacs/manual/html_node/org/Stru...
It seems like org-mode ought to be able to do this, too.
At least, it's weird that emacs/vim _can't_ do something. I can't remember the last time anyone said that about, well, anything :)
One use case: You're trying to fix a big in code. You can create a new node and place under it clones of all relevant code (which may exist across multiple files) for the bug. And not just code but also collateral for tests (e.g. unit test or input files that reproduce the bug etc). Oh and might as well clone the bug report as well.
So all that you need to work with the bug conveniently under one node. Just edit there and all relevant files get updated.
Leo is powerful and has a decent user base. It is the closest thing I've found to Emacs in the Python world. Unfortunately the documentation is really bad and I just don't have time to learn it without good documentation. I toyes with the idea of becoming a master at it just so I can write proper docs but life is too short.
No, I wasn't even young in the nineties. Just youngerish.
Doesn't look very dead to me.
But, while lacking, they have the right spirit and are constantly trying to do better. If someone can adapt to the myriad of quirks and failures, it can be a very powerful tool. As an outliner it's definitly better than org-mode. But it might be good to have profund python-knowledge to take advantage of the scripting-ability to make it really useful.
That Mitsubishi one is hilarious.
Fun fact: Nullis seems to mean zero in Ukrainian, Pesian, Latvian, and Estonian as well, while also meaning "no" in Welsh, Latin, and Irish.
[1] https://www.notebook.ai/app/babel
They say imitation is the best form of flattery, but I'm surprised Ray that you didn't credit Gingko at all. It's practically identical.
Thoughts?
---
Edit: My bad... it's not on the website, but I see Gingko mentioned and linked in the Readme. Thanks Ray.
He does say "inspired by", though not sure if that was the credit you are expecting.
Unfortunately, being the first or most common product in a space has the side effect of attracting copies, spin offs, or other imitations.
Deleted Comment
> Nulis is an open source tree editor for writers, inspired by Gingko.
I will say that it's not mentioned anywhere on nulis.io however.
Couldn't find any mention first time I checked it out.
It allows one to "pan and zoom through text", there's also a screencast: https://www.youtube.com/watch?v=9YNiPUTGO28
I'm not a Vim user anymore, but this is definitely the most interesting (also, peculiar) approach to a non-coder's writing tool I've come across over many years of text editor geekery. I tried to hack together something similar for Plan9's Acme and Sam, but unfortunately those efforts led nowhere.
[1] - http://sandbox.fed.wiki.org/view/welcome-visitors
I find this much easier to learn to use, as I don't have to toggle between edit mode and non-edit mode. (Modality can be tricky: https://medium.com/interaction-reimagined/dangers-of-modal-u... - shameless plug :) )
I don't like markdown either though, the extra markup interferes with my thinking. Though there is no UI modality, I feel it adds a cognitive modality where I need to switch between thinking about the actual content, and the translation from text semantics to markdown syntax.
But I suppose I could stick to plaintext with these apps. A subtle rich text editing possibility would be appreciated too though.
Edit: Scandinavian keyboards require pressing shift to get /. So accessing the search bar doesn't seem to work at all.
Oh! There is an edit/preview mode, it's just global. I think I like it.
Author replied:I think this is where I got the idea for the name from =) Was looking for something that sounds awesome and relevant, and somehow stumbled upon this word.
https://mastodon.social/@rayalez/6864752