Yesterday I have played around with different cleo setting of my
outline tree
which led to the observation mentioned im my first posting!
I have now reorganized my outline tree and still have a similar
problem.
My outline tree has now the following structure:
@chapters
@chapter AAA
If you do the following sequence of commands
add-editor
add-editor
delete-editor
delete-editor
add-editor
You get an error message. If you continue to use leo the title bar at
the top of the editor
comes on permanantly even if there is only one editor, so this could
be a crash rather
than a
On Thu, 3 Apr 2008 02:01:29 -0700 (PDT)
bobjack [EMAIL PROTECTED] wrote:
When right clicking on the icon box the headline is not selected if
cleo is in use.
I'll change that so that it does, seeing I always use cleo I didn't
know the behavior was different without it :)
if you right click
On Thu, Apr 3, 2008 at 3:57 AM, bobjack [EMAIL PROTECTED] wrote:
If you do the following sequence of commands
add-editor
add-editor
delete-editor
delete-editor
add-editor
You get an error message.
The fix is on the trunk. All unit tests pass.
The bug was caused by an erroneous
On Thu, Apr 3, 2008 at 7:23 AM, Terry Brown [EMAIL PROTECTED] wrote:
On Thu, 3 Apr 2008 03:05:27 -0700 (PDT)
Nik [EMAIL PROTECTED] wrote:
I have only organizing and thin nodes in my outline tree.
Only the children of thin nodes suffer from cleo amnesia!
It seems that the problem is
I'd like to clean up Leo's top-level folder. At present, the bzr
trunk contains leo_to_html.xsl. It looks like this is used somehow by
the leo_to_html plugin. Can this file be moved to the plugins folder?
I'll leave this file alone for the rc1 release...
Edward
I apologize for my first misleading posting regarding
possible problems with tree depth. It was an unfortunate
coincidence that all thin nodes in my outline tree were
located at depth 7! After some simple experiements with
my outline tree I found that cleo 'problem' is related to
thin nodes. I
On Apr 3, 7:54 am, Edward K. Ream [EMAIL PROTECTED] wrote:
But whatever you do, please wait until after 4.4.8 final to do it :-)
Actually, it would be fine to experiment with solutions in a separate
branch. I should have said,
whatever you do, please wait until after 4.4.8 final to commit it
On Apr 3, 8:40 am, Nik [EMAIL PROTECTED] wrote:
I apologize for my first misleading posting regarding
possible problems with tree depth.
No apology needed. Bug reports are always helpful. You are not
expected to understand the bug in detail :-)
Edward
On Thu, Apr 3, 2008 at 7:37 AM, Ville M. Vainio [EMAIL PROTECTED] wrote:
On Wed, Apr 2, 2008 at 4:47 PM, Edward K. Ream [EMAIL PROTECTED]
wrote:
%run leo.py (in leo/leo/src)
When leo is installable as a package, this will be much simpler
(because we don't need to know where
Leo 4.4.8 rc1 is now available at:
http://sourceforge.net/project/showfiles.php?group_id=3458package_id=29106
This release tests some recent changes in how Leo is distributed. In
particular, the old manifest files are gone: the leo-x.zip file is
created with bzr export.
This is a happy
On Apr 2, 1:04 am, Ville M. Vainio [EMAIL PROTECTED] wrote:
On Wed, Apr 2, 2008 at 2:38 AM, Edward K. Ream [EMAIL PROTECTED] wrote:
I'm not sure what the solution is. Possibly all Leo imports will have
to be changed from:
import leoX
to
import leo.core.x.
Yes. Fully
On Mar 31, 3:52 pm, Edward K. Ream [EMAIL PROTECTED] wrote:
In short, the twin guidelines (no code changes, focus on non-gui code)
have turned what might be a big, dangerous task into a fun romp.
I got very close to getting the Komodo autocompleter to work a few
days ago. For the latest
On Thu, 3 Apr 2008 08:47:17 -0700 (PDT)
Edward K. Ream [EMAIL PROTECTED] wrote:
Actually, I should create an official branch. I just realized that
what I have done (create a local branch of the trunk) is dangerous: if
I forget and push that branch we will not be happy.
Not sure if you've
On Thu, Apr 3, 2008 at 5:40 PM, Terry Brown [EMAIL PROTECTED] wrote:
On Thu, 3 Apr 2008 15:31:17 -0700 (PDT)
thyrsus [EMAIL PROTECTED] wrote:
The only trouble I've had is in the LeoPyRef.leo file.
I use a local non-vcs copy of LeoPyRef.leo and LeoPluginsRef.leo, just
using them as a way
15 matches
Mail list logo
