From: "Christopher M. Miles" <numbchild@gmail.com>
Cc: Ihor Radchenko <yantar92@posteo.net>,
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 14:43:00 +0800 [thread overview]
Message-ID: <m2lei2vtmf.fsf@numbchild@gmail.com> (raw)
In-Reply-To: <6455a3ec.c80a0220.7ded4.665aSMTPIN_ADDED_BROKEN@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
"Christopher M. Miles" <numbchild@gmail.com> writes:
> [[PGP Signed Part:Undecided]]
>
> I meet an unfold-able headline now. Then I record a video to show this
> unfold-able headline. I executed command "describe-text-properties".
> Afterwards, I closed the buffer, then re-open the file to show the
> headline can be expanded normally, and show the subtree content.
>
> Here is the uploaded video (P.S, I know video link is not a good way to
> archive information in mailing list, but this problem seems can't be
> text-described simply. Sorry about this.):
>
> https://upload.disroot.org/r/QNhW1xz0#X2or/2T7i7Kb7pHPxfAupRaEYJ28Sbp+2R6UDREnFic=
I recorded a new video which contains the Edebug process. Which shows
the `org-cycle' function internal status data. Ihor, hope this can help
you find the reason.
https://upload.disroot.org/r/khVnJgYV#vMBC3hiBUoPqBG2bgTEfJb44AUrGXVDuvpVGKv8Vw+w=
--
[ stardiviner ]
I try to make every word tell the meaning that I want to express without misunderstanding.
Blog: https://stardiviner.github.io/
IRC(libera.chat, freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2023-05-06 6:53 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
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 [this message]
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=m2lei2vtmf.fsf@numbchild@gmail.com \
--to=numbchild@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mick.dauer@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).