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

On Wed, Jun 19, 2019 at 10:08 PM Chris George wrote: > > setting leoID from os.getenv('USER'): 'chris' > Leo 6.0-b1, master branch, build 445dfa149e > 2019-06-18 09:45:56 -0500 > KCrash: crashing... crashRecursionCounter = 2 > > The exact same crash on starting Leo. > I would have been shocked

Re: Team Leo

On Wed, Jun 19, 2019 at 9:42 PM Zoom.Quiet wrote: > Wow... > but where are we come from? > suggest note in tail, > for show Leo 's global consequence ;-) > Good idea. I know where you and Vitalije come from, but I'm not sure of many others. I'll ask. Edward -- You received this message

Re: leo in emacs?

On Wed, Jun 19, 2019 at 10:29 PM Jeff Filipovits wrote: I recall seeing talk of using Emacs as a front end for, but now I cannot > find it in my old messages. > That's not going to happen. However, you can access Leo outlines using Leo's bridge. See this page

leo in emacs?

I tried Leo a few times and really liked it. Not a programmer, but have to sort a lot of information and academic writing. I read this list because I enjoy seeing the project development and enjoy Edward's leadership. I have moved off of Leo and now use Emacs, mostly for org-mode but also for

Re: Team Leo

On Wednesday, June 19, 2019 at 7:42:17 PM UTC-7, Zoom.Quiet wrote: > > Wow... > but where are we come from? > suggest note in tail, > for show Leo 's global consequence ;-) > > technatica Chris George Notch HIll, British Columbia, Canada -- You received this message because you are

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

setting leoID from os.getenv('USER'): 'chris' Leo 6.0-b1, master branch, build 445dfa149e 2019-06-18 09:45:56 -0500 KCrash: crashing... crashRecursionCounter = 2 The exact same crash on starting Leo. Chris On Wednesday, June 19, 2019 at 6:00:36 PM UTC-7, Edward K. Ream wrote: > > On

Re: specific layout

That's great, thanks Chris, it worked perfectly! On Wednesday, 19 June 2019 20:53:07 UTC+8, Chris George wrote: > > Hi Martin, > > There is a central dock widget. By default it is the Outline widget. The > central widget has limitations and forms the anchor for all other dock > widgets to be

Re: Team Leo

Wow... but where are we come from? suggest note in tail, for show Leo 's global consequence ;-) Edward K. Ream 于2019年6月20日周四 上午1:52写道： > > > > On Monday, June 17, 2019 at 6:48:31 AM UTC-5, Edward K. Ream wrote: >> >> The following people contributed significantly to Leo 6.0, via suggestions, >>

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

On Wednesday, June 19, 2019 at 7:59:10 PM UTC-5, Edward K. Ream wrote: For the first time *ever*, the doEnter code is sound... > Well, I forgot to mention that this post refers to the python_terminal plugin. Edward -- You received this message because you are subscribed to the Google Groups

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

Note: this rewrite has no chance of curing the segfaults (#1212 ) that can happen during *startup. *That project will wait until 6.1, or later. For the first time *ever*, the doEnter code is sound, and contains no egregious hacks: - It

Re: Lewis: please run Leo with --trace=startup and report the results

results added at #1209 -- 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

Re: Rev b937f02 in devel cures python_terminal segfaults

On Wed, Jun 19, 2019 at 1:02 PM Jacob Peck wrote: > I've been out of Leo development for a while now. But I'm sorry this > little plugin toy of mine is causing such huge issues. I'm surprised to > hear of segfaults in python, though. > That's hardly your fault. > FWIW, I never intended the

Re: Problem when trying to upgrade a version of Leo in an existing VE to Leo 6.0 beta 1

Hello Edward, Am Mittwoch, 19. Juni 2019 07:50:17 UTC+2 schrieb Edward K. Ream: > > On Wed, Jun 19, 2019 at 12:44 AM Viktor Ransmayr > wrote: > >> As I reported yesterday into the announcement thread of Leo 6.0 beta 1 >> installation into a **new** virtual environment using pip & PyPI is

Re: Rev b937f02 in devel cures python_terminal segfaults

Hi all, I've been out of Leo development for a while now.  But I'm sorry this little plugin toy of mine is causing such huge issues.  I'm surprised to hear of segfaults in python, though. FWIW, I never intended the plugin to be enabled by default -- it was just a quick proof of concept on

Lewis: please run Leo with --trace=startup and report the results

After pulling the latest version. I can't do anything more on #1209 until I hear from you. 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

On Monday, June 17, 2019 at 6:48:31 AM UTC-5, Edward K. Ream wrote: > > The following people contributed significantly to Leo 6.0, via > suggestions, code, testing or distribution help: > > Terry Brown > Josef Dalcolmo > Chris George > Bob Hossley > Rob Keeney > Виталије Милошевић (Vitalije

Re: Rev b937f02 in devel cures python_terminal segfaults

On Wednesday, June 19, 2019 at 12:03:03 PM UTC-5, Edward K. Ream wrote: > > On Wed, Jun 19, 2019 at 11:02 AM Chris George > wrote: > >> I was starting Leo. >> > > Whoa. That's totally unexpected. That's an important clue. > Important, but not hopeful. I had forgotten (if I ever knew) that

Re: Rev b937f02 in devel cures python_terminal segfaults

On Wed, Jun 19, 2019 at 11:02 AM Chris George wrote: > I was starting Leo. > Whoa. That's totally unexpected. That's an important clue. 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: vim-mode, cursor shape, vertical select

On Wed, Jun 19, 2019 at 11:23 AM gar wrote: > Thanks for that fast answer. > > By now I tried vim plugin. It's horribly unusable. The greatest disaster > that vim-open-file doesnt force vim to jump to the line of code outline > start's with. > You just get vim with file open on the first line.

Re: vim-mode, cursor shape, vertical select

Thanks for that fast answer. By now I tried vim plugin. It's horribly unusable. The greatest disaster that vim-open-file doesnt force vim to jump to the line of code outline start's with. You just get vim with file open on the first line. Great for 1 thousand lined files :-) vim-open-node

Re: Rev b937f02 in devel cures python_terminal segfaults

I was starting Leo. This is the exact same thing that happens every time I enable this plugin. I have seen this when using three different distributions over the past six months or so. The startup process never completes. I never see a widget or the mainwindow. Luckily I am getting real good

I'll work on python_terminal after all other 6.0 issues

Segfaults still happen on Linux. Clearly, this is a python bug. Segfaults should *never* happen in Python, outside of modules like Qt which are essentially thin wrappers around C code. That's not the case here, afaik. There are many other problems with this plugin. It's likely work will be

Re: Rev b937f02 in devel cures python_terminal segfaults

On Wed, Jun 19, 2019 at 10:38 AM Chris George wrote: > chris@technatica:~/leo-editor$ python3 ./launchLeo.py --trace=startup > > KCrash: crashing... crashRecursionCounter = 2 > ... > [1]+ Stopped python3 ./launchLeo.py --trace=startup > Well, that's too bad. Lot's of

Re: vim-mode, cursor shape, vertical select

On Wed, Jun 19, 2019 at 10:35 AM gar wrote: > Hello there! > > I have just started to learn Leo and trying to use it's vim mode. > > First what I miss of is different cursor shape for normal and insert modes. > I discovered 'vimmodeinsertborder*' settings but they seem do not work for > me - I

Re: Rev b937f02 in devel cures python_terminal segfaults

chris@technatica:~/leo-editor$ python3 ./launchLeo.py --trace=startup setting leoID from os.getenv('USER'): 'chris' reading settings in /home/chris/leo-editor/leo/config/leoSettings.leo reading settings in /home/chris/.leo/myLeoSettings.leo reading settings in

vim-mode, cursor shape, vertical select

Hello there! I have just started to learn Leo and trying to use it's vim mode. First what I miss of is different cursor shape for normal and insert modes. I discovered 'vimmodeinsertborder*' settings but they seem do not work for me - I cannot observe any difference whether they set or not.

Re: Rev b937f02 in devel cures python_terminal segfaults

On Wednesday, June 19, 2019 at 9:39:50 AM UTC-5, Edward K. Ream wrote: Imo, the resulting segfault must be a python bug somewhere, but I haven't > isolated it yet. > Er, probably not. Python may have been justified in reporting an "uncaught exception". Rev 76a235a now catches all exceptions

Rev b937f02 in devel cures python_terminal segfaults

When entering a blank line, the last_line var was unexpected assigned to [] instead of an empty string. Imo, the resulting segfault must be a python bug somewhere, but I haven't isolated it yet. Please test the python_terminal plugin and report any further troubles. Edward -- You received

Re: Use the bridge, Luke

On Wed, Jun 19, 2019 at 7:38 AM Terry Brown wrote: Ok, this script appends the outline headlines, indented, to the current > vim buffer: > Many thanks for this! I'll add this to scripts.leo and Leo's bridge chapter. Edward -- You received this message because you are subscribed to the

Re: specific layout

Hi Martin, There is a central dock widget. By default it is the Outline widget. The central widget has limitations and forms the anchor for all other dock widgets to be placed in relationship to it. To get the layout you want you need to change the central widget to the body widget. Add the

Re: Use the bridge, Luke

On Wed, 19 Jun 2019 00:52:54 -0500 "Edward K. Ream" wrote: > On Tue, Jun 18, 2019 at 6:27 PM Terry Brown > wrote: > > Then I'm not sure that there's really anything to do. Python's > > well integrated into vim, so you can just use leoBridge as usual. > > > Cool. > > > I guess I can do

specific layout

hello all, could someone help me? I've just moved to 6.0, from 5, and I'm trying to get a specific window layout, and I can't figure out how to do it! I want the right half of the screen to be body, top left quarter to be outline, and bottom left quarter to be tabs/find/log... In v5 I used to

Leo 6.0-final coming within a week

Rebecca and I will be leaving for vacation on Wednesday, June 26. Leo 6.0 final will go out the door before then, no matter what. Items on the 6.0 list will be reassigned to 6.1

Re: More reasons why Leo won't emulate pyzo

On Tuesday, June 18, 2019 at 1:49:24 PM UTC-5, Edward K. Ream wrote: It's important to complete the pyzo project as much as possible. As part of > this process, this post lists more reasons why I have no intention of ever > integrating pyzo into Leo. > Against all these (valid) reasons, there