Re: rev 3b6b820c: first crack at pip install docs

Leo's documentation at http://leoeditor.com/installing.html now has an obsolete link at Installing Leo > Installing packages Download PyQt5 from http://www.riverbankcomputing.com/software/pyqt/download5. It seems the PyQt webpage has been recently updated. The link for PyQt5 via the

Re: Refresh of recommended plugins

By digging around in system leoSettings.leo I see that an empty user settings file is populated by copying @enabled_plugins from system settings (wish: easy show me what's different between default new user profile and mine). The plugin list in system settings file seems out of date (leo_cloud is

Refresh of recommended plugins

My myLeoSettings.leo file is now years old and there's a lot of stuff in there that is no longer as relevant and sometimes at cross purposes to today's best practices. Of particular interest to me today are plugins. What are the current best/favourite/recommended plugins you use? And conversely,

The console gui is ready for prime time

#509 is almost complete. The highlights of recent work: 1. The label *above* the minibuffer now contains the present state. For example, after Ctrl-F the label is: Mini-buffer: Search: indicating that a search string is expected. 2.

Re: settings reloaded :-)

> > Wha? sync across machines?? more more, tell me more about this > > @leo_cloud thing! > > Hmm, I did write a thing to extract plugin docstrings into the docs., > maybe we should make that go again. Anyway: > > https://groups.google.com/d/msg/leo-editor/46tA_ItS1Xg/4n5GFnymAwAJ > Thanks!

Re: rev 3b6b820c: first crack at pip install docs

thank you Lewis, that would be much appreciated. :) I continually struggle with how to balance level of detail between anemic and overwhelming. ​ -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving

Re: NEW: cloud storage plugin for Leo

On Wed, 18 Oct 2017 08:51:07 -0500 "Edward K. Ream" wrote: > On Sun, Sep 24, 2017 at 3:40 PM, Terry Brown > wrote: > > The new leo_cloud plugin allows subtrees within a .leo file to be > > stored in the cloud. > > > ​Rev cd45289 adds a mention of

Re: settings reloaded :-)

On Thu, 30 Nov 2017 20:55:33 -0800 Matt Wilkie wrote: > > Heh, so @leo_cloud nodes allow my settings to stay in sync. across > > the four machines I use Leo on, and... > > > > Wha? sync across machines?? more more, tell me more about this > @leo_cloud thing! > > "Your

Re: rev 3b6b820c: first crack at pip install docs

I'll try and squeeze some time from the weekend and slap on my user's hat Lewis On Friday, December 1, 2017 at 9:54:54 PM UTC+11, Edward K. Ream wrote: > > > Instead, the remarks should be folded into the node: > > @rst html/installing.html-->Installing packages > > This is not a trivial

Re: rev 3b6b820c: first crack at pip install docs

On Thursday, November 30, 2017 at 10:59:27 PM UTC-6, Matt Wilkie wrote: ok, in future I'll do that. For this time see .../leo/doc/LeoDocs.leo#Leo's > Documentation-->Installing & running Leo-->@rst html/quick.html > Imo, putting instructions in a separate section would slow users down. Worse,

Re: Wrapping up the console gui

On Thu, Nov 30, 2017 at 11:37 PM, lewis wrote: > Excellent work. > > IMO the order for the paragraphs should be: > Limitations > Broadcasting and listening > Developing the cursesGui2 plugin > ​This is debatable, but I have gone with it. It's now up on the web. All

Re: rev 3b6b820c: first crack at pip install docs

On Friday, December 1, 2017 at 3:36:02 AM UTC-6, Edward K. Ream wrote There are three nodes in the "quick" tree. Imo, all three nodes must have > some introductory words succinctly explaining what is being discussed. This > is not easy to do. Lewis, do you have any suggestions? > Also, the

Re: rev 3b6b820c: first crack at pip install docs

On Thu, Nov 30, 2017 at 10:59 PM, Matt Wilkie wrote: > > ​Where are the new docs? In future, it would be easiest to put clone new >> nodes as the last top-level nodes of LeoDocs.leo That way devs and >> interested users can see at a glance what has changed. >> > > ok, in