Thanks for the reply, Ville, I'll give that a try.
Could the Leo web page that gives the system requirements be changed
to say python 2.6 should be used? At the moment, this url:
http://webpages.charter.net/edreamleo/install.html
states:
Leo will work on any platform that supports Pyt
Thanks! I've been a way from the internet for a couple days, but I've
now incorporated your suggestions.
On Jul 21, 7:59 pm, tfer wrote:
> Know that I'm on the right revision, here are some proposals:
>
> Creating and destroying nodesNow that I'm looking at the right
> leoDoc.leo:
>
> Chapter 3
--- On Fri, 7/23/10, vitalije wrote:
> I have noticed the same error. I think it happens only if
> you have
> @button or @command nodes somewhere in @settings tree.
Hmm, I have that situation, and still don't see the error.
> I think that you should look at two methods
> createAtButtonHelper
>
> Hmm, I was touching this code recently, adding the Goto Script and button
> submenu stuff.
>
> But it's working for me bzr revno = 3169.
I have noticed the same error. I think it happens only if you have
@button or @command nodes somewhere in @settings tree.
I think that you should look at two
On Jul 23, 3:59 pm, Nick_H wrote:
> I'm working with Leo 4.7.1 final (build 3005, dated 26 Feb 2010) and
> just noticed a bug in propagate_changed_lines within leoShadow.py.
> I haven't worked out the complete fix for this, but thought I'd
> mention it now so that others don't stumble over it unaw
I'm working with Leo 4.7.1 final (build 3005, dated 26 Feb 2010) and
just noticed a bug in propagate_changed_lines within leoShadow.py.
I haven't worked out the complete fix for this, but thought I'd
mention it now so that others don't stumble over it unawares.
It's the handling of the 'replace' ta
