From: Michael Dauer <mick.dauer@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: BUG: org-cycle does not unfold some subtrees
Date: Fri, 5 May 2023 20:40:01 +0200 [thread overview]
Message-ID: <CAP7OBxJ8nzyWeL08bvbe+=49SUfJ+u8ng=ONSNNV_aAsNSFRHg@mail.gmail.com> (raw)
In-Reply-To: <87o7mybris.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
This is with the cursor on the first asterisk:
Text content at position 299:
There are text properties here:
display [Show]
face org-level-1
fontified t
I could not test more positions because I accidentally cut it, and even an
undo fixed it. I would have to wait until it happens again.
Am Fr., 5. Mai 2023 um 19:43 Uhr schrieb Ihor Radchenko <yantar92@posteo.net
>:
> Michael Dauer <mick.dauer@gmail.com> writes:
>
> > Based on my analyses it's not the cycle functions, but must come from
> > broken text attributes. Even (org-fold-core-region (point-min)
> (point-max)
> > nil) does not unfold the affected subtrees then. Assuming that
> > (org-fold-core-region) is the only place where the folding and
> > hiding happens, I expect the problem there. But I understand too little
> > about the emacs internals to debug this function.
>
> May you please put a point right before the problematic fold, run
> M-x describe-text-properties <RET>, and share the contents of the newly
> displayed buffer listing all the text properties?
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at <https://orgmode.org/>.
> Support Org development at <https://liberapay.com/org-mode>,
> or support my work at <https://liberapay.com/yantar92>
>
[-- Attachment #2: Type: text/html, Size: 2072 bytes --]
next prev parent reply other threads:[~2023-05-05 18:41 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 [this message]
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
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='CAP7OBxJ8nzyWeL08bvbe+=49SUfJ+u8ng=ONSNNV_aAsNSFRHg@mail.gmail.com' \
--to=mick.dauer@gmail.com \
--cc=emacs-orgmode@gnu.org \
--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).