Re: Preliminary merge of trunk into at-path

2008-09-18 Thread Edward K. Ream
On Sep 17, 3:39 pm, Edward K. Ream [EMAIL PROTECTED] wrote: Please report any problem [with the trunk] immediately.  I'll soon be merging the leo-30 branch into the trunk. It looks like the at-path stuff broke the goto-global-line command. I'm merging the leo-30 branch into the trunk now.

Re: Preliminary merge of trunk into at-path

2008-09-18 Thread Edward K. Ream
On Thu, Sep 18, 2008 at 8:42 AM, Edward K. Ream [EMAIL PROTECTED] wrote: It looks like the at-path stuff broke the goto-global-line command. I'm merging the leo-30 branch into the trunk now. I will fix the goto problem after the merge. Probably today. Warning: rev 1067 of the trunk

Re: Leo notebook - finally a reality (in literal sense ;-)

2008-09-18 Thread Ville M. Vainio
On Sat, Sep 6, 2008 at 5:29 PM, Edward K. Ream [EMAIL PROTECTED] wrote: Now it's easier than ever to add *quick* notes with leo. ILeo knows of special leo file ~/.ipython/ipython_notebook.leo, which is opened automatically when you...launch leo without specifying a .leo file to open. This

Re: Sqlite, leo's future file format?

2008-09-18 Thread Ville M. Vainio
On Sat, Sep 6, 2008 at 5:03 PM, Edward K. Ream [EMAIL PROTECTED] wrote: Are you aware of Leo's support for zodb data stores? Afaik, nobody has done anything at all with it. Perhaps there is a big untapped potential in this area. Zodb is a big dependency, while sqlite is bundled with python

Re: Preliminary merge of trunk into at-path

2008-09-18 Thread Ville M. Vainio
On Thu, Sep 18, 2008 at 8:51 PM, Edward K. Ream [EMAIL PROTECTED] wrote: P.P.S. The leo-30 branch compiles with both Python 2k and Python 3k. However, if you run the code with Python 3k you will get dropped into the curses gui(!) That's intentional: the regular gui code doesn't Leo has a

Caution: leo-30 branch merged into trunk.

2008-09-18 Thread Edward K. Ream
Rev 1069 of the trunk now contains the leo-30 code. The code should compile with both Python 2.x and Python 3.0. All unit tests pass, and I have reviewed all changed files to make sure the changes are at least reasonable. Please use a bit more caution than typical with this code, and please

Re: Sqlite, leo's future file format?

2008-09-18 Thread Terry Brown
I've just written a through-the-web web authoring system which uses a node hierarchy and stores the nodes as pickled objects in a sqlite3 db. Some nodes have 5 MB .mp3 files as attributes, but this doesn't seem to be a problem. So I'm impressed with the performance of sqlite, but I don't think

Re: Preliminary merge of trunk into at-path

2008-09-18 Thread Edward K. Ream
On Thu, Sep 18, 2008 at 1:21 PM, Ville M. Vainio [EMAIL PROTECTED] wrote: On Thu, Sep 18, 2008 at 8:51 PM, Edward K. Ream [EMAIL PROTECTED] wrote: P.P.S. The leo-30 branch compiles with both Python 2k and Python 3k. However, if you run the code with Python 3k you will get dropped into the

Re: Leo notebook - finally a reality (in literal sense ;-)

2008-09-18 Thread Edward K. Ream
On Thu, Sep 18, 2008 at 1:07 PM, Ville M. Vainio [EMAIL PROTECTED] wrote: Actually, even if I say so myself, opening a default leo file is a very good idea. It's on the list of things to do first. My guess is within a week. Edward --~--~-~--~~~---~--~~ You

Re: Sqlite, leo's future file format?

2008-09-18 Thread Edward K. Ream
On Thu, Sep 18, 2008 at 1:38 PM, Terry Brown [EMAIL PROTECTED] wrote: I've just written a through-the-web web authoring system which uses a node hierarchy and stores the nodes as pickled objects in a sqlite3 db. Some nodes have 5 MB .mp3 files as attributes, but this doesn't seem to be a

Re: Caution: leo-30 branch merged into trunk.

2008-09-18 Thread Edward K. Ream
On Sep 18, 1:23 pm, Edward K. Ream [EMAIL PROTECTED] wrote: Rev 1069 of the trunk now contains the leo-30 code... I'll give top priority to any new bugs while we shake out the rough edges. Python 3K's 'except anException as e' replaces Python 2K's 'except anException, e' syntax. The

Re: Leo now requires Python 2.4 or higher

2008-09-18 Thread Edward K. Ream
On Mon, Aug 25, 2008 at 9:18 AM, Ville M. Vainio [EMAIL PROTECTED] wrote: Python 2.6 will probably be the earliest version that can be made compatible with py3k (that's the explicit design choice of python developers), so2.4as an interim requirement may not be worth it... That may be