Re: [Off-topic?] Blog post about Grafoscopio and Jupyter

2017-11-20 Thread Matt Wilkie 
off-topic perhaps, but welcome :) Thanks Offray

On Mon, Nov 20, 2017 at 2:53 PM, Offray Vladimir Luna Cárdenas <
off...@riseup.net> wrote:

> Hi,
>
> Ideas about interactive computing and documentation has been discussed
> on this list. So I thought this like could be interesting for some
> members in this community:
>
> How the Results of Disruption Changes the Discussion Between Aficionados
> of Specific Languages and Environments
>
> https://medium.com/@dasein42/how-the-results-of-disruption-
> changes-the-discussion-between-aficionados-of-specific-languages-and-
> bd424b420f54
>
> Cheers,
>
> Offray
>
>
> --
> 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 it, send an
> email to leo-editor+unsubscr...@googlegroups.com.
> To post to this group, send email to leo-editor@googlegroups.com.
> Visit this group at https://groups.google.com/group/leo-editor.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

[Off-topic?] Blog post about Grafoscopio and Jupyter

2017-11-20 Thread Offray Vladimir Luna Cárdenas 
Hi,

Ideas about interactive computing and documentation has been discussed
on this list. So I thought this like could be interesting for some
members in this community:

How the Results of Disruption Changes the Discussion Between Aficionados
of Specific Languages and Environments

https://medium.com/@dasein42/how-the-results-of-disruption-changes-the-discussion-between-aficionados-of-specific-languages-and-bd424b420f54

Cheers,

Offray


-- 
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 it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

new Github [Pip] issues label for pip, pypi.org, setup.py

2017-11-20 Thread Matt Wilkie 
I created a new Github issues label named [Pip]. Use it for anything
related to `setup.py`, installing with `pip`, and/or the python package
index (PyPi: http://pypi.org)

-- 
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 it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Cleaning up the worst pep8 offenses

2017-11-20 Thread Matt Wilkie 
>
> For now, I think Leo's beautify commands are good enough.  Note that you
> can suppress these commands in individual nodes with @nobeautify.
>

Thanks for the reminder. I forgot they existed and had been doing things by
hand. ;-)

-- 
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 it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Cleaning up the worst pep8 offenses

2017-11-20 Thread Edward K. Ream 
On Mon, Nov 20, 2017 at 11:06 AM, jkn  wrote:

Just a general reminder for people (like me) who forget this sometimes: the
> scope of PEP-8 is quite limited:
>
>This document gives coding conventions for the Python code *comprising
> the standard library* in the main Python distribution
>

​Heh.  I never noticed this!​ This makes me very happy.

It does not recommend the style for your non-library code, although it is
> easy to see while people use it for that purpose. Perhaps a 'Leo Code Style
> Guide', with Edwards deviations from PEP-8, would be useful?
>

​The result of the beautify* commands could be called my recommended style.

Many thanks for giving us all a big loophole ;-)

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 it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Cleaning up the worst pep8 offenses

2017-11-20 Thread jkn 


On Monday, November 20, 2017 at 2:31:38 AM UTC, Edward K. Ream wrote:
>
>
>
> On Sun, Nov 19, 2017 at 5:09 PM, Terry Brown  > wrote:
>
>>
>>
>> > I have just created #584: clean up the worst pep8 offenses
>> > .
>> ​​
>>
>>
>> I occasionally fix PEP 8 things when I see them, missing spaces after
>> commas particularly bug me, but I like to keep those changes at least
>> within a file I'm changing anyway, if not within the part of the file
>> I'm changing.
>
>
> ​The beautify* commands will fix such things.
> ​
>
>> I feel that PEP-8 is seen as a place to start, not a set
>> of commandments that must be obeyed.  80 char line length is
>> particularly dated in today's monitor-scape.
>>
>> http://jakevdp.github.io/blog/2017/11/09/exploring-line-lengths-in-python-packages/
>
>
> ​I agree completely.​
>
> Hmm, I guess I don't see any harm in hunting PEP-8 things, but it
>> wouldn't be a priority for me.
>>
>
> ​I've just closed #584.  It turns out that the KeyHandlerClass class uses 
> mixedCase method names consistently.  True, there are other classes in 
> leoKeys.py that use the other way, but that kind of inconsistency can't be 
> helped now.
>
> Furthermore, I think that using the "reloadSettings" name in all classes 
> makes sense, because it creates a different kind of consistency.  
> Alternatively, we could replace all the reloadSettings methods using a 
> publish/subscribe pattern, but I see no urgent reason not the use the 
> reloadSettings pattern.
>
> In short, there are far bigger issues facing Leo than naming conventions 
> ;-)
>
> Edward
>

Just a general reminder for people (like me) who forget this sometimes: the 
scope of PEP-8 is quite limited:

   This document gives coding conventions for the Python code *comprising 
the standard library* in the main Python distribution

It does not recommend the style for your non-library code, although it is 
easy to see while people use it for that purpose. Perhaps a 'Leo Code Style 
Guide', with Edwards deviations from PEP-8, would be useful?

A-foolish-consistency-ly yours
Jon N

 

-- 
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 it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: viewrendered fails to load

2017-11-20 Thread Terry Brown 
On Mon, 20 Nov 2017 06:44:35 -0800 (PST)
Josef  wrote:

> Here is the log window.

Ah - looks like viewrendered's not loading :-}

Can you create a blank node in Leo, put

import leo.plugins.viewrendered

in the body, hit Ctrl-B, and post whatever shows up in the log when you
hit Ctrl-B?

Thanks, Terry

> BTW, on the old kubuntu setup viewrendered worked with the python2
> and PyQt4 that comes with kubuntu.
> I haven't got any other combination to work yet.
> This one is on my new xubuntu 16.4 installation, with python3
> installed via conda and PyQt5 installed via pip.
> The error message is always the same though, also with the other 
> combinations I tried.
> 
> Leo Log Window
> Leo 5.6, build 20171115141637, Wed Nov 15 14:16:37 CST 2017
> Git repo info: branch = master, commit = 44c0248da75f
> Python 3.6.3, PyQt version 5.9.2
> linux
> isPython3: True
> caching enabled
> setting leoID from os.getenv('USER'): 'dalcolmo'
> load dir: /home/dalcolmo/prog/leo-editor/leo/core
> global config dir: /home/dalcolmo/prog/leo-editor/leo/config
> home dir: /home/dalcolmo
> reading settings in 
> /home/dalcolmo/prog/leo-editor/leo/config/leoSettings.leo
> Using default leo file name:
> /home/dalcolmo/.leo/workbook.leo
> loadOnePlugin: can not load enabled plugin: leo.plugins.viewrendered
> reading settings
> in /home/dalcolmo/prog/leo-editor/leo/doc/CheatSheet.leo
> 
>  
> 

-- 
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 it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: viewrendered fails to load

2017-11-20 Thread Josef 
Here is the log window.
BTW, on the old kubuntu setup viewrendered worked with the python2 and 
PyQt4 that comes with kubuntu.
I haven't got any other combination to work yet.
This one is on my new xubuntu 16.4 installation, with python3 installed via 
conda and PyQt5 installed via pip.
The error message is always the same though, also with the other 
combinations I tried.

Leo Log Window
Leo 5.6, build 20171115141637, Wed Nov 15 14:16:37 CST 2017
Git repo info: branch = master, commit = 44c0248da75f
Python 3.6.3, PyQt version 5.9.2
linux
isPython3: True
caching enabled
setting leoID from os.getenv('USER'): 'dalcolmo'
load dir: /home/dalcolmo/prog/leo-editor/leo/core
global config dir: /home/dalcolmo/prog/leo-editor/leo/config
home dir: /home/dalcolmo
reading settings in 
/home/dalcolmo/prog/leo-editor/leo/config/leoSettings.leo
Using default leo file name:
/home/dalcolmo/.leo/workbook.leo
loadOnePlugin: can not load enabled plugin: leo.plugins.viewrendered
reading settings in /home/dalcolmo/prog/leo-editor/leo/doc/CheatSheet.leo

 

-- 
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 it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Cleaning up the worst pep8 offenses

2017-11-20 Thread Edward K. Ream 
On Sun, Nov 19, 2017 at 10:51 PM, Matt Wilkie  wrote:

> This passed off the port bow this evening: https://github.com/hayd/
> pep8radius. I like the approach, applying pep8 only in the vicinity of
> where one has recently been working.
>

​Interesting, and I like the demo.

For now, I think Leo's beautify commands are good enough.  Note that you
can suppress these commands in individual nodes with @nobeautify.

For the most part, though, I think there is lots more to life than pep 8 ;-)

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 it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Back to fixing bugs

2017-11-20 Thread Edward K. Ream 
On Thursday, November 16, 2017 at 10:54:19 AM UTC-6, Edward K. Ream wrote:

This filter 
> 
>  
> [is:issue is:open label:First label:Bug] shows that only 4 high-priority 
> bugs remain.  I would like to complete them all by Thanksgiving.
>

The filter now shows only two items, including a new item, #578: Support 
for org-mode tags on import. 



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 it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Rev 24da84a completes #327, letting local files unbind bindings

2017-11-20 Thread Edward K. Ream 
Rev 24da84a 

 
completes #327: Create a way to unbind bindings in leoSettings.leo 
.

The new code is relatively straightforward.  See the comments at the end of 
#327  for details.  
Please report any problems immediately. In particular, the new code should 
have no effect on user-defined mode bindings.

*Discussion*

This enhancement allows you to override bindings made in leoSettings.leo or 
myLeoSettings.leo by setting:

command-name = None

in the *local .leo file*, that is, outside of leoSettings.leo or 
myLeoSettings.leo.* Important*: binding:

do-nothing = 

does not work.  That would eat  entirely.  Instead, the new code calls 
k.handleUnboundKeys when it sees any key previously bound to command-name.

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 it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.