I'm traveling now, so I can't look at the attached file now. However, I had 
similar challenges w/ clones until I figured out a few things:

   1. It's generally best (for me anyway) to *not* clone the entire @file 
   node; only the sub-node(s) that require cloning. That way, the @path of the 
   cloned nodes becomes irrelevant.
   2. In the rare cases where I do need to clone the entire @file node, I 
   have to ensure the @path trees match the directory trees. The @path string 
   is not inside my @file nodes, but in the nodes above.

Hope that makes sense and hope that helps. Regards,


On Friday, April 13, 2018 at 6:35:06 AM UTC-7, k-hen wrote:
> Hi All,
> I'm still having a problem with the @path directive when using using file 
> clones. Attaches is a simplified example.
> In the attached, If I don't have file clones the path works fine, but as 
> soon as I add the file clones the path gets lost and it writes them to the 
> root directory. 
> I tried to work around this by separating the file *contents* from the 
> @clean node and cloning the contents instead. 
> This saves the @path, but then I lose the @language directive and the 
> syntax highlighting. 
> If I add the @language directive to the child content node then it writes 
> that line in the output file which also doesn't work.
> I suppose my only option now is to include the full pathname in every file 
> (I have hundreds) but that doesn't seem like a great solution.
> Any guidance would be appreciated.
> Thanks,
> Kevin
> On Tuesday, April 10, 2018 at 6:05:55 PM UTC-2:30, k-hen wrote:
>> Hi Again,
>> There's a tip that says to clone your file nodes and put the clones in a 
>> folder at the end of the outline to match your output directories.
>> Also, there has been some notices recently regarding using @path 
>> directives, potentially recursively to simply your @file naming.
>> Both of these seem great.
>> I have this set up now, but some of the files aren't picking up the @path 
>> directives from the last node.
>> Also, not sure if this is related but performance has gotten 
>> significantly worse since doing this.
>> So .... I'm not sure ... 
>> Is there a 'primary' version of the @file (or @clean in my case) which 
>> would define the @path? (I'm hoping it's the ending?)
>> i.e. does it matter if you clone from Section A to Section B vs Section B 
>> to Section A?
>> Should it only be the _contents_ of the file and not the actual @file 
>> headline node that gets cloned?
>> Should the @path's be higher up in the outline?
>> Should I just stick with fully qualified file names?
>> Loving Leo so far but I've still got lots to learn.
>> Thanks very much,
>> Kevin
>> P.S. Using leo 5.7.1 master branch from git

You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to