On Sun, Aug 24, 2008 at 6:36 AM, zpcspm [EMAIL PROTECTED] wrote:
Update: I have retyped the whole .py @thin file from scratch and the
problem vanished. Presumably it was something wrong with the @thin
file, not with the at.write() algorithm. It's still interesting,
because I didn't see any
On Sun, Aug 24, 2008 at 5:47 AM, Kent Tenney [EMAIL PROTECTED] wrote:
Alt-g reports
no child index for @shadow image/grab.py
not found: ktenney.20080807085542.1:@shadow image/grab.py
Thanks Kent, for this report. I'm relying on you and others who
actually use @shadow to get all the kinks
On Aug 24, 5:47 am, Kent Tenney [EMAIL PROTECTED] wrote:
Alt-g reports
no child index for @shadow image/grab.py
not found: ktenney.20080807085542.1:@shadow image/grab.py
The fix is on the trunk at rev 893.
Edward
--~--~-~--~~~---~--~~
You received this
On Sat, Aug 23, 2008 at 10:36 AM, billp9619 [EMAIL PROTECTED] wrote:
Likewise, I would like to be able to express user attributes in the
body as directives, so that they are more accessible to non-technical
users and also that they could be exported to the MORE format.
It is possible for a
On Sat, Aug 23, 2008 at 11:25 AM, billp9619 [EMAIL PROTECTED] wrote:
A few weeks ago I came across several new books on DOJO.
Thanks, Bill, for this info.
I believe an adapter could be written to access leo outlines
directly - but the data model of the DOJO control is like the
example JSON
On Thu, Aug 21, 2008 at 5:24 PM, rogererens [EMAIL PROTECTED] wrote:
Thanks for explaining. One more thing: how do you define 'correctly
installed'? Putting the directory into /site-packages?
site-packages is a typical place for extensions, but anywhere else
will do as well. I don't put
I plan to release Leo 4.5 b4 tomorrow (Monday) and Leo 4.5 final on
Friday.
Please test the code on the trunk and report any problems immediately.
There are no known serious bugs that would prevent either version.
Edward
P.S. There are quite a few items on the list for the 4.5.1 cycle. It
On Aug 24, 2:27 pm, Edward K. Ream [EMAIL PROTECTED] wrote:
I plan to release Leo 4.5 b4 tomorrow (Monday) and Leo 4.5 final on
Friday.
Please test the code on the trunk and report any problems immediately.
I have just pushed the trunk to the Leo-4-5-final branch
The trunk has been stable
On Sun, Aug 24, 2008 at 2:38 PM, zpcspm [EMAIL PROTECTED] wrote:
These are not serious
The reason why I'm reporting these tracebacks is because I'm almost
ready to commit into the trunk the feature we've discussed some time
ago here: http://tinyurl.com/5nescw
Hmm. That makes them more
On Sun, Aug 24, 2008 at 1:25 PM, VR [EMAIL PROTECTED] wrote:
However I think it would be an appreciated service to all Leo-Users if
for all scripts plug-ins that are provided, we find a *general* way of
stating the minimum python version needed. - What do you think about this
proposal?
To
On Mon, Aug 25, 2008 at 6:13 AM, zpcspm [EMAIL PROTECTED] wrote:
On Aug 25, 1:28 pm, Edward K. Ream [EMAIL PROTECTED] wrote:
First of all, what platform and version of Python are you using?
Slackware Linux 12.0
Python 2.5.1, Tk 8.4.16, Pmw 1.3
Ok. Please download a clean copy of the trunk
On Mon, Aug 25, 2008 at 7:07 AM, Kent Tenney [EMAIL PROTECTED] wrote:
I recommend @thin for everyone,
I don't think that's a good idea,
I don't think there is real disagreement between us--it's just a
matter of emphasis. To be clear, I think @shadow is sensational
technology. It's the way
On Mon, Aug 25, 2008 at 6:52 AM, hemanth [EMAIL PROTECTED] wrote:
Pardon me if this is discussed else where.
I have recently started using Ubuntu Linux as my sole desktop.
I downloaded Leo-4-5-b3.zip from Sourceforge and unzipped. I ran,
$sudo setup.py install
The 'install' script (not
On Aug 20, 11:05 am, Ville M. Vainio [EMAIL PROTECTED] wrote:
There are currently 2 alternative linux installation routes, both of
which are simpler than what is done in the install script:
1) Install leo as library (currently only used by %lleo in ILeo, but
other uses may surface in the
On Mon, Aug 25, 2008 at 10:04 AM, Ville M. Vainio [EMAIL PROTECTED] wrote:
Please don't remove setup.py. My recent change should prevent the confusion.
Ok. I'll put it back in and redo the distribution.
Edward
--~--~-~--~~~---~--~~
You received this message
On Mon, Aug 25, 2008 at 10:14 AM, zpcspm [EMAIL PROTECTED] wrote:
I've just pushed the feature into the trunk. Please tell me if I did
something wrong (like overwriting something for example). I had to do
two merges because the trunk was modified right before I was going to
commit into it.
On Mon, Aug 25, 2008 at 9:18 AM, Ville M. Vainio [EMAIL PROTECTED] wrote:
On Mon, Aug 25, 2008 at 3:08 AM, Edward K. Ream [EMAIL PROTECTED] wrote:
for very much longer. Python 2.4 is probably the earliest version
that can be make compatible with Python 3k, so pretty soon Python 2.4
On Mon, Aug 25, 2008 at 10:31 AM, TL [EMAIL PROTECTED] wrote:
Just installed the latest version and found the following issues with
the new .leo directory:
Thanks for this report. I'll fix these before releasing b4.
1. The File Explorer application in Windows XP does not allow users to
On Mon, Aug 25, 2008 at 10:52 AM, Edward K. Ream [EMAIL PROTECTED] wrote:
On Mon, Aug 25, 2008 at 10:31 AM, TL [EMAIL PROTECTED] wrote:
Just installed the latest version and found the following issues with
the new .leo directory:
Thanks for this report. I'll fix these before releasing b4
Leo 4.5 beta 4 is now available at:
http://sourceforge.net/project/showfiles.php?group_id=3458package_id=29106
This beta 4 release will likely be the last release before Leo 4.5
final. It fixes several bugs reported since the b3 release.
Please report any problems immediately.
Edward
On Mon, Aug 25, 2008 at 11:42 AM, zpcspm [EMAIL PROTECTED] wrote:
I have added the line
otl : vimoutline, #zpcspm 8/25/08 Vim's outline plugin
to
self.extra_extension_dict
in
Code--
Core classes--
@thin leoApp.py--
app.__init__--
define global data structures app
This didn't
On Mon, Aug 25, 2008 at 11:46 AM, Ville M. Vainio [EMAIL PROTECTED] wrote:
Make sure to add the version in trunk - it has my warning fix.
Oops. The updated setup.py didn't make it into the b4 distribution.
I've updated the leo-4-5-final branch, so it will appear in all
further releases.
On Mon, Aug 25, 2008 at 8:59 AM, Terry Brown [EMAIL PROTECTED] wrote:
Just in case people are out there looking for javascript frameworks, I
should point out jQuery (www.jquery.com) which has been working well
for me.
Thanks, Terry, for this link. Eight years ago, when I rewrote Leo in
On Mon, Aug 25, 2008 at 9:02 AM, Terry Brown [EMAIL PROTECTED] wrote:
I'll probably do that - knowing about c.importCommands.scanPythonText
was the pointer I needed, thanks.
I just did a minimal prototype because I wasn't sure what you might
want. However, there is one change I'd be happy to
On Mon, Aug 25, 2008 at 10:35 AM, Ville M. Vainio [EMAIL PROTECTED] wrote:
With ipython, we use _ipython instead of .ipython as the rc directory
on windows, for this and other reasons (some win32 programs don't
really like files/dirs starting with .).
Wow. Configuration issues never stop
to be).
I agree. I'll modify the make script in leoDist.leo so it copies the
readme.txt file from the leo\doc folder to the top-level folder.
Edward
Edward K. Ream email: [EMAIL PROTECTED]
Leo: http://webpages.charter.net
On Mon, Aug 25, 2008 at 2:58 PM, Terry Brown [EMAIL PROTECTED] wrote:
I guess I'd always assumed that the .leo was for unix only. For
windows, what's the advantage of _leo over leo?
There is already a leo directory, so perhaps _leo is less ambiguous.
Edward
Edward K. Ream email: [EMAIL PROTECTED]
Leo: http://webpages.charter.net/edreamleo/front.html
--~--~-~--~~~---~--~~
You received
On Tue, Aug 26, 2008 at 1:58 AM, zpcspm [EMAIL PROTECTED] wrote:
I have modified @test batch mode to make it pass.
leo is now started via launchLeo.py instead of leo/core/runLeo.py
The change is on the trunk (r907).
Thanks!
Edward
--~--~-~--~~~---~--~~
You
On Aug 25, 11:42 am, zpcspm [EMAIL PROTECTED] wrote:
I have added the line
otl : vimoutline, #zpcspm 8/25/08 Vim's outline plugin
to
self.extra_extension_dict
in
Code--
Core classes--
@thin leoApp.py--
app.__init__--
define global data structures app
This didn't fix the
Previous versions of Leo had an .exe installer that created registry
entries for Leo icons and file types. The problem with this approach
is that it requires a manifest of all files to be included. This is
increasingly infeasible now that so many people are modifying Leo's
sources.
The most
On Tue, Aug 26, 2008 at 12:25 PM, zpcspm [EMAIL PROTECTED] wrote:
Why don't get rid of remaining calls to leo/core/runLeo.py and replace
them with calls to launchLeo.py
I just did a search for runLeo.py in leoPy.leo and unitTest.leo.
Besides proper imports, there are no such calls in the
Several recent changes affect how Leo gets distributed, so it is
appropriate to have at least one release candidate before 4.5 final.
I expect this to happen Thursday or Friday. Please report any
problems immediately.
Edward
--~--~-~--~~~---~--~~
You received
On Tue, Aug 26, 2008 at 11:04 AM, zpcspm [EMAIL PROTECTED] wrote:
However, this thread got a bit messed. Let's go back to the original
topic. Please update the site docs. You shall see a new screenshot
after that (which shows 3 numbers in the status area) and a new FAQ
entry (I've considered
On Tue, Aug 26, 2008 at 3:54 PM, Terry Brown [EMAIL PROTECTED] wrote:
The discussion seemed to be pointing towards this
becoming /some/arbitrary/path/.leo/myLeoSettings.leo.
That was not my intention, and I don't want to spread .leo directories
around. One is enough.
Edward
On Aug 26, 6:29 pm, Edward K. Ream [EMAIL PROTECTED] wrote:
I'm not that great at the registry, but I'm not scared of it either.
Attached is a commented python script to generate the needed keys.
Many thanks for this. I'll add this as a post-install script to the
.exe installer. We can
On Aug 27, 9:28 am, Edward K. Ream [EMAIL PROTECTED] wrote:
Here is my latest draft of this script.
Oops. The long lines are problem. Rev 921 now contains leo\dist\post-
install-script.py, owned by leoDist.leo.
Please note: I've only tested this script using Leo's execute-script
command
On Aug 27, 11:05 am, Edward K. Ream [EMAIL PROTECTED] wrote:
Hmm. I have an idea. Maybe sys.executable will indicate the folder,
and the pre-install script can write the post-install script.
Drat. sys.executable is the .exe file for the installer: C:\leo.repo
\trunk\Leo-4-5-rc1.exe
On Aug 27, 11:19 am, Edward K. Ream [EMAIL PROTECTED] wrote:
We are getting close [to running install scripts from the .exe installer.]
The present @button make script in leoDist.leo embeds a pre-install
script to the .exe installer. This script makes the file
associations.
Using a post
A few days ago I saw how to refactor atFile.scanAllDirectives,
g.scanDirectives and related methods so they can all use common code.
The Aha is that we must completely separate parsing of directives from
the rest of the logic. The way to do that is to create a helper
method, say
On Aug 27, 7:31 pm, Edward K. Ream [EMAIL PROTECTED] wrote:
This code is on the trunk at rev 938, but *only* in leoProjects.txt.
The existing 'real' code absolutely must not change until after Leo
4.5 final.
I've just created an at-path branch for this work.
Edward
On Fri, Aug 29, 2008 at 5:06 AM, gegard [EMAIL PROTECTED] wrote:
How do I write out derived files otherwise? I thought that I could
just replace @shadow with @nosent, but then nothing gets written out
As you say, a script will work, but changing @shadow to @nosent should
also work: it will
On Fri, Aug 29, 2008 at 1:02 AM, zpcspm [EMAIL PROTECTED] wrote:
I've been thinking about something and I fail to see an answer.
Consider the following code:
--- cut here ---
class Example:
def __init__(self):
self.s = '''
foo
bar'''
You probably want to do:
self.s =
On Thu, Aug 28, 2008 at 1:59 PM, Kent Tenney [EMAIL PROTECTED] wrote:
After the problem description below, I corrected a Python error
in grab.py, and the error went away.
I put the Python error back in grab.py, Leo then imported
the file correctly.
Go figure.
The import code must be
On Thu, Aug 28, 2008 at 10:02 AM, Ed Blake [EMAIL PROTECTED] wrote:
An xml template seems like overkill
I like Terry's and your idea: put the info in a .leo file. All we
need is some designated node, say @registered-plugins, and then, say,
one child node per plugin, say @plugin, with the
On Fri, Aug 29, 2008 at 8:09 AM, zpcspm [EMAIL PROTECTED] wrote:
You probably want to do:
self.s = g.adjustTripleString(self.s)
I'm not sure I understand. I can see how this is used in leo itself.
But I don't get how it can be applied to derived files.
Correct. You will have to create
On Fri, Aug 29, 2008 at 9:00 AM, Terry Brown [EMAIL PROTECTED] wrote:
Didn't this come up before - you have to dirty the nosent nodes to
get the actually written, i.e. add a line and delete it again or
something.
Changing @shadow to @nosent should dirty the node.
Edward
On Fri, Aug 29, 2008 at 8:15 AM, zpcspm [EMAIL PROTECTED] wrote:
What about headlines like @thin myfile @newlines=unix?
There is a need for something like this. Global options aren't
fine-grained enough, and inheriting an @newlines option in child nodes
isn't safe enough.
I don't much the
On Fri, Aug 29, 2008 at 8:21 AM, zpcspm [EMAIL PROTECTED] wrote:
I was importing (manually) a small flat python script into a leo @thin
node and I've noticed that the output of the script changed after that
(due to the indentation change of the multiline strings). I guess this
is a drawback
On Thu, Aug 28, 2008 at 11:57 AM, Ed Blake [EMAIL PROTECTED] wrote:
Umm, I didn't get a .leo directory?
WinXP 'Pro', Python 2.5
os.path.expanduser('~') works correctly here, what are you using to get the
user data directory?
Using os.path.expanduser gives, for me, exactly the same answer
On Fri, Aug 29, 2008 at 9:25 AM, gegard [EMAIL PROTECTED] wrote:
Yes, thank you, this, too! Changing the node text isn't enough, you
have to do the body itself.
Huh?? Changing headline text does indeed mark the node dirty.
Did you change headline text in a script? If so, you might have to
On Fri, Aug 29, 2008 at 9:34 AM, zpcspm [EMAIL PROTECTED] wrote:
I don't see a way to specify a negative indentation
of a multiline string in a node body.
There isn't a way, and there can't be a way: I'm not going to change
Leo's rock-solid read code to handle weird cases like this.
Of
On Fri, Aug 29, 2008 at 10:03 AM, gegard [EMAIL PROTECTED] wrote:
However it is still only written out if the body is changed (if body
text is unchanged it reports unchanged: filename).
Yes. That makes sense. Does this cause a problem for you?
Edward
On Aug 29, 9:20 am, Edward K. Ream [EMAIL PROTECTED] wrote:
On Fri, Aug 29, 2008 at 8:15 AM, zpcspm [EMAIL PROTECTED] wrote:
What about headlines like @thin myfile @newlines=unix?
There is a need for something like this. Global options aren't
fine-grained enough, and inheriting
On Aug 29, 9:33 am, Edward K. Ream [EMAIL PROTECTED] wrote:
Using os.path.expanduser gives, for me, exactly the same answer as Leo
computes. See computeHomeDirectory in runLeo.py.
But perhaps not if there is no HOME variable defined. Still, I would
prefer to leave the present code alone
On Sun, Aug 31, 2008 at 10:08 AM, Kent Tenney [EMAIL PROTECTED] wrote:
I keep having to do this, when will the need to delete the shadow
files go away?
Something strange is happening. The syntax (of the public file)
should matter only when first importing the file. Thereafter, Leo
doesn't
On Sep 1, 6:49 am, Edward K. Ream [EMAIL PROTECTED] wrote:
Could you send me the file you are having trouble with?
Kent sent me the file in private. Here is my reply to him:
QQQ
It looks like there is a scanning/parser error in Leo's
import code. Specifically at the line:
logging.error
On Sep 1, 8:32 am, Edward K. Ream [EMAIL PROTECTED] wrote:
There is syntax error in grab.py:
logging.error(failure in Grabber._get_config_file, no GRABROOT in
environment.
try adding GRABROOT to /etc/environment
There is no closing paren in the call to logging.error.
When I add
On Mon, Sep 1, 2008 at 9:01 AM, Kent Tenney [EMAIL PROTECTED] wrote:
(@slurp = dumb import, entire file into top level node)
I would like it if Leo could fall back to a @slurp if the file is odd, and
as a side benefit, offer configuration to choose between @auto and @slurp
import, even a
On Mon, Sep 1, 2008 at 9:57 AM, Terry Brown [EMAIL PROTECTED] wrote:
Had a quick look, looks interesting, I'm guessing much easier to
integrate than Komodo, although I don't know how it compares to
Komodo. API docs. seem to be lacking (just the way Edward likes it :-)
Heh.
I was thinking
On Mon, Sep 1, 2008 at 9:41 AM, Ville M. Vainio [EMAIL PROTECTED] wrote:
It was fixed by adding the following to the end of my xmodmap file:
add Mod1 = Alt_L
add Mod2 = Mode_switch
Thanks for this. The Alt-key mess is a major irritation.
Edward
Leo 4.5 final is now available at:
http://sourceforge.net/project/showfiles.php?group_id=3458package_id=29106
Many thanks to all who have contributed so much to this release.
The highlights of Leo 4.5:
--
- Full support for @shadow files in Leo's core.
- Major
The trunk is now available for development work. Feel free to commit
to it, but as always, please make sure that all unit tests pass before
doing so.
The focus for Leo 4.5.1 will be relatively small items that have been
on the to-do list for far too long. As always, the to-do list is in
On Tue, Sep 2, 2008 at 9:30 AM, Kent Tenney [EMAIL PROTECTED] wrote:
Thoughts on making the first line of the node a
valid location for @path and @file directives?
I think the new code supports this for free. That is, @path is
valid either in headlines or body text. I could be wrong
On Mon, Sep 1, 2008 at 2:05 PM, Terry Brown [EMAIL PROTECTED] wrote:
On Mon, 1 Sep 2008 20:10:04 +0300
Ville M. Vainio [EMAIL PROTECTED] wrote:
pysmell seems to operate in tags like manner, and that should be
good enough for most purposes. I.e. generate the completion database
every now
On Tue, Sep 2, 2008 at 10:45 AM, Ville M. Vainio [EMAIL PROTECTED] wrote:
ModuleName.ClassName. [file in the method names] is easyish, but
x = Foo()
a = x. [now what are my choices] is trickier.
This article explains it pretty well:
On Tue, Sep 2, 2008 at 5:52 PM, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Hello all,
first of all: Edward thank you for such a great product. It helps me
daily to get the control of my source.
My tests with @shadow notes showed me that when I read a @shadow tree
with File/read @shadow
The two recently-reported bugs are severe enough to merit a quick
4.5.1 release--I don't like to have 'final' releases with such bugs.
So please do not push speculative code to the trunk for now.
Edward
--~--~-~--~~~---~--~~
You received this message because you
On Tue, Sep 2, 2008 at 12:38 PM, Terry Brown [EMAIL PROTECTED] wrote:
goto-global-line: 3
can not open .../trunk/.leo/shadow/xtest.py
The fix is on the trunk: the error message was supposed to be part of
exception handling.
Edward
--~--~-~--~~~---~--~~
You
On Tue, Sep 2, 2008 at 12:11 PM, Kent Tenney [EMAIL PROTECTED] wrote:
https://wiki.ubuntu.com/UbuntuDeveloperWeek
Thanks for this heads up.
Edward
webpages.charter.net/edreamleo/front.html
On Wed, Sep 3, 2008 at 7:50 PM, Terry Brown [EMAIL PROTECTED] wrote:
But it seems too bad to have nowhere for the bleeding edge to be while
releases are coming up.
They can be in any other branch.
So what if, when releases are getting close, the trunk is used as a
'release' branch, with
On Thu, Sep 4, 2008 at 3:06 AM, zpcspm [EMAIL PROTECTED] wrote:
I find it a bit hard to select something from Recent Files. I think
this is because the menu looks bloated due to dirnames. Is it possible
to emphasize the second item (just the file name of the outline) by
displaying it in bold
On Wed, Sep 3, 2008 at 9:27 AM, Terry Brown [EMAIL PROTECTED] wrote:
Still not working for me with auto, I either get
I'll fix this asap.
Edward
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
On Thu, Sep 4, 2008 at 9:46 AM, Terry Brown [EMAIL PROTECTED] wrote:
Ok, I've created a pre-release branch, belonging to the
leo-editor-team, and I've pushed the current trunk to it.
Thanks.
It's described like this:
New development goes here during releases
When the trunk is only
The line number code was a perfect illustration of why literate-
programming sections are, in general (with a few exceptions), a truly
bad idea.
I've just spent several hours refactoring the code to use 9 (!!) new
helper functions. The new code is on the trunk, and all (previous)
unit tests
On Thu, Sep 4, 2008 at 2:53 PM, Terry Brown [EMAIL PROTECTED] wrote:
For @auto it seems to be only working for me if the @auto node itself
is selected. If a descendant of the @auto node is selected I get a
traceback.
Thanks. I'll fix this today.
Edward
I would like to eliminate the ancient goto-line-number command. This
puts up a dialog to get the line number. This is way obsolete.
Would anyone object if I removed this command?
Edward
--~--~-~--~~~---~--~~
You received this message because you are subscribed
On Fri, Sep 5, 2008 at 2:28 PM, Ville M. Vainio [EMAIL PROTECTED] wrote:
http://leo.zwiki.org/CreateShadows
I don't recall whether I remember this script :-) Anyway, it seems
like an excellent idea.
I have added this feature as %lshadow magic command to ileo :-)
Cool. I'll check it out
On Sat, Sep 6, 2008 at 5:28 AM, Ville M. Vainio [EMAIL PROTECTED] wrote:
Sqlite databases are self-contained in one file, and it seems also the
author suggests sqlite as a possible application file format.
Are you aware of Leo's support for zodb data stores? Afaik, nobody
has done anything
On Sep 5, 3:08 pm, Ville M. Vainio [EMAIL PROTECTED] wrote:
BTW, I think we should prevent shadow files from accidentally
overwriting valuable stuff:
I suppose similar remarks apply to @auto nodes as well...
Edward
--~--~-~--~~~---~--~~
You received this
On Fri, Sep 5, 2008 at 4:58 PM, Ville M. Vainio [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
On Fri, Sep 5, 2008 at 2:38 PM, Ville M. Vainio [EMAIL PROTECTED] wrote:
Currently, there are many commands to read in current node:
read-at-auto-nodes
read-at-file-nodes
read-at-shadow-nodes
Why not have one command to combine all of these, which would select
the right command based on
On Fri, Sep 5, 2008 at 3:55 PM, Terry Brown [EMAIL PROTECTED] wrote:
But it's waiting on nested @path working... where's that at Edward?
It appears to work on the at-path branch.
Edward
--~--~-~--~~~---~--~~
You received this message because you are subscribed
The recent suggestions for improvements have been great. Keep them
coming.
However, it may be awhile before I respond to them all. It's
important that I fix the bugs that necessitate Leo 4.5.1 immediately.
Edward
--~--~-~--~~~---~--~~
You received this message
On Sun, Sep 7, 2008 at 9:58 AM, Theo Ruys [EMAIL PROTECTED] wrote:
I come from a 'pure' literate programming world (i.e. noweb), and I
would like to do similar things with the rst3 plugin. That is, have a
single leo source file and let leo generate three different files from
it:
- a source
On Sep 2, 5:52 pm, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
My tests with @shadow notes showed me that when I read a @shadow tree
with File/read @shadow Nodes is perfect. And the private file has the
sentinels.
But when I reopen that leo file the whole content of the public file
is
On Sun, Sep 7, 2008 at 1:00 PM, Edward K. Ream [EMAIL PROTECTED] wrote:
However, you should be able to use @shadow without trouble using a
workaround: just don't use the read-at-shadow-nodes or write-at-shadow-
nodes commands :-) Indeed, these commands should only very rarely be
needed
On Sat, Sep 6, 2008 at 12:27 PM, TL [EMAIL PROTECTED] wrote:
A previous post suggested that Leo supports or would soon support the
ability to configure within a Leo file that the Leo panes have
vertical orientation with a specific split width between the outline
and the body panes. Is this
On Sun, Sep 7, 2008 at 1:57 PM, Theo Ruys [EMAIL PROTECTED] wrote:
Hmm, that is not exactly what I want.
I want to write the documentation for the source program in a @rst3
subtree.
In this @rst3 subtree I want to refer to fragments of the program,
like:
In the following code fragment::
On Sat, Sep 6, 2008 at 10:33 AM, Lew Maestas [EMAIL PROTECTED] wrote:
Perhaps a Finite State Machine (FSM) is the item you need here.
I doubt it :-) There are implementation issues, but the main problems
are understand what should, in fact happen.
Edward
On Sat, Sep 6, 2008 at 12:21 PM, TL [EMAIL PROTECTED] wrote:
These type of changes can be made using by coding the desired behavior
within mode nodes and binding them to keys. Many, if not all, of
the changes discussed in this thread have been solved within the Vim
emulation using this
On Thu, Sep 4, 2008 at 3:42 PM, Terry Brown [EMAIL PROTECTED] wrote:
Code--Core classes--@thin runLeo.py --utils--createFrame (leo.py)
c.updateRecentFiles(relativeFileName or fileName)
I don't think relative filenames should be passed to
c.updateRecentFiles()? They get stuff in
On Thu, Sep 4, 2008 at 10:16 AM, Terry Brown [EMAIL PROTECTED] wrote:
Recall the discussion about not showing the @shadow text in the
headline of all the @shadow nodes (ditto for @file, @url, @auto,
etc.). I would certainly prefer not to see it, and it seemed that the
approach of having
On Sep 6, 6:50 am, Ville M. Vainio [EMAIL PROTECTED] wrote:
Here's an example ileo snippet to get your gmail threads with todo
label into leo outline (under heading MyTodo):
Thanks for this. I've put it on the list of things to document.
Edward
On Sep 7, 12:52 pm, Edward K. Ream [EMAIL PROTECTED] wrote:
P.S. There is a long-standing problem with line numbers in @nosent
files. A proper fix would be to create faux (temporary) sentinels,
and then use them to make sense of descendant nodes.
This appears to work well. The new code
On Mon, Sep 8, 2008 at 4:16 AM, Theo Ruys [EMAIL PROTECTED] wrote:
At a certain point I want to describe (parts) of this program
in a @rst tree. This means that I want to (re)use certain
named sections (i.e. clones) of the original program
in this @rst tree. For example,
- example of
On Sep 2, 5:52 pm, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
My tests with @shadow notes showed me that when I read a @shadow tree
with File/read @shadow Nodes is perfect. And the private file has the
sentinels.
But when I reopen that leo file the whole content of the public file
is
On Mon, Sep 8, 2008 at 10:28 AM, Terry Brown [EMAIL PROTECTED] wrote:
On Sun, 7 Sep 2008 16:16:14 -0500
Edward K. Ream [EMAIL PROTECTED] wrote:
What is 'w'? Are you sure that it is the same as c.frame.bodyCtrl?
I don't think so, it's one of the headline widgets in the tree panel
On Mon, Sep 8, 2008 at 2:01 PM, Edward K. Ream [EMAIL PROTECTED] wrote:
On Mon, Sep 8, 2008 at 10:28 AM, Terry Brown [EMAIL PROTECTED] wrote:
On Sun, 7 Sep 2008 16:16:14 -0500
Edward K. Ream [EMAIL PROTECTED] wrote:
What is 'w'? Are you sure that it is the same as c.frame.bodyCtrl?
I
On Tue, Sep 9, 2008 at 1:10 AM, Sze Tan [EMAIL PROTECTED] wrote:
Hi Edward,
About the simplest example I can construct that causes the problem is:
[snip]
I hope this helps to track down the issue,
Thanks. I see the behavior you describe. I should be able to fix this today.
Edward
501 - 600 of 19891 matches
Mail list logo
