The devel branch is now open for commits

2019-08-02 Thread Edward K. Ream
I will soon begin work on 6.1 issues . Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop

Leo 6.0 final released

2019-08-02 Thread Edward K. Ream
Leo 6.0 final, http://leoeditor.com, is now available on GitHub . Many thanks to all who have contributed to this release. *The highlights of Leo 6.0* - Leo now requires python 3.6 or above. This greatly simplifies Leo's code. - Leo's

Re: ENB: building Leo into emacs org mode

2019-08-02 Thread Edward K. Ream
On Fri, Aug 2, 2019 at 7:58 AM Edward K. Ream wrote: *> I have no plans to write the required elisp code*. Indeed, it would be a big distraction for me and Leo's other devs. If I had understood emacs way back in 1985 I would likely have written something like org mode myself. Leo's history

Re: Please hold commits to devel

2019-08-02 Thread Edward K. Ream
On Thursday, August 1, 2019 at 6:18:23 AM UTC-5, Edward K. Ream wrote: This will prevent problems as I prepare for Leo 6.0 final. > The devel branch is now open for commits. I will soon begin work on 6.1 issues

Re: Leo 6.0 final released

2019-08-02 Thread Viktor Ransmayr
Hello Edward, Am Fr., 2. Aug. 2019 um 19:02 Uhr schrieb Edward K. Ream < edream...@gmail.com>: > Leo 6.0 final, http://leoeditor.com, is now available on GitHub > . > Thanks a lot to you & all other Leo developers! - I was able to upgrade a python

Re: Linux Snapcraft and Packager integrations are broken

2019-08-02 Thread Edward K. Ream
On Fri, Aug 2, 2019 at 1:46 PM Matt Wilkie wrote: > > It looks like that with the release of 6.0 in master Packager woke up. The > integration hook now reports success in communicating but Packager itself > failed the build. I haven't looked at the logs yet: >

Re: Leo 6.0 final released

2019-08-02 Thread Matt Wilkie
> > Thanks a lot to you & all other Leo developers! - I was able to upgrade a > python virtual environment instance using PyPI / pip w/o any problem from > Leo version 5.9 to 6.0 ... > Yay! It took awhile to get there with your setup. Thanks for the reports which helped get those bugs sorted

Re: Leo 6.0 final released

2019-08-02 Thread Edward K. Ream
On Fri, Aug 2, 2019 at 2:21 PM Viktor Ransmayr wrote: > Hello Edward, > > Am Fr., 2. Aug. 2019 um 19:02 Uhr schrieb Edward K. Ream < > edream...@gmail.com>: > >> Leo 6.0 final, http://leoeditor.com, is now available on GitHub >> . >> > > Thanks a lot to

Re: Help wanted: stickynotes encryption problems

2019-08-02 Thread Matt Wilkie
> Does anybody else notices similar behavior? I am using Google Chrome, >> regularly updated. >> > > I'm not seeing this with up to date Firefox on Windows right now, but I > have run into formatting wierdness in g-groups before. One thing that > helped was turning off the browser automatic

Re: Linux Snapcraft and Packager integrations are broken

2019-08-02 Thread Matt Wilkie
> > The Leo Github Webhooks > page has two > failing integrations: snapcraft.io and packager.io. > > From a quick inspection it looks like they're supposed to be for building > complete Linux packages to install. Does anyone want to

Re: Linux Snapcraft and Packager integrations are broken

2019-08-02 Thread Chris George
That was me. I initiated it from the packager side. I am still working on snap. I was almost there but needed one file in leo-editor. Unfortunately setup.py, snap, git all have different packaging numbers. Still at it. Chris On Fri, Aug 2, 2019 at 12:30 PM Edward K. Ream wrote: > > > On

Re: Discuss: Retire vim mode?

2019-08-02 Thread Edward K. Ream
On Tuesday, June 25, 2019 at 5:52:55 AM UTC-5, Edward K. Ream wrote: Important: I'm talking about vim *mode* (@bool vim-mode), *not* the vim.py > plugin. The vim plugin is here to stay, although it should be improved. > > Terry and Kent have voted with their feet, and I am grateful to gar for

Re: Leo 6.0 final released

2019-08-02 Thread Matt Wilkie
> > Leo 6.0 final, http://leoeditor.com, is now available on GitHub > . > I think the v6.0 tag needs to be merged into master branch, or something. Or maybe it's just how Git Extensions shows it to me? (git branching

Re: Leo and black

2019-08-02 Thread Matt Wilkie
After playing with black for a bit, I quite like it. The only thing I've seen it change that I haven't wholesale agreed with is dedenting "next line comments". func(arg1, arg2 ... keyword=thing) # indented comment about above line because inline would # be too long, and before-line is

Re: ENB: building Leo into emacs org mode

2019-08-02 Thread Edward K. Ream
On Friday, August 2, 2019 at 7:58:19 AM UTC-5, Edward K. Ream wrote: Org babel is great for code snippets. It does not scale up to entire > source files. > One could consider allowing @others and section references within part of code blocks

Re: Desktop integration: Button to create menu links

2019-08-02 Thread Edward K. Ream
On Thu, Aug 1, 2019 at 11:55 PM Matt Wilkie wrote: Commit d0ad9f810 to devel adds a [add-desktop-links] button to > Desktop-integration.leo (under Settings menu). > The settings menu item looks good. I haven't tested the buttons withing DI.leo and have no opinion about them. You can fix

Re: Jeff R: What emacs features do you want?

2019-08-02 Thread Edward K. Ream
On Thu, Aug 1, 2019 at 8:03 PM Jeff R. wrote: Here are the reasons why I use emacs: [org mode and elisp]. > Thanks for this. It lead me to a big aha, which I'll describe in another post. 1. > > The benefit elisp is that, with just a bit of knowledge, I can write > custom functions on the fly,

ENB: building Leo into emacs org mode

2019-08-02 Thread Edward K. Ream
Something in the recent conversation with John R created several Ahas: *Aha 1:* There is no need to "invent" a Leonine gui for emacs: org mode's "gui" would suffice. *Aha 2: *Adding Leonine features to org mode would be a task for an Emacs Champion. *I have no plans to write the required

Re: Jeff R: What emacs features do you want?

2019-08-02 Thread Edward K. Ream
On Friday, August 2, 2019 at 7:19:47 AM UTC-5, Edward K. Ream wrote: Thanks for this. It lead me to a big aha, which I'll describe in another > post. > Here it is. Edward -- You received this message because you are