On Tue, May 6, 2008 at 5:50 PM, dswheeler <[EMAIL PROTECTED]> wrote:
>
> However I did not change @file to @nosent. I imported the file several
> times and the resulting node was always named "@nosent /
> template.txt". I would then manually change it to "@thin ..." or
> "@file ...". When I woul
"But Dear, your glasses are on top of your head." You are correct. Not
only was there an @ignore in the file but it was the first line. I
figured it was something obvious that I was just overlooking
(repeatedly). Thanks for the prompt reply.
However I did not change @file to @nosent. I imported t
On Tue, May 6, 2008 at 1:54 PM, Kayvan A. Sylvan <[EMAIL PROTECTED]> wrote:
>
> > Has anyone had trouble with unreadable fonts on Linux with the brand
> > new trunk code?
>
> Not I.
Glad to hear it.
>
>
> > When I went to check the trunk on my Ubuntu machine I found that the
> > fonts were unre
On May 6, 12:00 pm, "Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> I shall be attempting to update LeoPy.leo and LeoDocs.leo by
> hand in the near future. This is necessarily a tricky process.
Actually, it went smoothly. I just deleted all clones containing
code. The latest code is now on th
On May 5, 9:52 am, "Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> It will be easier for me if nobody updates any of Leo's core files in
> the trunk until after the sax-graph branch merges with the trunk.
I have just finished the last by-hand merges of Leo's project notes.
It is now fine with me
On Tue, May 06, 2008 at 08:39:50AM -0700, dswheeler wrote:
>
> 2) I'm currently using leo on an existing project and trying to import
> existing files into leo for refactoring. The file in question is named
> template.txt and contains html markup and macro expansion
> placeholders. I used File--
On Tue, May 06, 2008 at 10:30:48AM -0700, Edward K. Ream wrote:
>
> Has anyone had trouble with unreadable fonts on Linux with the brand
> new trunk code?
Not I.
> When I went to check the trunk on my Ubuntu machine I found that the
> fonts were unreadable. However, they are also unreadable on
On Tue, May 06, 2008 at 01:11:46PM -0500, Edward K. Ream wrote:
> On Tue, May 6, 2008 at 12:00 PM, Edward K. Ream <[EMAIL PROTECTED]> wrote:
>
>
> > All unit tests pass on XP. I'll run unit tests on Linux soon.
>
> At present 9 gui-related tests fail on my Ubuntu box. This is likely a
> proble
On Tue, 6 May 2008 13:13:06 -0500
"Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> > I haven't seen any problems with sax-graph branched as of this
> > morning, I'm using 8.04, but Tk 8.5 rather than the default 8.4.
>
> Did you rebuild Python from sources? Just installing Tk 8.5 has no
> effect on
On Tue, May 6, 2008 at 10:39 AM, dswheeler <[EMAIL PROTECTED]> wrote:
I used File-->Import..-->Import to @file which
> generated an "@nosent .../template.txt" node with the file text as the
> body.
I'm surprised that any import command generates @nosent nodes. Presumably
you changed @file to @
On Tue, May 6, 2008 at 12:54 PM, Terry Brown <[EMAIL PROTECTED]>
wrote:
>
> > Has anyone had trouble with unreadable fonts on Linux with the brand
> > new trunk code?
>
> I haven't seen any problems with sax-graph branched as of this morning,
> I'm using 8.04, but Tk 8.5 rather than the default 8.
On Tue, May 6, 2008 at 12:00 PM, Edward K. Ream <[EMAIL PROTECTED]> wrote:
> All unit tests pass on XP. I'll run unit tests on Linux soon.
At present 9 gui-related tests fail on my Ubuntu box. This is likely a
problem with my python/ubuntu install rather than the merged sax-graph
code...
Edw
On Tue, 6 May 2008 10:30:48 -0700 (PDT)
"Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> Has anyone had trouble with unreadable fonts on Linux with the brand
> new trunk code?
I haven't seen any problems with sax-graph branched as of this morning,
I'm using 8.04, but Tk 8.5 rather than the default
Has anyone had trouble with unreadable fonts on Linux with the brand
new trunk code?
When I went to check the trunk on my Ubuntu machine I found that the
fonts were unreadable. However, they are also unreadable on my
(unchanged) sax-graph branch, so it looks like the culprit is a recent
upgrade
On Tue, 6 May 2008 10:08:21 -0700 (PDT)
"Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> 1. Avoid criss-cross merges if at all possible.
Now that it's too late to help, I see this in the bzr docs. (I was
looking up the definition of criss-cross merge :)
4.4.4 Using the remerge command
In some c
The sax-graph branch was unusual in several ways:
- Development on this branch lasted a lot longer than usual.
- The sax-graph branch was a criss-cross merge of the graph-world and
sax branches.
- Because of the extensive changes made in the branch to crucial core
files, it was not feasible to
Revision 391 of the trunk now contains the merged sax-graph code.
Please report any problems immediately. I expect there may be
reversions possible. If you have changed Leo's core recently I urge
you to carefully review the present trunk code to ensure that the
changes haven't been reverted.
Th
1) Thanks for writing Leo. From my limited experience with it, it is
to outliners and mind mappers what lisp is to programming languages.
Kinda awkward at first but once you realize how powerful it's
abstractions are and what you can do with them chills run down your
spine and you get goose bumps.
On Tue, May 6, 2008 at 9:14 AM, Terry Brown <[EMAIL PROTECTED]> wrote:
> /leo/bzr/leo.repo/sax-graph/leo/src/leoTkinterFrame.py",
> line 431, in __repr__ return "" % self.title
> AttributeError: leoTkinterFrame instance has no attribute 'title'
Thanks for this report. I'll fix it soon. Not s
On Tue, May 6, 2008 at 7:56 AM, bobjack <[EMAIL PROTECTED]> wrote:
>
> toolbar and rClick won't work in the sax-graph branch as some of the
> changes to core that are needed to support those versions have not
> been made.
>
> I merged those changes into the branch (local copy) and they worked
> fi
This is part of a config.php file for a web template. All the code is
not present; I removed code and left enough just to make my point.
I will update and test.
Thanks! ;)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Gro
There have been no significant problems with the sax-graph world, so
it is time to do the grand merge of the sax-graph world into the
trunk.
I had planned to work with the sax-graph code for a few more days, but
this plan ran afoul of problems with working with two copies of
leoToDo.txt and leoPr
Just grabbed sax-graph and will try it today for coding. Didn't see
any problems, and it seemed faster to load leoPy.leo.
When I switched back to the launching console the traceback below was
there, didn't see any problem while running though.
Cheers -Terry
Traceback (most recent call last):
toolbar and rClick won't work in the sax-graph branch as some of the
changes to core that are needed to support those versions have not
been made.
I merged those changes into the branch (local copy) and they worked
fine.
I merged sax-graph into my local copy of the trunk and non of the
conflicts
On Tue, May 6, 2008 at 4:37 AM, bobjack <[EMAIL PROTECTED]> wrote:
>
> toolbar.py overrides frame in init, it may be as well to delete this
> file if problems occur (or event if they don't) as it has side effects
> even if it isn't loaded.
>
> Havn't had time to play with sax-graph yet but will so
toolbar.py overrides frame in init, it may be as well to delete this
file if problems occur (or event if they don't) as it has side effects
even if it isn't loaded.
Havn't had time to play with sax-graph yet but will soonest
Bob
--~--~-~--~~~---~--~~
You received
26 matches
Mail list logo
