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: Sat, 18 Sep 2021 10:27:41 +0200	[thread overview]
Message-ID: <CAP7OBxLh4evBdYUbM0HqJo4jNFUx25fj=JnrovzHc35dW7PbDQ@mail.gmail.com> (raw)

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

Hi,

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.

But it seems that there are multiple issues with multiple org commands and
inline tasks (visibility, navigation, selection).

For that reason I already suggested a while ago that the * END line would
be indented 1 level more then the * start of the inline task. By that it
would behave like a normal subtree for all org-commands.

Here a minimal example of an issue with visibility cycling:
>>>
* Example
** heading 1
xxxxx
** heading 2
*************** TODO Test access with provided credentials
xxxxx
*************** END
** heading 3
*************** TODO State "high value" targets
:@CB:
xxxxx
*************** END
** heading 4
xxxxx
<<<

Stating collapsed, pressing TAB on the heading 2 already shows the issue.

IMO the suggested simple (but breaking (but easy to fix)) design change
would make inline tasks more compatible and stable, and even more intuitive
in the expanded visualization.

Regards,
Michael

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

             reply	other threads:[~2021-09-18  8:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-18  8:27 Michael Dauer [this message]
2021-09-18  8:29 ` BUG Visibility Cycling with inline tasks 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
  -- 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='CAP7OBxLh4evBdYUbM0HqJo4jNFUx25fj=JnrovzHc35dW7PbDQ@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
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).