Ihor Radchenko <yanta...@gmail.com> writes: > I think I addressed the raised issues. > Just merged org-fold upstream.
👏 > Kévin Le Gouguec <kevin.legoug...@gmail.com> writes: > >> My recipe (based on commit f9dd109bc, Emacs 29.0.50 commit 864c8013fd): >> >> $ git switch feature/org-fold-universal-core-tidy >> $ make autoloads >> $ emacs -Q -L lisp -eval "(setq org-startup-folded t)" repro.org >> >> Restarting Emacs with the above between each step: >> >> (1) C-s abc ⇒ no logbook is unfolded, >> (2) C-s def ⇒ no logbook is unfolded, >> (3) C-s ghi ⇒ some logbooks are unfolded. >> >> Assuming you can reproduce: is it expected that logbooks are expanded in >> case (3)? I don't see what's "conceptually" different in situation (3) >> vs. (1) and (2), so I'm puzzled to get different results. > > I had a hard time to reproduce your recipe because it was related to > font-locking. The only way was increasing the font size, so that line > widths were larger than the frame width. Huh! Interesting; here I could trigger the bug with all lines fitting comfortably within the frame width; the longest is 70 columns long (line 69). ((frame-width) is 80; M-x describe-char says "DejaVu Sans Mono" 15) Anyway, thanks for your patience! font-lock problems are no joke 😕 > I believe I fixed the issue now. Seems fixed to me!
