emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Mathena <jmmathena@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [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, 15 Feb 2022 09:23:49 -0600	[thread overview]
Message-ID: <CADywB5+P_42Xc27GQWfwMomdkCr9_+Q1N21C9AOfkc6X61R3ug@mail.gmail.com> (raw)

It seems like the visibility property on a parent heading overrides
the visibility property on a child heading - is this expected? e.g.
when I have the raw text:

* Foo
:PROPERTIES:
:VISIBILITY: content
:END:
** Bar
:PROPERTIES:
:VISIBILITY: folded
:END:
*** Baz

... I would expect (and would like) to see

* Foo...
 * Bar...

that is, where Foo shows only the content below it, and Bar has all of
its children folded. Instead, I get

* Foo...
 * Bar...
  * Baz...

i.e., behavior like if Foo and Bar both "had their visibility" set to
"content" (I'm aware that's not how the internals work but I'm not
sure how else to articulate what I mean). Is there a way to prevent
this and get the behavior I'd expect?

This behavior was reproduced with straight.el on Org mode version
9.5.2 (9.5.2-gbc8c3e @ /home/john/.emacs.d/straight/build/org/, GNU
Emacs 27.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.27, cairo
version 1.17.4) of 2021-03-26, with org-startup-folded set to nil
(without which the visibility properties don't take effect).

Best,

John


             reply	other threads:[~2022-02-15 15:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 15:23 John Mathena [this message]
2022-02-19 15:07 ` [BUG] Child's visibility property is overridden by parent's [9.5.2 (9.5.2-gbc8c3e @ /home/john/.emacs.d/straight/build/org/) Ihor Radchenko
2024-01-30 13:48   ` Ihor Radchenko

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=CADywB5+P_42Xc27GQWfwMomdkCr9_+Q1N21C9AOfkc6X61R3ug@mail.gmail.com \
    --to=jmmathena@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).