On Thu, Jun 19, 2008 at 12:27 PM, Kent Tenney [EMAIL PROTECTED] wrote:
It is your expectations, not Leo, that are faulty. Leo can never read
@nosent nodes:
Why not?
Because there are no sentinels in the file! Without sentinels, your options
are:
1. Use @auto to get the file.
2. Use
Because you can never have too many @file flavors ;-) I'll point out
there's a plugin that adds a @text node which maybe does closer to what
Kent was expecting. When you double click on something it reads the
file, writes the file on outline save, I think.
On Fri, 20 Jun 2008 09:03:35 -0700
Turns out @menuat is completely unintrusive, if you don't count the new
@settings node type list entries. Here's the diff... shall I merge w.
trunk?
Cheers -Terry
36c36
'popup', # New in Leo 4.4.8.
---
'menuat', 'popup', # New in Leo 4.4.8.
78c78
---
'menuat':
On Fri, Jun 20, 2008 at 1:07 PM, Terry Brown [EMAIL PROTECTED] wrote:
On Fri, 20 Jun 2008 12:40:42 -0500
Kent Tenney [EMAIL PROTECTED] wrote:
Any ETA on merging the leo-menuat branch with the trunk?
I want both --one-config and menu config cascading.
I'll merge it if Edward says it's ok
On Wed, Jun 18, 2008 at 3:49 PM, Kent Tenney [EMAIL PROTECTED] wrote:
I just created a node
@file-nosent buildout/README.txt
(README.txt is a rst file)
the file buildout/README.txt exists, I expected it to
be loaded into the body of the @file-nosent node,
It is your expectations, not
