Re: Terry, let's make leoserver great

On Fri, Feb 16, 2018 at 2:17 PM, Terry Brown wrote: I'd just do > ​ ​ > response = {'answer': repr(answer)} > ​ ​ > unconditionally, ​That helped. ​ ​Rev 3bf2c2a contains cleaned up code, and converts two files to @file, for more consistent viewing. Evaluating repr(g)

Re: Terry, let's make leoserver great

On Fri, 16 Feb 2018 12:05:36 -0800 (PST) "Edward K. Ream" wrote: > On Friday, February 16, 2018 at 1:59:49 PM UTC-6, Edward K. Ream > wrote: > > Rev 79d92fa contains the present code. Can you see anything amiss? > > > > How weird. "2" evaluates and shows correctly, but

Re: Terry, let's make leoserver great

On Fri, 16 Feb 2018 14:11:03 -0600 Terry Brown wrote: > On Fri, 16 Feb 2018 11:59:49 -0800 (PST) > "Edward K. Ream" wrote: > > > Rev 79d92fa contains the present code. Can you see anything > > amiss? > > Push? > > Cheers -Terry Doh, wrong

Re: Terry, let's make leoserver great

On Fri, 16 Feb 2018 11:59:49 -0800 (PST) "Edward K. Ream" wrote: > Rev 79d92fa contains the present code. Can you see anything amiss? Push? Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe

Re: Terry, let's make leoserver great

On Friday, February 16, 2018 at 1:59:49 PM UTC-6, Edward K. Ream wrote: Rev 79d92fa contains the present code. Can you see anything amiss? > How weird. "2" evaluates and shows correctly, but repr(g) evaluates correctly but shows nothing(!!) Edward -- You received this message because you

Re: A Recent Article by Me

Chris, that's a great article! Much of that mirrors how I use and benefit from Leo. I do some HTML and CSS stuff, but 90+% of my time in Leo is either writing in LaTEX or Markdown. Good stuff! Rob... On Thursday, February 15, 2018 at 2:50:11 PM UTC-5, Chris George wrote: > >

Re: Terry, let's make leoserver great

On Friday, February 16, 2018 at 1:20:43 PM UTC-6, Edward K. Ream wrote: Hmm. I've tried the obvious things with no joy. Rev 79d92fa contains the present code. Can you see anything amiss? Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group.

Re: Terry, let's make leoserver great

On Friday, February 16, 2018 at 12:29:42 PM UTC-6, Terry Brown wrote: Hmm, my first thought was call json.dumps with a default kwarg. > https://docs.python.org/2/library/json.html#basic-usage like > def default(obj): > return str(obj) > > but on second thoughts probably makes sense to

Re: Terry, let's make leoserver great

On Fri, 16 Feb 2018 09:38:27 -0800 (PST) "Edward K. Ream" wrote: > File "c:\Anaconda3\lib\json\encoder.py", line 180, in default > o.__class__.__name__) > TypeError: Object of type 'module' is not JSON serializable > > Terry, how would you go about fixing this? Hmm, my

Terry, let's make leoserver great

I am playing with your leoserver stuff . I want to understand this code thoroughly. Lots of questions and comments. 1. Reminder: to get the link to a comment, you click on the link (x days ago) at the start of the

Re: A Recent Article by Me

On Thu, Feb 15, 2018 at 7:05 PM, Chris George wrote: > It was a paid piece. They bought all the digital rights. > > A quote and a link to the article would be "fair use" though. > ​I've updated this page

Rev b2e638b uses changes from LeoDocs-matt1.leo

The changes are minimal, and affect only the node Installing Leo with pip. It would have been easier to propose the new text directly, but then Leo wouldn't have the diff-leo-files and diff-and-open-leo-files commands ;-) Edward -- You received this message because you are subscribed to the

Re: 1d3e6bc: The CompareLeoOutlines class for comparing .leo files

On Monday, February 12, 2018 at 1:58:57 AM UTC-6, Edward K. Ream wrote: > > *Comparing documentation is still hard* > > ...Documentation can only be evaluated by looking at the entire outline. > Diffs just fragment the "viewing experience". So you could say that, *for > documentation only*,

Two back burner enhancements related to rust

The following two items are on the back burner now that I'm not going to rewrite everything in rust: 1. python2rust.py suggests a script for munging python files into something that looks more like rust. 2. Hooks for munging external files

Re: 2018 will be a momentous year for Leo

On Thu, Feb 15, 2018 at 9:14 PM, Jacob MacDonald wrote: Rust has some really nice ergonomics for dealing with data structures. The > possibility of interfacing with Python to implement core data functions in > a faster and safer way is very interesting. Looks like I'll be

Re: 2018 will be a momentous year for Leo

On Fri, Feb 16, 2018 at 5:48 PM, Edward K. Ream wrote: > On Thu, Feb 15, 2018 at 1:21 PM, Terry Brown wrote: > >> > Given the relatively small amount of code involved, we might >> > seriously consider rewriting Leo's core assets in javascript or even

Re: 2018 will be a momentous year for Leo

On Thu, Feb 15, 2018 at 1:21 PM, Terry Brown wrote: > Given the relatively small amount of code involved, we might > > seriously consider rewriting Leo's core assets in javascript or even > > rust. > > I think is some ways the issue is not so much web ui vs. Qt UI, but >

ENB: Why python will remain Leo's future

Rewriting Leo's core is out of the question. Python is: - Best for users as the simplest and most flexible scripting language. - Dynamic. Imagine doing @button in rust. - The basis for Leo's API. Instead, Leo can and should add support for the rust language #727

Re: Error starting Leo: 'NoneType' object has no attribute 'QObject'

Hi there. I may be able to help. I am running Debian Stretch (64 bit) and hit exactly the same issue. However, once I identified the root issue the solution was simple. The root issue is that by default Debian Stretch installs Python version 2 as well as Python version 3. My system only had