Re: Using dead keys with QT5?

[Arjan]

Hm, after some further tries it seems doing to opposite works, 
`QT_IM_MODULE=compose launchLeo.py` (instead of my default on ubuntu 14.04, 
where $QT_IM_MODULE=ibus).

Strange but good enough for me.

All best,

Arjan

On Sunday, January 29, 2017 at 1:27:39 PM UTC+1, Edward K. Ream wrote:
>
> ​​On Sat, Jan 28, 2017 at 5:29 PM, Arjan  wrote:
> 
> > I found this QT bug report for the problem: 
> https://bugreports.qt.io/browse/QTBUG-56452.
> ...
> > Any ideas what else to try?
>
> Define Leo abbreviations:
> 
> e/;;=​é
> e\;;=è
>
> HTH.
>
> 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: The color branch has been merged into master

['Terry Brown' via leo-editor]

You can use your regular git repo. dir as long as you don't modify 
...\leo\config\leoSettings.leo, which I don't imagine you do if you're using 
git.
How it's supposed to work:
set HOME=N:\scratch\delete\home

make Windows think you're home folder's N:\scratch\delete\home, so it doesn't 
see any changes you've made in your regular %HOME%\.leo\myLeoSettings.leo.  
N:\scratch\delete\home should be a folder which exists, but is completely empty 
(delete it and recreate it if unsure).
then for
python N:\local\leo-editor\launchLeo.py
you should just replace N:\local\leo-editor\ with where ever your launchLeo.py 
is, i.e. where ever your git repo. clone is.  So it will read the 
leoSetting.leo that comes with Leo, but not your local modifications.
Cheers -Terry




 
  From: lewis 
 To: leo-editor  
Cc: terry_n_br...@yahoo.com
 Sent: Monday, January 30, 2017 3:22 PM
 Subject: Re: The color branch has been merged into master
   
N:\>set HOME=N:\scratch\delete\home

N:\>python N:\local\leo-editor\launchLeo.py
python: can't open file 'N:\local\leo-editor\launchLeo.py': [Errno 2] No such 
file or directory

This didn't work for me. Wouldn't I need to have a new copy of Leo different 
than my usual git repo? 

Lewis

On Tuesday, January 31, 2017 at 3:26:27 AM UTC+11, Terry Brown wrote:
Can you try running Leo like this:
mkdir d:\scratch\delete\home
set HOME=d:\scratch\delete\home
python d:\local\leo-editor\launchLeo. py

(with whatever path suits instead of d:\scratch\delete\home of course)
that's how I launch when I want to see default behavior.
-- 
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.

Re: The color branch has been merged into master

[lewis]

I disabled myLeoSettings so now I'm running default Leo. The body pane 
background is white, and the operators are black. 

Just a reminder that the theme system is broken. See issue 350 


Regards
Lewis

-- 
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: The color branch has been merged into master

[lewis]

N:\>set HOME=N:\scratch\delete\home

N:\>python N:\local\leo-editor\launchLeo.py
python: can't open file 'N:\local\leo-editor\launchLeo.py': [Errno 2] No 
such file or directory

This didn't work for me. Wouldn't I need to have a new copy of Leo 
different than my usual git repo? 

Lewis

On Tuesday, January 31, 2017 at 3:26:27 AM UTC+11, Terry Brown wrote:
>
> Can you try running Leo like this:
>
> mkdir d:\scratch\delete\home
> set HOME=d:\scratch\delete\home
> python d:\local\leo-editor\launchLeo.py
>
> (with whatever path suits instead of d:\scratch\delete\home of course)
>
> that's how I launch when I want to see default behavior.
>

-- 
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: The color branch has been merged into master

['Terry Brown' via leo-editor]

Can you try running Leo like this:
mkdir d:\scratch\delete\home
set HOME=d:\scratch\delete\home
python d:\local\leo-editor\launchLeo.py

(with whatever path suits instead of d:\scratch\delete\home of course)
that's how I launch when I want to see default behavior.
For me for @language python current trunk 
Leo 5.4, build 20170129073103, Sun Jan 29 07:31:03 CST 2017Git repo info: 
branch = master, commit = 1c28e916c371Python 2.7.5, PyQt version 4.8.5Windows 7 
AMD64 (build 6.1.7601) SP1
looks quite different - body pane background is white, the operators you 
mention are black.
Of course our Windows, Python, and Qt versions all differ.
Cheers -Terry
 
  From: lewis 
 To: leo-editor  
 Sent: Monday, January 30, 2017 7:52 AM
 Subject: Re: The color branch has been merged into master
   
The default colours present many characters as very low contrast and are 
virtually unreadable. 
See attached pic with an example using @language python. The = character is 
almost invisible. Math operators and % are also affected.

I don't think this has anything to to with the new colorizer, but worth 
reporting. I'm almost certain I'm using default and haven't changed any 
settings.

Leo 5.4, build 20170129073103, Sun Jan 29 07:31:03 CST 2017
Git repo info: branch = master, commit = 1c28e916c371
Python 3.6.0, PyQt version 5.7.1
Windows 10 AMD64 (build 10.0.14393) SP0

Lewis


On Sunday, January 29, 2017 at 11:42:36 PM UTC+11, Edward K. Ream wrote:
All appears to have gone smoothly. Please report any problems.

-- 
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.

Python parsing issue

[Kent Tenney]

commit 1c28e916c37153df427e93c8cb97b635f58f5cbd
declaration appended to class definition, this looks like a bug.

a minimal version of what I'm seeing, file test.py:
###
import sys

class Foo():
pass

def __init__(self):
pass

if __name__ == '__main__':

'''
>>> print('ok?'')

'''

print('__main__')


###

When the above is added to a Leo file via @auto test.py,
the parsed version shows in the 'Declarations' node:
import sys

and shows in the 'Class foo' node:

class Foo():

 pass

 @others

if __name__ == '__main__':


 '''

 >>> print('ok?')

 '''


 print('__main__')


Thanks,

Kent

-- 
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: The demo branch and plugin

[Edward K. Ream]

On Monday, January 30, 2017 at 8:53:35 AM UTC-6, Edward K. Ream wrote:

> The plugin no longer alters Leo's key handling in any way.

As a result, I'll probably merge the demo branch into master later today.

All the remaining work will happen in the plugin itself, or LeoDocs.leo.  
That being so, there is no reason to use a separate branch. On the 
contrary, doing the work in master could avoid problems with updating 
LeoDocs.leo.

EKR

-- 
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: The demo branch and plugin

[Edward K. Ream]

On Sunday, January 29, 2017 at 9:40:49 PM UTC-6, Edward K. Ream wrote:

*tl;dr:* Read the summary.

The plugin is ready for preliminary testing. I have tested the basic logic 
(the demo-next command), but not the helpers. The adventurous are invited 
to give it a go. The demo.py docs 
 should 
be accurate and up-to-date. 

The demo.py plugin has seen a spectacular collapse in complexity. The demo 
plugin is now clearly the simplest thing that could possibly work. The 
collapse happened for several reasons:

1. The plugin no longer alters Leo's key handling in any way.  As a result, 
presenters should create a key binding for demo-next.

2. *Demo scripts must handle all complications*.  This should work well in 
practice.  And it makes sense.  If a presenter wants to do something fancy, 
that should be her concern, not the plugin's. The undo section of the docs 
 
discusses the new philosophy.

3. There is no demo-back command. In an emergency, presenters can use Leo's 
existing undo, with the caveats discussed in the undo section.

*Summary*

The plugin is ready for *preliminary *testing. Helpers are untested.

Demo scripts are responsible for all complications, including undo.  There 
is no demo-back command.

The demo.py docs 
 are 
better than ever before. They follow the "less said the better" principle.

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: The color branch has been merged into master

[Edward K. Ream]

On Monday, January 30, 2017 at 7:52:51 AM UTC-6, lewis wrote:
 

> The default colours present many characters as very low contrast and are 
> virtually unreadable. 
>

The screenshot looks more like Tk than Qt.

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: The color branch has been merged into master

[lewis]

The default colours present many characters as very low contrast and are 
virtually unreadable. 
See attached pic with an example using @language python. The = character is 
almost invisible. Math operators and % are also affected.

I don't think this has anything to to with the new colorizer, but worth 
reporting. I'm almost certain I'm using default and haven't changed any 
settings.

Leo 5.4, build 20170129073103, Sun Jan 29 07:31:03 CST 2017
Git repo info: branch = master, commit = 1c28e916c371
Python 3.6.0, PyQt version 5.7.1
Windows 10 AMD64 (build 10.0.14393) SP0

Lewis


*On Sunday, January 29, 2017 at 11:42:36 PM UTC+11, Edward K. Ream wrote:*
>
> *All appears to have gone smoothly. Please report any problems.*
>

-- 
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.