Re: Leo's real weaknesses

Hi, Nice to see how this discussion is moving forward. I share the idea of longer names. These 3 letters don't convey anything to me and I have to go always to the docs to remember what they mean (I think g if for gui, and c for commander and no idea about p, but I'm always unsure). That

Re: Leo's real weaknesses

Hi, Some years ago I proposed something for Leo, combining two technologies: fossil and Yaml[1], for the same reasons exposed here: fossil a as easier, self contained technology for working with files and Yaml as a diff friendly format to express graphs (trees with clones). At that time the

Re: Syntax coloring mystery solved!!

Congrats on finding the culprit. Couple of things I'd like to see in Leo syntax highlighting, highlighting of trailing whitespace, and highlighting of  https://en.wikipedia.org/wiki/Non-breaking_space and also of tab (\t).  To be quite honest I've only made one foray into the syntax highlighting

Re: Leo's real weaknesses

On Fri, Jan 13, 2017 at 2:22 PM, vitalije wrote: Fossil OTOH, keeps all its data in just one file which is in fact just > sqlite3 database file. > ​Interesting. ​> ​ If you are interested in those scripts I will try to find (or recreate) and share them. ​Of course I'm

Re: Leo's real weaknesses

I suppose it can be done with the git also. But in that case user would need to have git installed and also git would need to recreate '.git' subfolder inside temporary folder every time. Fossil OTOH, keeps all its data in just one file which is in fact just sqlite3 database file. One can

Syntax coloring mystery solved!!

*tl;dr:* Calling doc.markContentsDirty(0, len(p.b)) suffices to recolor a node! This should be done *instead of* calling highlighter.rehighlight explicitly. I could never have found this bug if I hadn't seen how fast pyzo colorizing code was within pyzo itself compared to the *same* code

Re: Leo's real weaknesses

On Fri, Jan 13, 2017 at 4:53 AM, vitalije wrote: Converting from xml to (say) json, won't help. >> > IMHO it is not necessarily true. I don't suggest changing Leo document > format from xml to json or any other format. But there can be found a > scheme of encoding a Leo

Re: Understanding Leo Code

On Tuesday, January 10, 2017 at 5:46:51 PM UTC-5, rengel wrote: Beyond that, there are many other small annoyances: > - In __doc__ strings, Leo code often states the obvious. Every Python > programmer knows, that __init__ is the constructor. > Leo's cff command often finds matches in multiple

Re: Leo's real weaknesses

> > Converting from xml to (say) json, won't help. > > IMHO it is not necessarily true. I don't suggest changing Leo document format from xml to json or any other format. But there can be found a scheme of encoding a Leo document in such a way that its changes can be expressed in a human