Interesting, that's a good point, thanks for the info.
On Fri, 2020-08-14 at 07:49 -0700, Thomas Passin wrote:
>
>
> On Friday, August 14, 2020 at 10:17:20 AM UTC-4, k-hen wrote:
> > Thank you kindly for your reply. I've enabled this feature and it
> > seems very promising, but I think I might
On Fri, Aug 14, 2020 at 9:17 AM wrote:
In a perfect world, I could specify a sync directory in Leo and it would
> automatically import all of the files in those directories,
>
Please have a look at the active_path and at_folder plugins.
Edward
--
You received this message because you are
On Friday, August 14, 2020 at 10:17:20 AM UTC-4, k-hen wrote:
>
> Thank you kindly for your reply. I've enabled this feature and it seems
> very promising, but I think I might need a slightly different behaviour.
> I'll take a minute to explain the use case.
>
> [snip]
> This is likely the
Thank you kindly for your reply. I've enabled this feature and it seems
very promising, but I think I might need a slightly different
behaviour.I'll take a minute to explain the use case.
In our git project we have a docs directory which is a simple
collection of markdown files. This works great
On Thu, Aug 13, 2020 at 10:29 PM Thomas Passin wrote:
>
>
> On Thursday, August 13, 2020 at 7:31:02 PM UTC-4, k-hen wrote:
>>
>> [snip]
>>
>
> Would you file a bug issue on this? The issue URL is
>
> https://github.com/leo-editor/leo-editor/issues
>
My apologies for not jumping in yesterday.
On Thursday, August 13, 2020 at 7:31:02 PM UTC-4, k-hen wrote:
>
> [snip]
>
Would you file a bug issue on this? The issue URL is
https://github.com/leo-editor/leo-editor/issues
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe
Why is it that you want to use auto-md trees? You could consider
ReStructured text, for example.
On Thursday, August 13, 2020 at 7:31:02 PM UTC-4, k-hen wrote:
>
> Well, Glad I'm in good company :-)
>
> I'm thinking the workaround is to use a the full path for every @auto
> headline, rather
Well, Glad I'm in good company :-)
I'm thinking the workaround is to use a the full path for every @auto
headline, rather than nesting @path nodes?.Is there perhaps a way to do
expansion on the filename within a headline or something so I don't
need to repeat it all?
It doesn't seem wise to clone
Aha! I duplicated this behavior. I got the same loss of clone-hood in an
@auto-md tree. I did not get it in an @file tree. When I cloned a node in
an @auto-md tree and dragged it out of the tree, it still lost its clone
status whe I closed and reloaded the file.
On Thursday, August 13, 2020
I've been thinking about this a bit more, and I'm thinking this is
probably expected and I just wasn't thinking about it properly.Since
this is an *auto* node, perhaps it's clearing & reloading the
descdendant nodes of my file on the load of Leo.So the clone is there
originally, then it deletes
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
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
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
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,
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 :-/
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
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
17 matches
Mail list logo
