Is it correct that you only are seeing this behavior on (a?) auto-md file?

On Thursday, August 13, 2020 at 5:46:36 PM UTC-4, k-hen wrote:
>
> Hi Felix,
> I am also perplexed. Note that the clones which are not a descendant of 
> the file don't have this behaviour either.
>
> I first encountered this in my large document using the pip version (6.2). 
> I was able to reproduce this however using both a new/fresh/extremely 
> small .leo file, 
> I was also encountered this after installing/using the git version 
> (6.3-devel). 
>
> I don't have any custom scripts or plugins, only the defaults.
>
>
> Kevin
>
>
>
>
> On Thursday, August 13, 2020 at 4:59:08 PM UTC-4 Félix wrote:
>
>> That's weird,
>>
>> For a leo file to change between having 2 positions be clone of each 
>> other, to being two distinct nodes, happening to have the same headline and 
>> content, requires a non-trivial change...
>>
>> Would be curious to see if you dont have scripts or plugins enabled that 
>> would make changes to your document while its saving it. 
>>
>> Do you have the bug in a completely new file with only two simple nodes 
>> (clones), saving the file, closing the file, then re-opening it?
>>
>> Or do you have this bug only in a particular Leo file ?
>> --
>> Félix
>>
>>
>> On Thursday, August 13, 2020 at 1:59:51 PM UTC-4, k-hen wrote:
>>>
>>> I saw another post from today about cloning, so I've checked out the 
>>> current devel branch - and unfortunately it's happening there for me also 
>>> :-(
>>> The post says something about 'clones' branch, but I don't see one of 
>>> those.
>>>
>>>
>>> On Thursday, August 13, 2020 at 1:46:13 PM UTC-4 k-hen wrote:
>>>
>>>> OK, so I've been able to repeat the behaviour at least.
>>>> I created a new outline and cloned a node and it worked fine.
>>>>
>>>> Then for my use case I have an @auto-md clone_test.md with a child node 
>>>> that is being cloned and moved out, and that one is also dropping the 
>>>> clone 
>>>> after restarting leo :-/
>>>>
>>>>
>>>>
>>>>
>>>> On Thursday, August 13, 2020 at 1:38:53 PM UTC-4 tbp1...@gmail.com 
>>>> wrote:
>>>>
>>>>> You aren't doing anything wrong, but it shouldn't be happening.  I 
>>>>> don't lose my clones that way.  I happen to be on the devel branch but I 
>>>>> don't think that's a factor here:
>>>>>
>>>>> Leo 6.3-devel, devel branch, build 6a92120f1a
>>>>> 2020-06-23 09:38:53 -0500
>>>>> Python 3.8.2, PyQt version 5.14.2
>>>>> Windows 10 AMD64 (build 10.0.18362) SP0
>>>>>
>>>>> Maybe Edward could shed some light here.
>>>>>
>>>>> On Thursday, August 13, 2020 at 1:24:19 PM UTC-4, k-hen wrote:
>>>>>>
>>>>>> Hi,
>>>>>> I'm not sure if this is a bug or if I'm doing something wrong. I've 
>>>>>> created some cloned nodes, and the icon is correct and they work as I 
>>>>>> expect, but as soon as I close & reopen leo they become non-cloned 
>>>>>> (copied) 
>>>>>> nodes. 
>>>>>>
>>>>>> I first tried using an in-place clone (ctrl+`) then dragging the 
>>>>>> clone out, and also tried copy/paste-as-clone but got the same behaviour 
>>>>>> both times.
>>>>>>
>>>>>> Am I missing something?
>>>>>>
>>>>>> I'm using Leo installed via pip,  
>>>>>> Leo 6.2.1 final
>>>>>> Python 3.6.3, PyQt version 5.14.2
>>>>>> Windows 10 AMD64 (build 10.0.14393) SP0
>>>>>>
>>>>>> Thanks,
>>>>>> Kevin
>>>>>>
>>>>>>

-- 
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/1a90b382-50f0-43b1-8108-73e52527f11bo%40googlegroups.com.

Reply via email to