On Thu, May 24, 2012 at 10:23 PM, Terry Brown terry_n_br...@yahoo.com wrote:
On Thu, 24 May 2012 19:23:26 -0700 (PDT)
Edward K. Ream edream...@gmail.com wrote:
As or rev 5348, patterns of the form !command-name! get translated
to the key binding for command-name, or the string Alt-xcommand-
On Thu, May 24, 2012 at 3:17 AM, ne1uno eltro...@gmail.com wrote:
python does obviously have type inference, isn't it good enough?
Python's interpreter knows the type of objects at run time, that is,
just at the time the interpreter is about to execute an opcode.
My goal is to deduce
About a year ago at the Ashland sprint Kent (iirc) made the following
suggestion: solid, simple implementation of one of the standard
template engines providing intuitive template nodes, variable
definitions, and rendering options.
This is moving up the to-do list and yesterday's docstring hack
Take a look at jinjarender for an example how it could behave.
Basically it's @nosent like one directional rendering. Valuespace
plugin is used as input source
Sent from my Windows Phone
From: Edward K. Ream
Sent: 5/25/2012 4:12 PM
To: leo-editor
Subject: Should Leo support a standard template
I've been using jinja2 lately, because it's favored by Salt.
http://saltstack.org
There is so much wisdom behind the Salt team that I look to them
for best practice recommendations.
I've been wanting to slip in a plug for Salt, there you go. Of course there
are many very good template systems
On Fri, 25 May 2012 05:06:51 -0500
Edward K. Ream edream...@gmail.com wrote:
As or rev 5348, patterns of the form !command-name! get translated
to the key binding for command-name, or the string Alt-xcommand-
nameReturn if there is no key binding.
That's neat. You could go with an
On Fri, May 25, 2012 at 10:20 AM, Terry Brown terry_n_br...@yahoo.com wrote:
The advantage I see is what happens when the conversion isn't happening
In that case, the code produces the literal string
Alt-xcommand-nameReturn
where command-name is the (.*) part of the pattern. So the
On Fri, 25 May 2012 11:15:38 -0500
Edward K. Ream edream...@gmail.com wrote:
The advantage I see is what happens when the conversion isn't happening
In that case, the code produces the literal string
Alt-xcommand-nameReturn
No, I mean when no attempt at conversion is being made,
On Fri, May 25, 2012 at 8:12 AM, Edward K. Ream edream...@gmail.com wrote:
About a year ago at the Ashland sprint Kent (iirc) made the following
suggestion: solid, simple implementation of one of the standard
template engines providing intuitive template nodes, variable
definitions, and
On Fri, May 25, 2012 at 1:36 PM, Kent Tenney kten...@gmail.com wrote:
I think I suggested just this ... AWKWARD ...
Don't panic. A templating script (or plugin) can do just about
anything as long as it doesn't monkey-patch leoFileCommands.py or
leoAtFile.py. But that's never going to be
One of the schemes I'm contemplating would involve using non-printing plane
15 and 16 unicode codepoints as embeddable smart tab-stops. Such would
interact with saving and reading, but probably all able to be taken care of
by hooks rather than hacking the read/write code.
Such templates would
On Wed, 21 Mar 2012 12:01:58 -0700
Matt Wilkie map...@gmail.com wrote:
Here is a plugin idea for someone, copy selected outline structure,
or something.
Edward's post on a different topic just pointed out to me -
- you can use copy node in Leo, and paste in your email editor, and it
On Fri, May 25, 2012 at 3:07 PM, Terry Brown terry_n_br...@yahoo.com wrote:
- you can use copy node in Leo, and paste in your email editor, and it
pastes the XML for the Leo node *and subtree* into the email program
- and it works backwards - select / copy the XML from an email, use
On Fri, May 25, 2012 at 11:43 AM, Terry Brown terry_n_br...@yahoo.com wrote:
In that case, the code produces the literal string
Alt-xcommand-nameReturn
No, I mean when no attempt at conversion is being made, because the
docstring is just being looked at directly, or processed by other
On Fri, May 25, 2012 at 2:44 PM, tfer tfethers...@aol.com wrote:
One of the schemes I'm contemplating would involve using non-printing plane
15 and 16 unicode codepoints as embeddable smart tab-stops. Such would
interact with saving and reading, but probably all able to be taken care of
by
Also look at jinja_test.leo in contrib branch; it renders a template
to variable mytest (with @= mytest, and @cl jinja, declared in
prelude node), and assigns the value of variable to node @r mytest.
You can execute the outline by alt-x vs-update.
It probably helps to read the docstring of
Here is what I've got for the abstract of the talk:
Leo is an outliner, each node in a leo outline has two parts, a headline -
a single line topic, and its body text, either of which can be blank.
Headlines are displayed in the outline pane their position and indent
level give a visual
17 matches
Mail list logo
