It's time to go back and complete the one-node world. This is a
fundamentally important project.
I'll be putting my head down until this is complete. Any help
answering questions will be appreciated. Thanks.
Edward
--~--~-~--~~~---~--~~
You received this
I am running into complications with the one-node world. This is no
great surprise.
For starters, I have added a g.enableDB switch that turns off file
caching. That way I have some hope of debugging read code :-) I plan
to make this a command-line option. There probably should also be a
On Aug 25, 8:40 am, Edward K. Ream edream...@gmail.com wrote:
I am running into complications with the one-node world. This is no
great surprise.
The one-node branch now contains the latest work. Be careful: the
code is actively dangerous when g.unified_nodes is True.
The problem with
Last night I retrieved the code in leoDist.leo that created the NSIS
installer. It was in Leo 4.4; there may be a later version. Imo, Leo
does need this installer, and it would be worth significant work to
make it happen.
I plan to use a script to turn the output of bzr ls into a concise
Hi:
I have a question or maybe a concern with this.
When you say will write @file nodes exactly like @thin nodes does
that mean that the source for the external file will no longer be kept
in the .leo file? If so, I think that will break my current usage /
work-flow.
Right now I keep only the
On Tue, Aug 25, 2009 at 10:42 AM, Edward K. Ream edream...@gmail.comwrote:
I plan to use a script to turn the output of bzr ls into a concise
manifest file that will be the basis of including files in the
executable installer.
The form of the manifest isn't important. Instead the script
I'm having trouble setting up the file association on windows vista so
that when I double click on a file it opens leo with that file. I
didn't have problems setting up windows xp for this.
I'm having trouble with the directions at
On 8/25/09, John Hutchinson jrhutchin...@att.net wrote:
Right now I keep only the foo.leo file under version control, and
delete all the derived files that make up my project periodically. So
a clean instance of my project is just foo.leo, then when I write
the missing @file nodes, I get
On 8/25/09, Edward K. Ream edream...@gmail.com wrote:
Finally, I think pickleshare.py should be moved into Leo's core. It's
used by Leo's core and is an essential part of caching. At present,
it's pretty much hidden in the external directory, and furthermore,
leoExternal.leo should be
On 8/25/09, Edward K. Ream edream...@gmail.com wrote:
The problem with caching is perhaps only a symptom of a deeper
problem, namely, how to synchronize leoProjects.txt. This problem
gets quite severe when working on several branches at once. It's
gotten so bad that I don't want to drag
I'm having trouble with the directions at
http://webpages.charter.net/edreamleo/install.html#installing-leo-on-windows.
For step 5 I'm not sure what it means by setting up a short-cut
“Target = C:Python25pythonw.exe “C:Python25Libsite-
packagesleolaunchLeo.py” Start in = D:code ”. Target
...looks like I erred on the side of brevity when penned those
instructions up, and then line-breaks and backslashes were discarded
when converted to Sphinx docs.
I've posted a pretty print version at
http://www.uttara.ca/blog/install/installing-leo-editor-on-windows
which should make the
On Tue, Aug 25, 2009 at 3:31 PM, Matt Wilkie map...@gmail.com wrote:
...looks like I erred on the side of brevity when penned those
instructions up, and then line-breaks and backslashes were discarded
when converted to Sphinx docs.
I've posted a pretty print version at
On Tue, Aug 25, 2009 at 2:38 PM, Ville M. Vainio vivai...@gmail.com wrote:
On 8/25/09, Edward K. Ream edream...@gmail.com wrote:
Finally, I think pickleshare.py should be moved into Leo's core. It's
used by Leo's core and is an essential part of caching. At present,
it's pretty much
A few weeks ago I wrote that it appeared that a few Tk plug-ins that
worked in earlier versions broke in 4-6-2. Ville said that should
not be too much the case. I took a more careful look today and the
situation is not that bad. Nice job on the new release - it is
faster.
The three problems
Another vista option.
Create a text file and name it leostart.cmd
Put the following commands (or something similar) in the file
set PYTHONHOME=c:\python25
set PYTHONPATH=c:\python25
C:\Python25\python.exe c:\python25\lib\site-packages\leo-4-6-2-final
\launchleo.py %1 --gui=tk
where you
16 matches
Mail list logo
