On Sun, May 18, 2008 at 11:02 PM, Edward K. Ream [EMAIL PROTECTED] wrote:
2. We will change all imports from
import leoX
to
import leo.core.leoX.
Or, perhaps less intrusively (sourcecodewise), from leo.core import
leoX, as you mention later on.
Requirement 2. We have got to be able to
On Sun, May 18, 2008 at 10:29 PM, TL [EMAIL PROTECTED] wrote:
Version 1 of the vi key bindings for editing in the body pane has been
uploaded to this forum's Files section.
Many thanks for this work. You're on the short list for the $100 prize.
The biggest issue is the lack of good
On Sun, May 18, 2008 at 2:19 PM, Kent Tenney [EMAIL PROTECTED] wrote:
I see Leo as a platform, I think the 'Next Big Thing can be that
what is built with Leo...
I picture a Leo file with documentation, a smart node which will open
a set of files on the filesystem, safely, without impinging
On Sun, May 18, 2008 at 5:16 PM, Stephen Farrar [EMAIL PROTECTED]
wrote:
[With text wrapping], up and down arrows take me to the next line in the
file, not the next line on the screen. That means I'm always reaching for
the
mouse.
Is there a way I can change the arrow key behaviour?
Or
On Sun, May 18, 2008 at 10:57 AM, zpcspm [EMAIL PROTECTED] wrote:
Interesting question.
Let us define p.fileLevel() for any position p as follows: p.fileLevel()
is
0 if p is not a descendant of any kind of @file node. Otherwise, suppose
root is the position of the enclosing @file
On Mon, May 19, 2008 at 6:56 AM, Edward K. Ream [EMAIL PROTECTED] wrote:
On Sun, May 18, 2008 at 2:19 PM, Kent Tenney [EMAIL PROTECTED] wrote:
I see Leo as a platform, I think the 'Next Big Thing can be that
what is built with Leo...
I picture a Leo file with documentation, a smart node
On Mon, May 19, 2008 at 7:20 AM, Kent Tenney [EMAIL PROTECTED] wrote:
Might it make sense to add a command line option,
--single-config '/home/ktenney/project/project.leo'
which would fetch configuration only from the specified file?
It seems this would basically produce the behavior I'm
The coming merge of the leo-as-a-package2 branch into the trunk has
the potential to be more complex than normal due to renaming the leo
\src directory to the leo\core directory.
I just did this rename in the leo-as-a-package2 branch, and then did a
trial merge. Apparently nothing happened.
My plan to start the new leo-as-an-editor branch from the latest trunk
turned out to work very well.
The branch now contains a mass update. Here are the push notes:
- Removed top-level references to g in leoGlobals.py.
This is needed because g can not be set until after run() imports
On May 19, 8:24 am, Edward K. Ream [EMAIL PROTECTED] wrote:
The coming merge of the leo-as-a-package2 branch into the trunk has
the potential to be more complex than normal due to renaming the leo
\src directory to the leo\core directory.
Apparently not. A merge of the trunk into the
I'm running the trunk (lp:leo-editor) just updated, getting the following
when starting Leo. This is on Ubuntu 8.04.
Is this a TK version issue? I haven't been following that thread.
Thanks,
Kent
Traceback (most recent call last):
File /home/ktenney/code/bzr/leo-editor/leo/src/leo.py, line
I'll hack together something :-)
Thanks. It will really help.
TL
--~--~-~--~~~---~--~~
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 unsubscribe
12 matches
Mail list logo
