emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Dauer <mick.dauer@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: BUG Visibility Cycling with inline tasks
Date: Mon, 20 Sep 2021 09:17:40 +0200	[thread overview]
Message-ID: <CAP7OBxLn2KHK+szR7vqTte7yWxjqs=GxCDwB8fS2WZKuykCb5A@mail.gmail.com> (raw)
In-Reply-To: <87y27r6dqr.fsf@localhost>

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

What I get after the first org-cycle is:
* Example
** heading 1
** heading 2
*              ** TODO Test access with provided credentials
** heading 3
xxxxx
*              ** END
** heading 4
xxxxx

So it also shows part of the following heading. This "garbage" can be max
more if the following subtree is more complex.

it stays after the 2nd and 3rd cycle. Cycles 4 to 6 are OK, then the
problem comes again.

Am Mo., 20. Sept. 2021 um 07:01 Uhr schrieb Ihor Radchenko <
yantar92@gmail.com>:

> Michael Dauer <mick.dauer@gmail.com> writes:
>
> > Stating collapsed, pressing TAB on the heading 2 already shows the issue.
>
> Could you describe what is the issue you observe and how it differs from
> your expectations? I do not see any problem with visibility on my side.
>
> Best,
> Ihor
>

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

  reply	other threads:[~2021-09-20  7:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2021-09-20  8:22     ` Ihor Radchenko
2021-09-21 18:52       ` Michael Dauer
  -- strict thread matches above, loose matches on Subject: below --
2021-09-26  9:51 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='CAP7OBxLn2KHK+szR7vqTte7yWxjqs=GxCDwB8fS2WZKuykCb5A@mail.gmail.com' \
    --to=mick.dauer@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --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).