New Themes

Two new themes are available in leo/themes: BreezeDark2 and Zepyhr Dark. An update to Breeze Dark to accomodate dock widgets and refresh the look. A new dark theme, Zephyr, based on Breeze Dark (that was a lot of work) with a new colour scheme and a few new wrinkles. Feedback is required.

Re: Kent and Ville: you're always part of the team

On Thu, Jun 20, 2019 at 1:08 PM Kent Tenney wrote: > Absolutely! > Proud to be from Ashland WI, Bayfield county, Barksdale township. > Thanks. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop

Re: Team Leo: where are you from?

On Thu, Jun 20, 2019 at 1:30 PM Chris George wrote: > https://www.mapcustomizer.com/map/Team%20Leo > The world-wide Team Leo. Thanks. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving

Re: Leo 6.0 requires Python 3.6 or later

I was breaking the line at a different place. Now it works following your example. However, it doesn't accept Leo command line arguments, but for now let's leave it at that and perhaps I'll start a new thread on that subject. Thanks for your help! Rob... On Thursday, June 20, 2019 at 4:49:21

Re: Leo 6.0 requires Python 3.6 or later

On Thu, 20 Jun 2019 13:26:53 -0700 (PDT) Rob wrote: > Needs to be on the same line. However, I get this error: I just tested it and it worked for me using two lines. Here's my exact leo.bat: call c:\Users\TBrown02\local\mc2\Scripts\activate.bat c:\Users\TBrown02\local\mc2\envs\leo python

Re: Leo 6.0 requires Python 3.6 or later

Needs to be on the same line. However, I get this error: D:\Utility Apps\Leo Resources>echo off activate does not accept more than one argument: ['C:\\Users\\rob_iawac46\\.conda\\envs\\leo', 'python', 'D:\\Synced\\github repos\\leo\\launchLeo.py'] Looks like I can't pass the script file as an

Re: Leo 6.0 requires Python 3.6 or later

On Thu, 20 Jun 2019 12:19:10 -0700 (PDT) Rob wrote: > Doesn't work, perhaps I'm not understanding something. > >1. I created an Anaconda environment (leo) which includes Python > 3.7 and PyQt (among other things). >2. I created the following batch file (paths match my file paths). > >

Re: Leo 6.0 requires Python 3.6 or later

Doesn't work, perhaps I'm not understanding something. 1. I created an Anaconda environment (leo) which includes Python 3.7 and PyQt (among other things). 2. I created the following batch file (paths match my file paths). echo off CALL C:\ProgramData\Anaconda3\Scripts\activate.bat

Re: Team Leo: where are you from?

https://www.mapcustomizer.com/map/Team%20Leo -- 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

Re: Kent and Ville: you're always part of the team

Absolutely! Proud to be from Ashland WI, Bayfield county, Barksdale township. On Thu, Jun 20, 2019 at 8:46 AM Edward K. Ream wrote: > Ok to tell people where you are from? > > Edward > > -- > You received this message because you are subscribed to the Google Groups > "leo-editor" group. > To

Re: Leo 6.0 requires Python 3.6 or later

Looks like you'd need something along these lines: https://stackoverflow.com/questions/42602024/windows-shortcut-to-run-python-script-in-anaconda-command-prompt replacing "jupyter lab" with "python c:\some\path\to\launchLeo.py". Not knowing your skill set let me know if more detail woudl be

ENB: Leo's past and future

This Engineering Notebook post discusses trade-offs (unpleasant choices) that I have been considering lately. The purpose of this post is to acknowledge these choices and to move on. I am committing to nothing here. The larger purpose is to free myself from the grip of urgent tasks so that I

Re: specific layout

The Tabs dock widget is nested with the Body dock widget. Set the @string setting to outline instead of body and restart. Then unnest the Tabs dock widget by selecting it and dragging it to its own position (not nested). Then change the central widget back to body and restart Leo. The central

Re: Leo 6.0 requires Python 3.6 or later

Thanks, Terry. I was able to launch Leo from an Anaconda shell. How do I translate that to a Windows shortcut like I had before? Rob... On Thursday, June 20, 2019 at 1:22:19 PM UTC-4, Terry Brown wrote: > > I think activating an Anaconda environment requires more steps. Easiest > way for

Re: Leo 6.0 requires Python 3.6 or later

I think activating an Anaconda environment requires more steps. Easiest way for testing is to launch the Anaconda shell from the start menu. If your ultimate goal is launching from an icon there are more steps, but initial testing the shell's the way to go. Cheers -Terry On Thu, Jun 20, 2019

Re: specific layout

[image: BrokenLayout.png] I applied your recipe and got some strange layout where LOG pane & friends became totally unreachable and invisible. How to restore them back? And how this became possible at all? среда, 19 июня 2019 г., 15:53:07 UTC+3 пользователь Chris George написал: > > Hi

Re: Leo 6.0 requires Python 3.6 or later

PS D:\Synced\github repos\leo> c:\ProgramData\Anaconda3\python.exe launchLeo.py Traceback (most recent call last): File "launchLeo.py", line 7, in import leo.core.runLeo File "D:\Synced\github repos\leo\leo\core\runLeo.py", line 27, in import leo.core.leoApp as leoApp File

Re: How to customize look?

On Thu, Jun 20, 2019 at 11:24 AM gar wrote: > Thanks a lot, Chris! You recipe just worked. But it isn't obvious for me > though. > > Edward, I believe that this should be written in the docs. It shouldn't be > THAT hard to just change the font size > You're right. It's on the list for 6.0.

Re: How to customize look?

Thanks a lot, Chris! You recipe just worked. But it isn't obvious for me though. Edward, I believe that this should be written in the docs. It shouldn't be THAT hard to just change the font size четверг, 20 июня 2019 г., 18:55:31 UTC+3 пользователь Chris George написал: > > HI Gar, > >

Re: How to customize look?

On Thu, Jun 20, 2019 at 10:40 AM gar wrote: > Strange... My settings contain (for example) @string font-size-body = 12px > But when I dump all the settings via menu command I see that: [F] @string > fontsizebody = 22px > Got no idea what does that mean and why does it go in this way. > The [F]

Re: Leo 6.0 requires Python 3.6 or later

On Thu, Jun 20, 2019 at 10:58 AM Rob wrote: > Now I can't run Leo at all. > > Any ideas on what to try next? > Open a console first. Then run python from the console. That way the console will remain open and you can see what went wrong. Edward -- You received this message because you

Re: Leo 6.0 requires Python 3.6 or later

Now I can't run Leo at all. 1. Had Python 3.4 on Windows (Leo worked fine). 2. Updated latest Git version of Leo as usual. 3. After error attempting to launch Leo (needs Python 3.6 or above), I installed Anaconda 64 bit. This includes Python 3.7 and PyQt5 by default. 4. Set path

Re: How to customize look?

HI Gar, Here is how I use themes. In the directory leo-editor/leo/themes are a number of theme files. These can be loaded using the File, Open Outline menu option in Leo. Opening an outline automatically loads it. Keep opening outlines until you find one you like. Then close all of the theme

Re: How to customize look?

Strange... My settings contain (for example) @string font-size-body = 12px But when I dump all the settings via menu command I see that: [F] @string fontsizebody = 22px Got no idea what does that mean and why does it go in this way. It seems strange to me to spend hours debugging setup of font

How to customize look?

I'm trying to customize Leo for my likings. First of all I took a theme and placed it's name into appropriate setting of myLeoSettings project. Ok, it applied, but font size is so huge that all texts run out of my screen. Ok. I added a setting for base font size. It didnt work. Fonts remained

Re: Team Leo: where are you from?

周琦 (ZoomQuiet) made the excellent suggestion that we highlight the global nature of Team Leo. > >> If you are comfortable doing so, please tell me where you are from. Here >> is the present list. I know, or can guess, some locations, but I won't >> reveal them unless it's ok with you,

Re: Rev 81a2f1e: A rewrite of PyInterp.doEnter & helpers

Good thing. Exact same crash as before. Chris On Thu, Jun 20, 2019 at 6:35 AM Edward K. Ream wrote: > > > On Thursday, June 20, 2019 at 8:23:55 AM UTC-5, Edward K. Ream wrote: > > The second comment in #1212 >> [defines] the >>

Re: Team Leo: where are you from?

> > Виталије Милошевић (Vitalije Milosevitch) > I live in Serbia. Vitalije -- 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 6.0 requires Python 3.6 or later

Nobody has complained about this, so I assume everyone has already gotten the message. I am not willing to support python 3.5 or earlier. Imo, the early versions of python 3 were dogs. *Details* The startup code uses g.minimum_python_version (The string '3.6') and raises an emergency

Kent and Ville: you're always part of the team

Ok to tell people where you are from? 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

Re: Use the bridge, Luke

On Thursday, June 20, 2019 at 8:36:34 AM UTC-5, Josef wrote: > > > Support for vim-script may add additional functionality if it would > support vim plugins, as there are many available. For me, there are > currently just a few reasons for using vim in parallel to Leo: vim starts > up fast,

Re: Use the bridge, Luke

Support for vim-script may add additional functionality if it would support vim plugins, as there are many available. For me, there are currently just a few reasons for using vim in parallel to Leo: vim starts up fast, has syntax highlighting for just about anything with good print support,

Re: Rev 81a2f1e: A rewrite of PyInterp.doEnter & helpers

On Thursday, June 20, 2019 at 8:23:55 AM UTC-5, Edward K. Ream wrote: The second comment in #1212 > [defines] the > InteractiveInterpreter class...at the module level. > Rev 62dac98 does the same for the actual plugin. This is the first

Re: Team Leo: where are you from?

Hello Edward, Am Do., 20. Juni 2019 um 14:57 Uhr schrieb Edward K. Ream : > > 周琦 (ZoomQuiet) made the excellent suggestion that we highlight the global > nature of Team Leo. > > If you are comfortable doing so, please tell me where you are from. Here is > the present list. I know, or can

Re: Rev 81a2f1e: A rewrite of PyInterp.doEnter & helpers

On Thursday, June 20, 2019 at 8:14:32 AM UTC-5, Edward K. Ream wrote: I revised the second comment in #1212 so that the InteractiveInterpreter class is defined at the module level. Now things are a bit more sane. Does QTextEdit use

Re: Team Leo: where are you from?

On Thursday, June 20, 2019 at 2:57:37 PM UTC+2, Edward K. Ream wrote: > > 周琦 (ZoomQuiet) made the excellent suggestion that we highlight the global > nature of Team Leo. > > If you are comfortable doing so, please tell me where you are from. Here > is the present list. I know, or can guess,

Re: Rev 81a2f1e: A rewrite of PyInterp.doEnter & helpers

On Thursday, June 20, 2019 at 8:02:35 AM UTC-5, Edward K. Ream wrote: The second comment in #1212 > now contains a > test program. Please run it with python and report your experiences. > Strange things happen for me on Windows. > Hmm.

Re: Rev 81a2f1e: A rewrite of PyInterp.doEnter & helpers

On Thu, Jun 20, 2019 at 7:11 AM Edward K. Ream wrote: >> from rlcompleter import Completer >> Well done. I'll take a look. Googling rlcompleter segfault produces several hits. Some of the bugs are supposedly fixed. Let's see if we can nail down where the segfault actually happens. The

Team Leo: where are you from?

周琦 (ZoomQuiet) made the excellent suggestion that we highlight the global nature of Team Leo. If you are comfortable doing so, please tell me where you are from. Here is the present list. I know, or can guess, some locations, but I won't reveal them unless it's ok with you, surveillance being

Re: Team Leo

G'day Mate ;) Lewis Sydney, Australia -- 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

Re: Rev 81a2f1e: A rewrite of PyInterp.doEnter & helpers

It is definitely rlcompleter causing the problem. Chris -- 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

Re: Team Leo

Rob Keeney Suwanee, GA, USA (near Atlanta, GA) -- 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,

Re: Rev 81a2f1e: A rewrite of PyInterp.doEnter & helpers

On Thu, Jun 20, 2019 at 6:47 AM Chris George wrote: > Bingo! > > from rlcompleter import Completer > > This is an import that is unique to the plugin. > > When I comment it out, Leo starts just fine and I even get a python > console. > Well done. I'll take a look. Edward -- You received

Re: Rev 81a2f1e: A rewrite of PyInterp.doEnter & helpers

On Thu, Jun 20, 2019 at 6:31 AM Chris George wrote: > > BTW, can you send a copy of Leo's log pane when you *aren't* crashing. >> I'm guessing it's some Linux flavor, but I'd like to know the details. >> >> > Leo 6.0-b2-devel, devel branch, build 0e86a7bf76 > 2019-06-19 21:25:33 -0500 > Python

Re: Rev 81a2f1e: A rewrite of PyInterp.doEnter & helpers

> BTW, can you send a copy of Leo's log pane when you *aren't* crashing. > I'm guessing it's some Linux flavor, but I'd like to know the details. > > Leo 6.0-b2-devel, devel branch, build 0e86a7bf76 2019-06-19 21:25:33 -0500 Python 3.6.8, PyQt version 5.12.3 linux > It's time to start