From: Ihor Radchenko <yantar92@posteo.net>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: John Mathena <jmmathena@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [BUG] Child's visibility property is overridden by parent's [9.5.2 (9.5.2-gbc8c3e @ /home/john/.emacs.d/straight/build/org/)
Date: Tue, 30 Jan 2024 13:48:26 +0000 [thread overview]
Message-ID: <87v87bue39.fsf@localhost> (raw)
In-Reply-To: <87tucu99od.fsf@localhost>
Ihor Radchenko <yantar92@gmail.com> writes:
> I would say that the existing behaviour is a confusing and might be
> considered as a bug. However, it may not always be straightforward how
> to deal with different combinations of VISIBILITY setting for
> ancestor/descendent headings. Consider the following example:
>
> * Foo
> :PROPERTIES:
> :VISIBILITY: folded
> :END:
> ** Bar
> :PROPERTIES:
> :VISIBILITY: content
> :END:
> *** Baz
>
> Foo is supposed to be folded, but it is unclear how to process Bar.
> Should Bar's contents be visible? Should it be folded?
My conclusion is that Bar should be visible. This will be consistent
with how VISIBILITY overrides document-wide STARTUP settings.
Also, the comment in one of Org tests I was concerned about was
inaccurate - it tested for a slightly different bug.
Fixed, on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=a5c977b43
--
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>
prev parent reply other threads:[~2024-01-30 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 15:23 [BUG] Child's visibility property is overridden by parent's [9.5.2 (9.5.2-gbc8c3e @ /home/john/.emacs.d/straight/build/org/) John Mathena
2022-02-19 15:07 ` Ihor Radchenko
2024-01-30 13:48 ` Ihor Radchenko [this message]
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=87v87bue39.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=jmmathena@gmail.com \
--cc=yantar92@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).