On Sat, Jan 14, 2012 at 9:13 AM, HansBKK hans...@gmail.com wrote:
I honestly think the lack of a clear statement on this topic in the docs
dangerous for relative newcomers to Leo and threatens its acceptance as a
data-safe working environment.
The post All about clone conflicts is my
From Terry's related thread
herehttps://groups.google.com/forum/#%21topic/leo-editor/4vazxXwWy8E/discussion
distinction between source files and output, or built, files.
I believe that is in effect what the safe-cloning rules, and the procedures
they imply which we've outlined in this
On Sat, Jan 14, 2012 at 1:45 AM, HansBKK hans...@gmail.com wrote:
I honestly think the lack of a clear statement on this topic in the docs is
dangerous for relative newcomers to Leo and threatens its acceptance as a
data-safe working environment.
Yes, some more words in the docs would be
of that problem.
Edward
In this other related concurrent
thread../d/msg/leo-editor/CyqaY1HS4eY/3rhy_IPW1kMJyou also state:
What we are seeing is the boundary between reasonable and unreasonable
uses of cross-file clones. That boundary is not sharp: whether cross-file
clones work depend
P.S. In your particular situation, I would suggest, if at all
possible, that you make complete external files, rather than clones,
to be the units of sharing. That way there is only one copy of the
data, so if you change that data outside of Leo all clones of (parts
of) that data will be in
On Fri, 13 Jan 2012 14:27:36 -0800
Matt Wilkie map...@gmail.com wrote:
I thought one of the major reasons for clones was to be able to
boiler plate common content across many files. Examples might
include copyright notices, written by _, code functions that get
re-used a lot and so on.
On Saturday, January 14, 2012 5:27:36 AM UTC+7, Matt Wilkie wrote:
P.S. In your particular situation, I would suggest, if at all possible,
that you make complete external files, rather than clones, to be the units
of sharing. That way there is only one copy of the data, so if you change
Why not?
Not sure, perhaps I just need to change my working style a bit.
I have a lot of information that I keep outside the @file nodes.
Documentation for example, which is not directly linked with the code.
I see you yourself are sharing information via Leo files, that are not
just reference
On Tue, Jul 12, 2011 at 5:57 AM, Josef joe...@gmx.net wrote:
Why not?
Not sure, perhaps I just need to change my working style a bit.
I have a lot of information that I keep outside the @file nodes.
Documentation for example, which is not directly linked with the code.
I see you yourself
On Thu, Jul 7, 2011 at 12:03 PM, Josef joe...@gmx.net wrote:
In my company, the others don't mind the sentinels, but since I use
leo as a storage for data which *inherently* needs or benefits from a
tree representation, this cannot be conveyed to others via the @file
nodes alone, but I must
On Jul 6, 11:37 am, Terry Brown terry_n_br...@yahoo.com wrote:
On Wed, 6 Jul 2011 10:46:17 -0500
Edward K. Ream edream...@gmail.com wrote:
Hmm. The docstring for the bookmarks plugin says that the plugin has
been superseded by the newly-improved handling of @url nodes.
Is this true?
There is jinjarender.py plugin that might be interesting. Check list archives
Largo84 larg...@gmail.com wrote:
Checked out genshi and django, they remind me of something similar
when I was considering using a CMS for my web site (they're called
template variables there, they serve the same
You won't have conflicts in the .leo files provided that you use
reference .leo files, as we do in the Leo project itself. See the
FAQ:http://webpages.charter.net/edreamleo/FAQ.html#leo-in-shared-environm...
So, I cannot share my non-reference files - that is a serious
limitation. It is these
I just had a look at leoGuiPluginsRef.leo and it contains a lot more
than just @file nodes: @chapters, @settings, commented out buttons
etc.
so, is the statement: Ref files should contain nothing but @file,
@auto and @shadow nodes the whole truth?
I also used (successfully) clones in my leo
On Jul 6, 8:10 am, Edward K. Ream edream...@gmail.com wrote:
You won't have conflicts in the .leo files provided that you use
reference .leo files, as we do in the Leo project itself. See the
FAQ:http://webpages.charter.net/edreamleo/FAQ.html#leo-in-shared-environm...
This is perhaps a
On Jul 7, 10:27 am, Edward K. Ream edream...@gmail.com wrote:
The acid test is whether Leo can be used by some, but not all,
developers on a significant project. At present, the best that can be
done in such situations is to use @auto or (maybe) @shadow for the
group's files. This is far
One can imagine situations in which the developers that don't use Leo
are not hostile to having Leo's sentinels in the group's files. In
this case, @file can be used and there are no problems.
In my company, the others don't mind the sentinels, but since I use
leo as a storage for data which
That worries me. So far I have been the only one working with Leo in
my company, but lately others have started to pick up Leo as well. As
the main cooperation tool we use SVN, so I check in my Leo files as
well. Now either we are all going to work with the same Leo files,
which will probably lead
On Wed, Jul 6, 2011 at 3:08 AM, Josef joe...@gmx.net wrote:
That worries me. So far I have been the only one working with Leo in
my company, but lately others have started to pick up Leo as well. As
the main cooperation tool we use SVN, so I check in my Leo files as
well. Now either we are all
On Wed, Jul 6, 2011 at 9:16 AM, Terry Brown terry_n_br...@yahoo.com wrote:
On Wed, 6 Jul 2011 01:08:02 -0700 (PDT)
Josef joe...@gmx.net wrote:
I understand that this will work fine as long as we are not using
clones, but then we loose one of the best features of Leo!
That depends what you
On Wed, 6 Jul 2011 10:46:17 -0500
Edward K. Ream edream...@gmail.com wrote:
Hmm. The docstring for the bookmarks plugin says that the plugin has
been superseded by the newly-improved handling of @url nodes.
Is this true?
Not entirely. You put that there, by the way :-)
Basically all the
That depends what you use clones for. If you use them for collecting a
short list of nodes of current interest from a larger tree, you can get
basically the same effect from the bookmarks.py and quickMove.py
plugins. With those plugins enabled, create a node with a headline
containing
On Wed, 6 Jul 2011 19:12:20 -0700 (PDT)
Largo84 larg...@gmail.com wrote:
That depends what you use clones for. If you use them for collecting a
short list of nodes of current interest from a larger tree, you can get
basically the same effect from the bookmarks.py and quickMove.py
Fair enough, that's an entirely different application. What I was
describing was my alternative to clones in the context of python source
code writing. For what you're doing I usually use a template language
like genshi or django-templates which has some sort of include
mechanism that can
Checked out genshi and django, they remind me of something similar
when I was considering using a CMS for my web site (they're called
template variables there, they serve the same function of substituting
repeatable text blocks). Conceptually, they make sense but I wouldn't
even know where to get
On Tue, Jul 5, 2011 at 2:47 PM, Largo84 larg...@gmail.com wrote:
Sorry if the answer is obvious, it's not to me. Should I avoid cloned
nodes in @files that are referenced in different .leo files?
Yes, you should avoid such clones, for the reasons you imply. Imo,
every piece of data, of
26 matches
Mail list logo
