Re: Summary of installation discussions

Edward, Saw your updates to LeoDocs "Installing everything with Anaconda or Miniconda" I still suggest including a heading as above "Install Leo using pip", and not merging it with the Anaconda/Miniconda topic. It will help users to see that pip and conda are separate package management tools.

Re: Matt, what's the status of #562?

> > ... (...just noticed a command mistake, fixing that shortly) > Done. Top post updated and also internal documentation notes with commit e1eae1f to leoDist.leo->Discussions->Matt's workflow for updating

Re: Matt, what's the status of #562?

> > I believe it's now only: >> >>- Someone besides Matt runs through process from start to finish and >>is successful ;-) >> >> ​I don't have any idea what "the process" is, or what it's supposed to do. > Oh! Well that's certainly a problem. :) > So, what I am asking is for a revision

Log hyperlinks for syntax errors

I've added log hyperlinks to jump to syntax errors (in Python code). I reduced the number of context lines a bit, seeing you don't need the context to find the error any more. I may have changed the reported line numbers. They now agree with what Python would report from the command line, not

Please proofread Leo's new Tips page

It's here . All corrections and suggestions welcome. The more I think about this tips page, the better I like it. I combines the best features of the FAQ, in a more guided way. This version of the tips have links to tutorial pages, so some people

Re: A new "Tips" tutorial

On Friday, January 26, 2018 at 6:44:02 AM UTC-6, Edward K. Ream wrote: This is in LeoDocs.leo, but I have not yet been able to upload it to Leo's > web site. > It's up now here . For those contemplating the effort required to learn Leo scripting, the

Re: Matt, what's the status of #562?

On Fri, Jan 26, 2018 at 12:01 AM, Viktor Ransmayr wrote: > > It's not clear to me, if you are interested in the user- or the developer >>> view on the status of this issue? >>> >> >> ​Both. I have no idea what this project attempts to do, how to describe >> it to

Re: NEW: geotag.py

On Fri, Jan 26, 2018 at 3:43 AM, lewis wrote: > TypeError: a bytes-like object is required, not 'str' > > I found this at stackoverflow: In Python 3 (but not in Python 2), str and > bytes are distinct types that can't be mixed. You can't write a str > directly to a

Re: Guide to using g.pdb()

On Thu, Jan 25, 2018 at 10:19 PM, lewis wrote: In the geotag.py plugin I added g.pdb() > > import leo.core.leoGlobals as g > g.pdb() > > But when I start Leo it is stuck with cursor showing (Pdb). > ​Good start ;-) This section

A new "Tips" tutorial

This is in LeoDocs.leo, but I have not yet been able to upload it to Leo's web site. Imo, this is an important improvement, allowing users to see tips all at once, and organized by topic. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group.

a24aedb: New script helpers for tips and github issues

Rev a24aedb is missing a proper checkin comment. Here it is: Added scripts to get issues and tips to Leo's core: leoGlobals.py: Added g.getGitIssues and GitIssueController class. leoTips.py: Added make_tip_nodes top-level function. These now appear in LeoDocs.leo: @button get-tips # Creates

Re: NEW: geotag.py

TypeError: a bytes-like object is required, not 'str' I found this at stackoverflow: In Python 3 (but not in Python 2), str and bytes are distinct types that can't be mixed. You can't write a str directly to a socket; you have to use bytes. But my python is extremely basic and I'm way out of