New Leo edit control

On Mon, 23 Jan 2017 13:40:48 -0600 "Edward K. Ream" wrote: > On Mon, Jan 23, 2017 at 11:42 AM, john lunzer > wrote: > > > Of the code editor's I've used code comparison is encouraged within > > a single running application, this allows for fancier things

console - can not find gnx:

I get this console output opening LeoDocs.leo: Leo 5.4, build 20170123152929, Mon Jan 23 15:29:29 CST 2017 Git repo info: branch = master, commit = efc05ebd9f23 Python 3.6.0, PyQt version 5.7.1 Windows 10 AMD64 (build 10.0.10586) SP0 reading settings in N:\git\leo-editor\leo\doc\LeoDocs.leo

Re: Leo and fossil

Well, if I'm being honest this is all theoretical in my mind. I've been looking into Fossil more and just the name triggers ideas. Fossil was chosen as a name due to the fact that all artifacts in Fossil are immutable and could be thought of as fossils. The imagery of archaeology is what I

Transitioning to the issue tracker

I am gradually moving my operational habits from to-do lists in leoPy.leo to Leo's issue tracker . There are many items in leo/doc/leoToDo.txt, but most of them are way back on a back burner. I am just about caught up making new issues from new

Re: Leo and fossil

On Mon, Jan 23, 2017 at 12:39 PM, john lunzer wrote: I think node versioning is a potentially "killer app". > ​Maybe. I recently used gitk to review seemingly mysterious changes to a single file. Not "killer", by any means, but useful enough. ​ > Having a fully automatic

Re: Tip: use separate windows to compare code

On Mon, Jan 23, 2017 at 11:42 AM, john lunzer wrote: Of the code editor's I've used code comparison is encouraged within a > single running application, this allows for fancier things like vim's diff > mode which looks like github's HTML diffs. If you open up two Leo >

Re: Leo and fossil

Been mostly on the sidelines on this one, mostly because I didn't have time to think about it. I think node versioning is a potentially "killer app". Having a fully automatic document versioning system at the .leo file level and node level would be a turbo boost in project organization and

Re: Tip: use separate windows to compare code

If thinking forwards. I would not consider the idea "dead". If in the future there are multiple front-ends (Qt/HTML-Javascript/curses) then it might make sense to do this in body editors rather than opening up a whole new Leo. In saying that I'm not trying to induce action, just consideration

Fixed #371: Intermixing code and comments in a single node

Rev c31c1b2 fixes #371 (execute-script fails when a node contains multiple @language directives

Leo 5.5b1 coming soon

The recent work with syntax coloring is too good to sit on. I'll fix a few more bugs before releasing 5.5b1 in about a week. 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

Re: Revised plans for 2017

On Saturday, January 21, 2017 at 5:03:53 PM UTC-6, Edward K. Ream wrote: The 21 present issues > > > are probably going to take most of this year, or perhaps even

Re: Leo's real strengths

On Monday, January 23, 2017 at 5:02:37 AM UTC-6, Edward K. Ream wrote: Still, Leo does have real strengths compared with all other editors and > IDE's: > Without clones, cff and related commands are not possible. EKR -- You received this message because you are subscribed to the Google

Leo's real strengths

emacs org-mode has found a sweet spot, and Leo will not easily dislodge org-mode from its prominent place. And now it *is* possible to think thoughts in org-mode that previously could only be thought in Leo. Still, Leo does have real strengths compared with all other editors and IDE's: -

Re: Revised plans for 2017

On Sunday, January 22, 2017 at 4:34:39 PM UTC-6, Edward K. Ream wrote: Only #374 (Leo can confuse directives with decorators > > ​is of serious concern. I'll attempt a fix today. > Rev 748101dc completes all work on importers. Copies of the