emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Michael Dauer <mick.dauer@gmail.com>
To: emacs-orgmode@gnu.org
Subject: BUG Visibility Cycling with inline tasks
Date: Sun, 26 Sep 2021 11:51:59 +0200	[thread overview]
Message-ID: <CAP7OBxJ+rKp=OTAtt6BFWMjviLNTrx9yYRjKrrbLt+Ubb8KD9A@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]

Hi,

I resend my report with now hopefully all information to reproduce it
quickly.

Inline tasks are a great feature of org-mode, very useful to include tasks
in all sorts of documents without interfering with the document structure.

0. emacs -Q
1. Insert the below snippet into scratch buffer.
>>>
* Example
** heading 1
xxxxx
** heading 2
*************** TODO Test access with provided credentials
xxxxx
*************** END
** heading 3
*************** TODO State "high value" targets
xxxxx
*************** END
** heading 4
xxxxx

(org-mode)
(require 'org-inlinetask)
<<<

2. Execute each of the 2 elisp statements at the bottom (C-x C-e)
3. Cycle Example to show children
4. Cycle heading 2

This should show the issue: Parts of heading 3 are expanded too. This is
also true for the next to cycling steps. Then comes a correct full cycle
and the issue repeats.

This garbage shown from the next heading(s) can become huge in more complex
structures.

Org mode version 9.4.6 (9.4.6-gcf30f7

Please confirm the issue.

Regards,
Michael

[-- Attachment #2: Type: text/html, Size: 1574 bytes --]

next             reply	other threads:[~2021-09-26  9:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-26  9:51 Michael Dauer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-09-18  8:27 BUG Visibility Cycling with inline tasks Michael Dauer
2021-09-18  8:29 ` Michael Dauer
2021-09-20  5:02 ` Ihor Radchenko
2021-09-20  7:17   ` Michael Dauer
2021-09-20  8:22     ` Ihor Radchenko
2021-09-21 18:52       ` Michael Dauer

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='CAP7OBxJ+rKp=OTAtt6BFWMjviLNTrx9yYRjKrrbLt+Ubb8KD9A@mail.gmail.com' \
    --to=mick.dauer@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

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).