From: William Denton <wtd@pobox.com>
To: Bruno Barbier <brubar.cs@gmail.com>
Cc: Daniel Hubmann <hubisan@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [BUG] Incorrect display of folded headings after cycling with subheading with VISIBILITY content/children
Date: Tue, 14 Feb 2023 16:15:27 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2302141612001.67798@shell3.miskatonic.org> (raw)
In-Reply-To: <63ebd56e.1c0a0220.7fd3f.2faf@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 973 bytes --]
On 14 February 2023, Bruno Barbier wrote:
> Daniel Hubmann <hubisan@gmail.com> writes:
>
>> After using org-cycle-overview (or org-cycle-content) and then using
>> org-cycle-set-visibility-according-to-property I get this:
>>
>> * Heading Lvl 1...** Heading Lvl 2 with VISIBILITY content...
>> *** Heading Lvl 3...
>
> I'm observing the same behavior.
Similar things have been happening to me since the middle of last year.
See:
https://lists.gnu.org/archive/html/emacs-orgmode/2022-07/msg00368.html
https://lists.gnu.org/archive/html/emacs-orgmode/2022-05/msg00811.html
(my screenshots are gone by they looked like what's been described)
Ihor did some work but the problem is still going on now and then, in the sort
of way that seems unreproducible to me.
Bill
--
William Denton
https://www.miskatonic.org/
Librarian, artist and licensed private investigator.
Toronto, Canada
CO₂: 421.18 ppm (Mauna Loa Observatory, 2023-02-13)
next prev parent reply other threads:[~2023-02-14 21:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 10:05 [BUG] Incorrect display of folded headings after cycling with subheading with VISIBILITY content/children Daniel Hubmann
2023-02-14 18:39 ` Bruno Barbier
2023-02-14 21:15 ` William Denton [this message]
2023-02-15 9:36 ` Daniel Hubmann
2023-02-15 15:31 ` Ihor Radchenko
2023-02-15 22:26 ` Daniel Hubmann
2023-02-15 23:03 ` Daniel Hubmann
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=alpine.DEB.2.22.394.2302141612001.67798@shell3.miskatonic.org \
--to=wtd@pobox.com \
--cc=brubar.cs@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=hubisan@gmail.com \
/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).