Re: No vim or pyzo bridges for Leo

2020-04-09 Thread Thomas Passin
I think you are looking at the wrong level. You are writing in terms of implementation, but what is ti about vim that you expect to do in Leo, and why do think Leo has something to offer an experienced vim user? Note that I'm writing as a non-vim user, so my ideas about its usefulness are

Re: No vim or pyzo bridges for Leo

2020-04-09 Thread gar
I dont see any other opportunities but to re-design Leo, leave all the features but change all the mechanics. Let me give an example. Let it be the problem of code navigation. Far away from the start of the epoch editors did it themselves: parsers, regexps, strange approaches. I keep remember

Re: No vim or pyzo bridges for Leo

2020-04-09 Thread Edward K. Ream
On Thu, Apr 9, 2020 at 5:04 AM gar wrote: > Well, there's a trouble with it. You have 2 separate windows which are in > sync, but you have to remember about it all the time. > And none of your hotkeys work until you press alt-tab. > This is not the route I'd love to use on everyday basis. > No,

I'll be taking a break for "quiet time"

2020-04-09 Thread Edward K. Ream
It's been a long time since I declared a quiet time for myself. It seems like a good thing to do right now. During quiet time I'll defer responses to discussions here. The purpose of quiet time is to rid myself of day-to-day distractions, and instead focus on questions. Text editors like vim

Re: No vim or pyzo bridges for Leo

2020-04-09 Thread gar
Well, there's a trouble with it. You have 2 separate windows which are in sync, but you have to remember about it all the time. And none of your hotkeys work until you press alt-tab. This is not the route I'd love to use on everyday basis. There is another potential way forward. At present, Leo's

Re: A new tree drawing approach

2020-04-09 Thread Edward K. Ream
On Thu, Apr 9, 2020 at 2:21 AM vitalije wrote: Is it that the existing code recreates all the QT items from scratch every > time there is a redraw? And your code can add/remove a much smaller subset > of QT items because of your set operations? > Yes, that's the difference. > I didn't quite

Re: A new tree drawing approach

2020-04-09 Thread Edward K. Ream
On Wednesday, April 8, 2020 at 9:05:25 PM UTC-5, btheado wrote: > > > > This looks interesting. Thanks for sharing. I'm not familiar with how the > existing tree drawing approach works. Could you share (in broad strokes) > what the current drawing does and how it is different from your new

Re: No vim or pyzo bridges for Leo

2020-04-09 Thread Edward K. Ream
On Thu, Apr 9, 2020 at 3:50 AM gar wrote: > First, I apologies for being too emotional. I do really love vim and do > really love leo so the news that they would never be together made me too > upset. > Secondly, after thinking about the bridge more and more I would probably > accept your point

Re: No vim or pyzo bridges for Leo

2020-04-09 Thread gar
First, I apologies for being too emotional. I do really love vim and do really love leo so the news that they would never be together made me too upset. Secondly, after thinking about the bridge more and more I would probably accept your point of view. Making the bridge itself has no practical

Re: A new tree drawing approach

2020-04-09 Thread vitalije
> > Is it that the existing code recreates all the QT items from scratch every > time there is a redraw? And your code can add/remove a much smaller subset > of QT items because of your set operations? > > Yes, that's the difference. > I didn't quite follow your example about expanding a