emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Dauer <mick.dauer@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org, Christian Hemminghaus <chrhemmi@gmail.com>,
	mail <mail@nicolasgoaziou.fr>
Subject: Re: Bug: Moving org-inline-tasks produces error message [9.3.6 (9.3.6-elpa @ /home/c.hemminghaus/.emacs.d/elpa/org-9.3.6/)]
Date: Sat, 15 May 2021 18:20:16 +0200	[thread overview]
Message-ID: <CAP7OBxJeCqdmdEMb+doFGO7x1aw1Y7hm9=0UKi_=6GyfJgBgqg@mail.gmail.com> (raw)
In-Reply-To: <87pmxsbc9q.fsf@gnu.org>

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

The main advantage is that all org-mode actions on subtrees would work
without any specific handling of inline tasks. e.g. visibility cycling,
hiding of none context, cut/copy, moving. With many of these actions I
experience some issues with inline tasks. And even from my personal user
perception I would like to have just the task headings on the same level,
not also the END marks.

Bastien <bzg@gnu.org> schrieb am Sa., 15. Mai 2021, 11:02:

> Hi Michael,
> Michael Dauer <mick.dauer@gmail.com> writes:
> > Wouldn't it be the much better approach to change inline tasks so
> > that the END line is one level below the "begin" line?
> I'm not sure how this would be better, and I would rather find this
> more confusing.  What is the expected benefit?
> --
>  Bastien

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

  reply	other threads:[~2021-05-15 16:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15  9:07 Bug: Moving org-inline-tasks produces error message [9.3.6 (9.3.6-elpa @ /home/c.hemminghaus/.emacs.d/elpa/org-9.3.6/)] Christian Hemminghaus
2020-09-05 10:42 ` Bastien
2020-09-07  6:45   ` Christian Hemminghaus
2021-05-13 13:06   ` Bastien
2021-05-14 18:08     ` Michael Dauer
2021-05-15  9:02       ` Bastien
2021-05-15 16:20         ` Michael Dauer [this message]
2021-05-15 11:06     ` Ihor Radchenko
2021-05-15 12:35       ` Bastien
2021-05-15 13:00         ` Ihor Radchenko
2021-05-15 13:06           ` Bastien

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:

  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='CAP7OBxJeCqdmdEMb+doFGO7x1aw1Y7hm9=0UKi_=6GyfJgBgqg@mail.gmail.com' \
    --to=mick.dauer@gmail.com \
    --cc=bzg@gnu.org \
    --cc=chrhemmi@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \


* 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


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