@path usage question

[William Strømsvold]

I use Leo for mostly everything at work, which includes matlab, python, project reports, summaries, links + +. From Leo I try to generate a workspace directory structure which is something like:

-Workspace
--matlab
--python
--meetings
--reports

I have a different @path on every parent node (matlab, python, report etc)

When I create a matlab file I do it under the matlab node with @shadow calculations.m, with an @path on the parent node (which is matlab). Often I want to clone this source code into the project report, but run into problems with conflicting paths. I have another @path for reports.

How do you solve this? I've tried to remove some of the path directives, and write the path directly for each file (@shadow matlab\calculations.m), but then some of the smoothness of using the @path directive disappears.

Anyone else with the same issues? Any smart ways to solve this?

-William S.

[TL]

> Often I want to clone this source code into the project report,
> but run into problems with conflicting paths.

Can you clarify. Is your "source code" in a separate node that you
have cloned? What is meant by "problems with conflicting paths"?

[Edward K. Ream]

Cloning an @<file> node (@thin, @shadow, etc.) an putting that clone under another @path is almost guaranteed to cause problems. @<file> nodes are designed to describe a single external file.

I'm not sure this is actually what you are describing, but if it is, don't do it :-)

My suggestions is that you clone parts of files, not entire external files.  If you do that, @path shouldn't matter.

Edward

[William Strømsvold]

The problem is when I want to clone an @thin node for example, and the target for the clone is another node with another path. I see this problem, so I've come to the conclusion that I should only clone  parts of the derived file (as Edward said). It also came to me that i can mark many nodes and clone them in one operation, in which the marked nodes are cloned to under a new node, and then move this node with all the cloned subnodes to wherever I want them.

-William S.

2009/11/9 Edward K. Ream <edre...@gmail.com>