where do marks escape?

[gar]

Recently I invented an approach how to navigate in a huge amount of nodes to the ones I currently work with.

I cannot clone them since most of them in the @auto containers - but I mark them and navigate from one to another when needed with goto-next/prev-marked.

But I found that marks suspiciously disappear after random amount of navigations.

Is that the intended behavior? If so - it is very unfriendly and I cannot understand it.

[Edward K. Ream]

On Mon, Jan 27, 2020 at 10:26 PM gar <gar...@gmail.com> wrote:

> I found that marks suspiciously disappear after random amount of navigations.

Marks are contained in Leo's caches, in ~/.leo/db. They should persist until you clear the caches.

Edward

[gar]

Actually they do not. They disappear time after time (and not all of
them - so this is not result of cache clearing).
So looks like this is not intended behavior. I will try to understand
when this happens.

> --
> 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+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/leo-editor/CAMF8tS2A-PoDLagMuC%2BKg%2BxCgjxh_D5kYqP1q41%2BbdxcSVTTPw%40mail.gmail.com.
>

[gar]

One of the reasons (and may be the only one) why it behaves in that manner: undo.

When user undoes something - it also can be applied to marks too.

This seems not intuitive to me... I would like to have an option turn it off.

[Edward K. Ream]

On Tuesday, January 28, 2020 at 5:17:16 AM UTC-6, gar wrote:

Actually they do not. They disappear time after time (and not all of them - so this is not result of cache clearing).

Marks and expansion bits definitely exist in the c.db cache. fast.handleBits reads the bits, fc.setCachedBits writes them.

I have just created #1484 for this issue.

Edward

[gar]

Also discovered that when parent node is collapsed - mark _may_ dissappear (this happens not every time, and may happen never, actually).

It may happend even if you start a search with F3 (which occasionally collapses the whole tree). 

[Edward K. Ream]

On Mon, Feb 3, 2020 at 12:42 AM gar <gar...@gmail.com> wrote:

Also discovered that when parent node is collapsed - mark _may_ dissappear (this happens not every time, and may happen never, actually).

It may happend even if you start a search with F3 (which occasionally collapses the whole tree). 

Thanks for these remarks. I have recorded them in #1483.

Edward

[gar]

Another case. When saving outline latest set mark may disappear.

[Edward K. Ream]

On Thu, Feb 6, 2020 at 3:27 AM gar <gar...@gmail.com> wrote:

Another case. When saving outline latest set mark may disappear.

Noted in #1484.

Edward

[Thomas Passin]

I can confirm erratic mark disappearances.  Usually  they seem to persist through several bouts of closing and opening Leo, but I'm never sure they will be there.

BTW, I have set up these hot keys for marks:

F4 - go to next mark

F9 - set mark on node

F10 - clear all marks

I used these keys because they are used in EditPlus, and I have many years of habits from using it.  The only difference is that in EditPlus F9 toggles a mark rather than simply turning it on, and I like that behavior better.

@ekr, would you be amenable to adding a mark-toggle command?  If so I'll post an enhancement request on GitHub.  I imagine it would be pretty easy, so I could probably adapt existing mark and clear code myself, come to that.

[Edward K. Ream]

On Mon, Mar 2, 2020 at 8:37 AM Thomas Passin <tbp1...@gmail.com> wrote:

I can confirm erratic mark disappearances.  Usually  they seem to persist through several bouts of closing and opening Leo, but I'm never sure they will be there.

Thanks for the confirmation of #1484.

Edward