From: Gregor Zattler <telegraph@gmx.net>
To: Michael Dauer <mick.dauer@gmail.com>,
Ihor Radchenko <yantar92@posteo.net>
Cc: William Denton <wtd@pobox.com>, "Fraga, Eric" <e.fraga@ucl.ac.uk>,
"Thomas S. Dye" <tsd@tsdye.online>,
"numbchild@gmail.com" <numbchild@gmail.com>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: BUG: org-cycle does not unfold some subtrees
Date: Sun, 14 May 2023 13:53:46 +0200 [thread overview]
Message-ID: <87ttwf86yd.fsf@no.lan> (raw)
In-Reply-To: <CAP7OBx+L11ck3Ni6rv94HGU3otdj6C4rG-rMDzkwR1LTj=BWiw@mail.gmail.com>
Hi Michael, Ihor, ...
* Michael Dauer <mick.dauer@gmail.com> [2023-05-14; 12:56 +02]:
> I think I found a way to consistently reproduce the issue:
>>>>
> * h1
> aaaaa
> * h2
> bbbbb
> * h3
> bbbbb
> * h4
> ccccc
> <<<
> Collapse all. All is fine at this time.
> At pos-min call (query-replace) bbb -> zzz: Already when asking whether to
> replace it cannot expand. h2 and h3 are expansion is broken.
I confirm this recipe. For me and with my
configuration, as with emacs -Q, I then cannot unfold
h2.
> (org-fold-core--clear-isearch-overlays) repairs it.
This is also the case with my configuration, as with
emacs -Q.
Then I can unfold all headings and see that the
replacement bbb --> zzz worked.
GNU Emacs 29.0.90 (build 1, x86_64-pc-linux-gnu, cairo version 1.16.0) of 2023-05-04
Org mode version 9.7-pre (release_9.6.5-357-g080710 @ /home/grfz/src/org-mode/lisp/)
Ciao; Gregor
next prev parent reply other threads:[~2023-05-14 11:55 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 17:35 BUG: org-cycle does not unfold some subtrees Michael Dauer
2023-05-05 17:46 ` Ihor Radchenko
2023-05-05 18:40 ` Michael Dauer
2023-05-05 20:18 ` Ihor Radchenko
2023-05-06 0:44 ` Christopher M. Miles
2023-05-06 6:27 ` Ihor Radchenko
2023-05-06 7:18 ` Michael Dauer
2023-05-06 7:22 ` Michael Dauer
2023-05-06 7:39 ` Ihor Radchenko
2023-05-06 8:22 ` Michael Dauer
2023-05-06 8:31 ` Ihor Radchenko
2023-05-06 17:46 ` Thomas S. Dye
2023-05-06 18:11 ` Ihor Radchenko
2023-05-06 18:39 ` Thomas S. Dye
2023-05-06 19:06 ` Ihor Radchenko
2023-05-06 20:25 ` Thomas S. Dye
2023-05-09 0:32 ` Thomas S. Dye
2023-05-09 6:27 ` Ihor Radchenko
2023-05-09 6:43 ` Michael Dauer
2023-05-09 7:34 ` Ihor Radchenko
2023-05-09 7:53 ` Thomas S. Dye
2023-05-09 9:53 ` Michael Dauer
2023-05-09 10:41 ` Ihor Radchenko
2023-05-10 1:56 ` William Denton
2023-05-10 7:54 ` Fraga, Eric
2023-05-10 8:19 ` Ihor Radchenko
2023-05-10 11:23 ` Fraga, Eric
2023-05-10 15:18 ` William Denton
2023-05-11 9:50 ` Ihor Radchenko
2023-05-11 13:34 ` William Denton
2023-05-11 13:46 ` Ihor Radchenko
2023-05-11 13:52 ` William Denton
2023-05-12 12:21 ` Ihor Radchenko
2023-05-12 21:01 ` William Denton
2023-05-12 21:15 ` Ihor Radchenko
2023-05-12 21:36 ` Thomas Dye
2023-05-14 10:56 ` Michael Dauer
2023-05-14 11:53 ` Gregor Zattler [this message]
2023-06-01 11:37 ` Ihor Radchenko
2023-08-04 13:42 ` Michael Dauer
2023-08-04 14:04 ` Ihor Radchenko
2023-08-04 14:11 ` William Denton
2023-08-08 15:21 ` Michael Dauer
2023-08-08 17:10 ` Ihor Radchenko
2023-08-09 9:14 ` Michael Dauer
2023-08-09 9:15 ` Michael Dauer
2023-08-09 9:19 ` Ihor Radchenko
2023-05-06 13:39 ` Christopher M. Miles
[not found] ` <6455a3ec.c80a0220.7ded4.665aSMTPIN_ADDED_BROKEN@mx.google.com>
2023-05-06 6:43 ` Christopher M. Miles
2023-05-05 23:18 ` Christopher M. Miles
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ttwf86yd.fsf@no.lan \
--to=telegraph@gmx.net \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=mick.dauer@gmail.com \
--cc=numbchild@gmail.com \
--cc=tsd@tsdye.online \
--cc=wtd@pobox.com \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).