On Sun, Nov 9, 2014 at 9:49 AM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
I have a command called 'x' that I use for this. It creates, at the
top of workbook.leo or the first outline already open if workbook.leo
is not open, a node named with the current date /
On Sun, Nov 9, 2014 at 11:56 AM, Davy Cottet cottet.d...@gmail.com wrote:
My idea
[is] to turn Leo complexity to the most simple but complete Sphinx editor.
That's a great idea. Leo's rst commands do indeed have way too many hidden
features. Maybe the set of features used by all of Leo's
The cycle-all-focus command is difficult to do properly because it cycles
through a list of widgets that changes as tabs are added to the Log pane.
It has been buggy from day one.
An alternative would be to create a set of commands each of which puts
focus in a particular pane, for example,
I begun with Leo at the same time I begun with Python, and also found Leo a
bit overwhelming to use in the beginning, but Edward and others have done
much to help newbies ever since (Tutorials, easier settings, quick start
guide, etc).
I think its a great idea to use leo for your purpose, and I
Im normally a power user of such commands, but never saw use on this one
specially because of the lack of traceability, IE, you cycle all but dont
know which one is next or which one you are on etc.
Well this is my chatty way to say I totally agree, and I like clearness of
the focus-to-x thing.
On Mon, 10 Nov 2014 08:01:36 -0600
Kent Tenney kten...@gmail.com wrote:
Does Leo currently offer the ability to define a tree
structure template? I seem to recall this.
Such that the great idea above wouldn't require a .leo file
but could live in a @tree node (or some such)
Rings a very
On Mon, 10 Nov 2014 05:15:34 -0800 (PST)
Edward K. Ream edream...@gmail.com wrote:
The cycle-all-focus command is difficult to do properly because it
cycles through a list of widgets that changes as tabs are added to
the Log pane. It has been buggy from day one.
An alternative would be to
On Mon, 10 Nov 2014 06:50:27 -0600
Edward K. Ream edream...@gmail.com wrote:
On Sun, Nov 9, 2014 at 9:49 AM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
I have a command called 'x' that I use for this. It creates, at the
top of workbook.leo or the first
Edward,
((long story short: program description built by setup.py, PKG-INFO,
doesn't match PKG-INFO.TXT))
I'm reverse engineering what I think you do and maybe have reached wrong
conclusion about the workflow, please correct at will. Anyway, here goes:
- At the top level there is are
I dont understand well your concern, so far, the focus-to-body,
focus-to-tree etc commands work perfectly, plus if you want to focus on
the log you can do:
c.frame.log.selectTab('LogTabNameHere'), and you will focus your selected
log pane.
Also, when I was trying to identify where did the user
I'm proposing the 2nd route be the default. Committing an example of
changes in a few minutes.
I created a branch and a pull request,
https://github.com/leo-editor/leo-editor/pull/94, but am not sure I did it
correctly because github is telling me We can’t automatically merge this
pull request..
I have been trying to define tree-structures-templates ever since I got
into Leo. Always trying to create useful-for-more-than-myself templates.
But the problem is what Terry just said, I often found it very difficult to
find the sweet spot, in which they are easy to document and understand,
and
On Mon, Nov 10, 2014 at 12:17 PM, Matt Wilkie map...@gmail.com wrote:
Edward,
((long story short: program description built by setup.py, PKG-INFO,
doesn't match PKG-INFO.TXT))
I see what you've done, but I don't think I like it.
The present make-leo script wants a proper PKG-INFO.TXT
On Mon, Nov 10, 2014 at 12:35 PM, Edward K. Ream edream...@gmail.com
wrote:
I see what you've done, but I don't think I like it.
Let me emphasize that I'm willing to consider removing pkg-info.txt, but
I'd like more warning in future.
Rev 7e0964a contains code that I used to verify that
The present make-leo script wants a proper PKG-INFO.TXT available so that
it can appear in the .zip file and executable installer.
oh, I didn't know it was used in other places!
I don't mind a script ignoring PKG-INFO.TXT and creating a new one, but
deleting the existing file seems
On Mon, Nov 10, 2014 at 10:42 AM, Edward K. Ream edream...@gmail.com
wrote:
Let me emphasize that I'm willing to consider removing pkg-info.txt, but
I'd like more warning in future.
Rev 7e0964a contains code that I used to verify that setup.py now appears
in Leo-5.0-b1.zip. This is all I
On Mon, Nov 10, 2014 at 12:34 PM, Fidel N fidelpe...@gmail.com wrote:
I have been trying to define tree-structures-templates ever since I got
into Leo. Always trying to create useful-for-more-than-myself templates.
But the problem is what Terry just said, I often found it very difficult
to
On Mon, Nov 10, 2014 at 12:56 PM, Edward K. Ream edream...@gmail.com
wrote:
On Mon, Nov 10, 2014 at 12:46 PM, Matt Wilkie map...@gmail.com wrote:
...and I think I may have just stuck my foot in it again a few seconds ago
attempting to sync with your changes. I don't think I'm liking the
On Mon, Nov 10, 2014 at 11:00 AM, Edward K. Ream edream...@gmail.com
wrote:
Matt, do you hang out on #leo on irc? It can sometimes be easier to chat
there...
I'm about to, installing a client now.
--
You received this message because you are subscribed to the Google Groups
leo-editor
I was wondering if there exists a syntax to describe a
tree structure in a node, like:
#headline
@tree myproject
#body
@auto index.html
@path style
@auto main.css
@auto simple.css
@path js
@auto model.js
@auto view.js
@auto controller.js
...
such that an rclick on
I'm afraid I don't know how this is used, if I put the
whole thing in a node and ctl-b it's available, but
it looks like it should be active automatically if in
a @commands tree in myLeoSettings.leo, but I've
not had success.
If that's true, what is the headline, what is the body?
Thanks,
Kent
Leo scripts are attractive because they have such easy access to both
outline data *and* its structure. This suggest driving the script from
the outline data, which is really what the rst3 command does. Perhaps you
can devise a simpler way to drive the script from outline data..
I am
On Mon, 10 Nov 2014 21:34:27 +0100
Fidel N fidelpe...@gmail.com wrote:
Leo scripts are attractive because they have such easy access to
both outline data *and* its structure. This suggest driving the
script from the outline data, which is really what the rst3 command
does. Perhaps you
On Mon, 10 Nov 2014 15:12:15 -0600
'Terry Brown' via leo-editor leo-editor@googlegroups.com wrote:
It's pretty trivial to translate Leo's data structure to these tables,
So just for amusement, here's some code that does that:
import sqlite3
con = sqlite3.connect(:memory:)
cur = con.cursor()
Thank you Terry, those posts go to my To-study list for when I finish the
exam :D
On Mon, Nov 10, 2014 at 10:27 PM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
On Mon, 10 Nov 2014 15:12:15 -0600
'Terry Brown' via leo-editor leo-editor@googlegroups.com wrote:
It's pretty
Cool, working as
@command x
Thanks,
Kent
On Mon, Nov 10, 2014 at 2:46 PM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
On Mon, 10 Nov 2014 13:36:44 -0600
Kent Tenney kten...@gmail.com wrote:
I'm afraid I don't know how this is used, if I put the
whole thing in a node and
On Mon, Nov 10, 2014 at 3:12 PM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
I am currently studying Database and XML standards history among other
things, (which never did before) and I realized that Leo database
structure is not the most modern one.
Now for
On Mon, Nov 10, 2014 at 11:23 AM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
I wonder if there's an easy way to do that by convention of widget
names. This code:
[snip]
reports 207 widget names with their usage count.
Well, I'm just looking for 3-4 more
28 matches
Mail list logo
