On Sun, 4 Dec 2011 14:58:10 -0800 (PST)
Largo84 <[email protected]> wrote:

> I also had difficulty getting bzr to work on Windows due to out of
> memory errors (I finally gave up). I actually uninstalled it and just
> download nightly snapshots occasionally. I suppose it would be better
> to get bzr to work,

Despite what Edward just said in another email, I'm not convinced
there's any reason to use bzr unless you want to modify Leo itself.
http://www.greygreen.org/leo/leo-editor-latest.zip can just be
downloaded an unzipped in the same place to stay up to date.  I'd like
it to change to http://www.leo-editor.org/nightly/leo-editor-latest.zip
just for future proofing, but it seems easier than bzr to me.  Well,
easier unless you use bzr a lot, in which case it's probably a tie.

> but I'm not exactly sure what the following
> suggestion means.

In a normal directory (i.e. not one you were already using for Leo
branches) you'd do

`bzr branch lp:~terry-n-brown/+junk/leo_test`

and it would create a branch of Leo in a directory called 'leo_test'.
If it's fixed, as I suspect, it should do that ok even on a memory
limited windows machine, but it would be good to verify that before
taking the next step, deleting the main launchpad copy and replacing it
with this one.

Cheers -Terry

> On Dec 4, 4:26 pm, Terry Brown <[email protected]> wrote:
> > Brian - if I'm right that you're the one who was having trouble getting
> > bzr to branch because of memory issues, can you try branching
> >
> > lp:~terry-n-brown/+junk/leo_test
> >
> > without using an existing shared repository on your local machine,
> > using the lower spec'ed configuration you think should work (i.e. 1GB
> > Windows XP maybe?).
> >
> > Thanks, Terry
> 

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en.

Reply via email to