Re: Qt docking as a replacement for NestedSplitter "Easteregg" menu.

On Monday, September 26, 2016 at 8:42:56 PM UTC+2, Terry Brown wrote: > > > https://github.com/leo-editor/snippets/blob/master/examples/layout/qtdock.py > > is a Py 2.7 / Qt 4 demo of Qt docking as it might apply to Leo, with > comments > in the doc. string. I think it's definitely worth

Re: My 15 year plan

Ed and all, Awareness of this predicament we face isn't new. I first learned of it via the dieoff.org site in 1999. (The site has recently changed; it used to consist mainly of links to many articles. Still worth reading, though.) A few thoughts: * "Pessimism has negative survival

Small typos in the Leo testimonials page (made by myself)

Hi, Today I was re-reading the testimonials page of Leo. Was a nice surprise to find me myself there! (http://leoeditor.com/testimonials.html#id23) I'm not a native speaker and I made still a lot of errors and typos. I found that in the mail that was quoted I made some. Where I said: > For

Re: Syntax coloring cloned node

One possible solution would be to use Leo-UNL instead of clones. For example in your @rst file you put somewhere following: .. code:: nasm LEOUNL:: Then run the following script (could be turned in to button) to generate your rst files: @first # -*- coding:utf-8 -*- import re import os

Re: Using leo for acquiring new fields of knowledge (self-education) and keeping compact documentation

By now, the best example I found of what I mean is this quote from Leo is an excellent PIM : “Cloning is pure genius!... Leo’s cloning facility, allows me to create several views on the CFA course material. My main view follows the prescribed study