Hi,
I've started using Leo about 2 months ago. I intended to use it as a
single point of entry for a Python toolkit I am writing from scratch,
where the code is closely coupled with documentation and tests.
My biggest stumbling block is that I find it hard to break out of a
file-based way of
Here's a stopgap measure to survive 2 people editing the same .leo
file, with very little coding
- Suppose 2 people (A and B) have foo.leo open
- A edits node with gnx 1 and saves the document. A also adds a new
node with gnx 3.
- B edits node with gnx 2, but is alarmed that document has been
Any tips for a Leo newbie on how to start a project from scratch?
Here's a quote from the docs: @thin - Use this unless you have a good
reason not to. It is the 'state-of-the-art' in derived files.
I had a bad experience when trying to import derived files into leo as
@file. After a couple of
Hi,
Yes, I remember now - I did use @thin for all derived files. I haven't
actively used Leo for the past few weeks, so the terminology is
slipping...
My problem has to do with starting with a blank myproject.leo. I don't
have a clear idea of how to proceed. I initially thought I'll do a top-
On Thu, Apr 10, 2008 at 7:43 AM, Ludwig Schwardt [EMAIL PROTECTED]
wrote:
When I tried to go deeper, I found it really hard to decide which
files I needed where in the Leo hierarchy. And what if the code in one
node needed code in another node? Do I clone it into the required
node, or do I
Also, use the following command if you want to always open gVim in tab
mode:
set showtabline=2 Tabs will always be displayed.
Note: (a non-Leo how-to) If tabs exist, it is easy to create an empty
tag by double clicking to the right of the last tab. You can then
drag a file into the tag's
On Wed, Apr 9, 2008 at 6:04 PM, TL [EMAIL PROTECTED] wrote:
Any questions?
Where do I start :-) I use vim just enough to verify that the previous vim
plugin worked, so your instructions are essentially incomprehensible to me.
Please assume I know *nothing* about vim, how it works, its features
On Apr 10, 3:27 pm, bobjack [EMAIL PROTECTED] wrote:
I've merged mod_rClick with the trunk. The api should be stable from
now on, barring bugs.
I should have said 'all unit tests passed'.
Bob
--~--~-~--~~~---~--~~
You received this message because you are
I've merged mod_rClick with the trunk. The api should be stable from
now on, barring bugs.
Docs for rClick and @popup:
The doc string of the rClick.py plugin
The testAtPopup.leo file in leo\test
The source code of the plugin.
The source code in particular contains several examples of the more
On Thu, Apr 10, 2008 at 5:05 PM, Edward K. Ream [EMAIL PROTECTED] wrote:
Here's a stopgap measure to survive 2 people editing the same .leo
file, with very little coding
I'm not sure I understand the problem you are trying to solve.
Two people editing the same .leo file in network share.
On Thu, Apr 10, 2008 at 9:31 AM, bobjack [EMAIL PROTECTED] wrote:
On Apr 10, 3:27 pm, bobjack [EMAIL PROTECTED] wrote:
I've merged mod_rClick with the trunk. The api should be stable from
now on, barring bugs.
I should have said 'all unit tests passed'.
Thanks for this work. We are
On Thu, Apr 10, 2008 at 9:59 AM, Edward K. Ream [EMAIL PROTECTED] wrote:
On Thu, Apr 10, 2008 at 9:31 AM, bobjack [EMAIL PROTECTED] wrote:
On Apr 10, 3:27 pm, bobjack [EMAIL PROTECTED] wrote:
I've merged mod_rClick with the trunk. The api should be stable from
now on, barring bugs.
On Thu, Apr 10, 2008 at 08:44:39AM -0500, Edward K. Ream wrote:
For programming projects, I organize my master .leo file in two ways: by
topic (Notes, Projects, To Do) and by file. I use @thin files like
leoNotes.txt, leoProjects.txt, leoToDo.txt and leoToDoLater.txt to keep the
actual .leo
On Thu, Apr 10, 2008 at 7:16 PM, Kayvan A. Sylvan [EMAIL PROTECTED] wrote:
with my python code (import a file, play with its classes, test out my
ideas), then update the code in Leo and back in ILeo, just reload the
module
and continue playing, ad infinitum. I get all the power of
14 matches
Mail list logo
