From: "Thomas S. Dye" <tsd@tsdye.online>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "Thomas S. Dye" <tsd@tsdye.online>,
Michael Dauer <mick.dauer@gmail.com>,
numbchild@gmail.com, emacs-orgmode@gnu.org
Subject: Re: BUG: org-cycle does not unfold some subtrees
Date: Sat, 06 May 2023 08:39:42 -1000 [thread overview]
Message-ID: <874jop9tki.fsf@tsdye.online> (raw)
In-Reply-To: <87a5yhz5wi.fsf@localhost>
Ihor Radchenko <yantar92@posteo.net> writes:
> "Thomas S. Dye" <tsd@tsdye.online> writes:
>
>>> But some third-party package might be.
>>> May you try disabling various extra packages and see if the
>>> problem persists?
>>
>> If it helps, I get this bug using the Spacemacs Org mode layer
>> and
>> Emacs 27.
>
> Sorry, but it does not help.
> Without reproducer, I can only guess.
>
> And I do not see any bug reports in Spacemacs repo. So, you
> likely has
> something else contributing.
OK, that helps.
For me, the bug bites intermittently. I often run an Emacs
instance for more than a week before I'm bitten, so it will likely
be a long process to work through the packages loaded on top of
what Spacemacs loads to make a reproducer.
Also, I anticipate a problem deciding that removing a package has
squashed the bug; will two weeks without the bug be long enough?
Three? Four or more?
I've found that I can work around the bug by moving the headline
up or down. Once this is done, the headline unfolds. Then, when
I move it back to its original position, it still unfolds
properly. For me, this is easier than my first workaround, which
involved stopping and re-starting the Emacs instance.
Possibly related, I intermittently get bits of text following the
ellipsis that indicates a folded headline. My impression is that
this happens when the bug has bitten a folded headline, but if I
remember correctly, the bug and the bits of text following the
ellipsis are not on the same heading. I'll check systematically
next time I see this, if you think it might help.
All the best,
Tom
--
Thomas S. Dye
https://tsdye.online/tsdye
next prev parent reply other threads:[~2023-05-06 18:58 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 [this message]
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
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=874jop9tki.fsf@tsdye.online \
--to=tsd@tsdye.online \
--cc=emacs-orgmode@gnu.org \
--cc=mick.dauer@gmail.com \
--cc=numbchild@gmail.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).