yes, I'm on Linux, but like you I would not expect that to make a 
difference. Now that the topic has been raised again I will re-experiment 
and post (I can also try under Windows).

I think the @all causes all the contents of the nodes underneath to be 
included in the @clean file. There are alternatives here (@others etc ...); 
I have'nt tried those for a while and will have to remind myslef. My 
short-cut thinking is that @all should help things, not hinder them...

    J^n


On Thursday, October 17, 2024 at 2:14:11 PM UTC+1 tbp1...@gmail.com wrote:

> Funny.  I just tried it before I posted and it did create the file and the 
> inbetween directories at the end of the path. I'm on Windows and your path 
> looks like Linux but I wouldn't think that would make a difference.  I 
> don't know what the @all is supposed to do so I have no opinion as to 
> whether it changed the behavior.
>
> On Thursday, October 17, 2024 at 7:40:04 AM UTC-4 jkn wrote:
>
>> Interesting ... I was the person who raised the earlier topic I presume 
>> you are referring to. And I actually tried Thomas' settings suggestion ... 
>> and it didn't work for me.
>>
>> Or at least, IIRC I had to use a particular combination of @path and 
>> @clean nodes to get it to work ... and in a way that I was not yet able to 
>> decide if there is leo bug, or in my understanding of how this should work.
>>
>> I have a part-draft of a posting on this. I will try to finish it, but I 
>> think I had:
>>
>> @path /path/to/new/directory
>>     @clean mynewfile.txt    # has '@all'
>>         node1   # with contents
>>
>> and I was expecting this to create /path/to/new/directory/mynewfile.txt 
>> ... but it wasn't
>>
>>
>>
>>
>>
>>
>> On Thursday, October 17, 2024 at 11:05:32 AM UTC+1 Israel Hands wrote:
>>
>>> And indeed it does. First it labels the new directory with */Directory/* 
>>> - saving the outline doesn't create it. But adding a file node with @file 
>>> or @auto created both file and directory.  Is there a reason why creating 
>>> directories directly in path without any file contents would be a bad thing?
>>>
>>> ta
>>>
>>> IH
>>>
>>> On Thursday 17 October 2024 at 10:56:55 UTC+1 Israel Hands wrote:
>>>
>>>> I've just noticed a similar ish question just a few lines below mine, 
>>>> sorry for not noticing that. If I enable the create missing directories 
>>>> will all my troubles be gone. I'm going to try now. 
>>>>
>>>> On Thursday 17 October 2024 at 10:53:45 UTC+1 Israel Hands wrote:
>>>>
>>>>> I use path to create the directory node - fine. However Leo will not 
>>>>> create the directory in the file system until a file is created within 
>>>>> the 
>>>>> directory.
>>>>> So I could create the directory and file in the file system but that 
>>>>> isn't as neat as making Leo do the work.
>>>>> So I create an @auto node in the as yet uncreated (in the file system) 
>>>>> directory node and Leo complains when I try to save the outline because 
>>>>> it 
>>>>> can't save the @auto file because the  directory doesn't exist. 
>>>>> If I use the write file from node command - it offers the system file 
>>>>> requester which of course does not yet have the directory created in 
>>>>> it.....
>>>>>
>>>>> I feel I may be missing the bleeding obvious here!
>>>>>
>>>>> Ta 
>>>>>
>>>>> IH
>>>>>
>>>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/35575000-8041-4322-aaea-ff847e2e3e44n%40googlegroups.com.

Reply via email to