Re: [9.4] LOGBOOK visibility

2020-07-04 Thread Ihor Radchenko
> FWIW, I think Emacs has a branch (feature/noverlay) which has been > reported to improve performance with overlays. AFAICT it's just hanging > there waiting to be merged (though a naive "git merge" reveals some > conflicts); some quick Googling suggests it has last been discussed two > years

Re: [9.4] LOGBOOK visibility

2020-07-04 Thread Kévin Le Gouguec
Thank you for taking the time to make this write-up. Nicolas Goaziou writes: > With overlays, you can't have your cake > and eat it too. FWIW, I think Emacs has a branch (feature/noverlay) which has been reported to improve performance with overlays. AFAICT

Re: [9.4] LOGBOOK visibility

2020-07-04 Thread Nicolas Goaziou
Hello, Ihor Radchenko writes: > There used to be several types of overlays for headline folding, drawer > folding, and block folding. One of the recent commits made all the > overlays use headline type. As a result all the overlays are merged into > a single overlay upon folding. This was done

Re: [9.4] LOGBOOK visibility

2020-07-04 Thread Kévin Le Gouguec
Ihor Radchenko writes: > (see the discussion in [1]). Ah, that makes sense! No idea how I managed to miss that thread. > I am currently working on a patch to rewrite the whole folding system. > Your issue should disappear once it is applied. Good to know! > Meanwhile, you

Re: [9.4] LOGBOOK visibility

2020-07-03 Thread Ihor Radchenko
> Meanwhile, you may, for example, advice > org-fold--isearch-filter-predicate to re-fold drawers during isearch. org-fold--isearch-filter-predicate->isearch-filter-visible Ihor Radchenko writes: >> I haven't reached the bottom of this rabbit hole yet. Since I think >> I've spent all the

Re: [9.4] LOGBOOK visibility

2020-07-03 Thread Ihor Radchenko
> I haven't reached the bottom of this rabbit hole yet. Since I think > I've spent all the time I had to spend in this issue for the day, here's > where I'm at. There used to be several types of overlays for headline folding, drawer folding, and block folding. One of the recent commits made all

Re: [9.4] LOGBOOK visibility

2020-07-03 Thread Kévin Le Gouguec
I haven't reached the bottom of this rabbit hole yet. Since I think I've spent all the time I had to spend in this issue for the day, here's where I'm at. If I open my example file[1] with Org 9.3 and master (86fada6b5), and compare the overlays covering the hidden part of the first LOGBOOK

Re: [9.4] LOGBOOK visibility

2020-07-03 Thread Kévin Le Gouguec
Kévin Le Gouguec writes: > For example, in the attached file, if I search for "bug#5": > > - Org 9.3 keeps the drawers closed, > - Org 9.4 opens every drawer for bugs 4, 5 and 6. > > AFAICT Org 9.3 never opened these drawers unless either > org-startup-folded was showeverything, the user

[9.4] LOGBOOK visibility

2020-07-02 Thread Kévin Le Gouguec
Hi, I've noticed that LOGBOOK drawers are now (9.4) open by default when visiting an Org file, AFAICT as a result of org-startup-folded now defaulting to showeverything. That's not much of a problem by itself; what I find more of a hindrance is that even with "#+STARTUP overview", when one