Re: Node Paste - AttributeError

2008-04-22 Thread TL
Thanks for the reply, I checked into why I wasn't at version 358. It turns out that I did a "branch" instead of a "merge" and a branch operation actually puts the files in a subdirectory named after the branch. As a result I had a \trunk branch containing an old version and a \trunk\trunk branch

Re: bzr repo's leo development workflows

2008-04-22 Thread John Griessen
Terry Brown wrote: > On Tue, 22 Apr 2008 10:08:27 -0500 > John Griessen <[EMAIL PROTECTED]> wrote: > >> 4. Decide to go ahead with a merge at a time agreed by developers. > My understanding is that you don't pull and push on a checkout, Ah, yes. When I change that in the write up it's: =

Re: Sax-Graph branch - Cleo attributes support?

2008-04-22 Thread Terry Brown
On Tue, 22 Apr 2008 14:40:57 -0500 "Edward K. Ream" <[EMAIL PROTECTED]> wrote: > > Given that you can arrive at the same node by different paths, I > > think a fully populated stack gives plugins a valuable tool for > > determining context, so I don't think it's just an internal > > implementatio

Re: bzr repo's leo development workflows

2008-04-22 Thread Edward K. Ream
On Tue, Apr 22, 2008 at 10:22 AM, Terry Brown <[EMAIL PROTECTED]> wrote: > > On Tue, 22 Apr 2008 10:08:27 -0500 > John Griessen <[EMAIL PROTECTED]> wrote: > > > 4. Decide to go ahead with a merge at a time agreed by developers. > > cd trunk > > bzr pull > > bzr merge ../leo-jg >

Re: Sax-Graph branch - Cleo attributes support?

2008-04-22 Thread Edward K. Ream
On Tue, Apr 22, 2008 at 10:26 AM, Terry Brown <[EMAIL PROTECTED]> wrote: > > On Tue, 22 Apr 2008 10:11:30 -0500 > "Edward K. Ream" <[EMAIL PROTECTED]> wrote: > > > Apparently our emails crossed on the net. Your statements are > > exactly as I understand the situation, and exactly as I intend the

Re: Node Paste - AttributeError

2008-04-22 Thread Edward K. Ream
On Tue, Apr 22, 2008 at 10:40 AM, TL <[EMAIL PROTECTED]> wrote: > > The node-paste operation is giving me following error when executed > immediately after a node-copy. This has occurred on a couple of .leo > files using the current trunk (branch 358). Anybody else seeing this? [snip] > > At

Re: "unicode object not callable" message

2008-04-22 Thread Edward K. Ream
On Tue, Apr 22, 2008 at 11:55 AM, derwisch < [EMAIL PROTECTED]> wrote: > > Dear all, > I have the following line in a script: > > outputFile.write(p.v.t.headString()) > > An error is raised when the line is executed: > "Type error: 'unicode' object not callable". Do p.headString() instead of p.v

Re: "unicode object not callable" message

2008-04-22 Thread Terry Brown
On Tue, 22 Apr 2008 09:55:18 -0700 (PDT) derwisch <[EMAIL PROTECTED]> wrote: > > Dear all, > I have the following line in a script: > > outputFile.write(p.v.t.headString()) > > An error is raised when the line is executed: > "Type error: 'unicode' object not callable". > > What can I do to av

"unicode object not callable" message

2008-04-22 Thread derwisch
Dear all, I have the following line in a script: outputFile.write(p.v.t.headString()) An error is raised when the line is executed: "Type error: 'unicode' object not callable". What can I do to avoid this message and just have the head contents written to the file? --~--~-~--~~---

Node Paste - AttributeError

2008-04-22 Thread TL
The node-paste operation is giving me following error when executed immediately after a node-copy. This has occurred on a couple of .leo files using the current trunk (branch 358). Anybody else seeing this? -- TL Traceback (most recent call last): File "C:\leo\src\leoCommands.py", line 286, i

Re: Sax-Graph branch - Cleo attributes support?

2008-04-22 Thread Terry Brown
On Tue, 22 Apr 2008 10:11:30 -0500 "Edward K. Ream" <[EMAIL PROTECTED]> wrote: > Apparently our emails crossed on the net. Your statements are > exactly as I understand the situation, and exactly as I intend the > situation to be. Criss-cross emails, like criss-cross merges, only less troubleso

Re: bzr repo's leo development workflows

2008-04-22 Thread Terry Brown
On Tue, 22 Apr 2008 10:08:27 -0500 John Griessen <[EMAIL PROTECTED]> wrote: > 4. Decide to go ahead with a merge at a time agreed by developers. > cd trunk > bzr pull > bzr merge ../leo-jg > (resolve any conflicts) > bzr commit -m "leo-jg changed install docs" >

Re: Sax-Graph branch - Cleo attributes support?

2008-04-22 Thread Edward K. Ream
On Tue, Apr 22, 2008 at 10:05 AM, Terry Brown <[EMAIL PROTECTED]> wrote: > On Tue, 22 Apr 2008 07:48:15 -0700 (PDT) > TL <[EMAIL PROTECTED]> wrote: > > > The Sax-Graph branch does not automatically fix the problem with Cleo > > attributes associated with sub-nodes of @thin nodes being lost when >

Re: bzr repo's leo development workflows

2008-04-22 Thread John Griessen
Terry Brown wrote: > On Mon, 21 Apr 2008 19:07:56 -0500 > John Griessen <[EMAIL PROTECTED]> wrote: > >> Until newbies know enough about bzr, they need to do >> >> bzr branch URL-of-central-repos local-dir-for-branch > > Bear in mind though that that creates the need to push back to the > launch

Re: Sax-Graph branch - Cleo attributes support?

2008-04-22 Thread Terry Brown
On Tue, 22 Apr 2008 07:48:15 -0700 (PDT) TL <[EMAIL PROTECTED]> wrote: > The Sax-Graph branch does not automatically fix the problem with Cleo > attributes associated with sub-nodes of @thin nodes being lost when > Leo is closed and reopened. Was it supposed to? Cleo currently stores attributes

Re: Sax-Graph branch - Cleo attributes support?

2008-04-22 Thread Edward K. Ream
On Tue, Apr 22, 2008 at 9:48 AM, TL <[EMAIL PROTECTED]> wrote: > > The Sax-Graph branch does not automatically fix the problem with Cleo > attributes associated with sub-nodes of @thin nodes being lost when Leo is > closed and reopened. Will the low-level node changes provide that support? > If

Sax-Graph branch - Cleo attributes support?

2008-04-22 Thread TL
The Sax-Graph branch does not automatically fix the problem with Cleo attributes associated with sub-nodes of @thin nodes being lost when Leo is closed and reopened. Will the low-level node changes provide that support? If so, what needs to be done to Cleo? Regards, TL --~--~-~--~~-

Re: Bicycle Repair Man integration with Leo

2008-04-22 Thread Edward K. Ream
On Apr 21, 7:32 pm, "Kayvan A. Sylvan" <[EMAIL PROTECTED]> wrote: > Great! Maybe this will be my first Leo plugin. I am still very much > loving using Leo as my programming platform. The following is just "thinking out loud". Anyone (including Kayvan) should feel free to ignore it :-) Somehow

Sax-

2008-04-22 Thread TL
> BTW, everything, including outline pastes, now works in the sax-graph branch. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com To u

Re: bzr repo's changes, how to create branches, checkouts, commit?

2008-04-22 Thread Terry Brown
On Mon, 21 Apr 2008 19:07:56 -0500 John Griessen <[EMAIL PROTECTED]> wrote: > Until newbies know enough about bzr, they need to do > > bzr branch URL-of-central-repos local-dir-for-branch Bear in mind though that that creates the need to push back to the launchpad branches. As I demonstrated

Re: Bicycle Repair Man integration with Leo

2008-04-22 Thread Edward K. Ream
On Mon, Apr 21, 2008 at 7:32 PM, Kayvan A. Sylvan <[EMAIL PROTECTED]> wrote: Great! Maybe this will be my first Leo plugin. I am still very much > loving using Leo as my programming platform. It would be a great first project: important, medium sized, limited in scope. I took a look at the brm

Re: installdocs merge directive attached

2008-04-22 Thread Edward K. Ream
On Mon, Apr 21, 2008 at 7:53 PM, John Griessen <[EMAIL PROTECTED]> wrote: So, Edward, would you like me to get a checkout? Iirc, you must first ask to be a member of leo-editor-team. Go to https://launchpad.net/~leo-editor-team and ask to become a member. Edward --~--~-~--~~---