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, mail <mail@nicolasgoaziou.fr>,
	Christian Hemminghaus <chrhemmi@gmail.com>
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: Fri, 14 May 2021 20:08:20 +0200	[thread overview]
Message-ID: <CAP7OBx+bSYNe5kdPTDja-Fic2Gn5T4H17F3KG7Td=NwZVn0Z+g@mail.gmail.com> (raw)
In-Reply-To: <877dk23hqn.fsf@gnu.org>

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


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 did not think it through. But IMO it would make IT more compatible with
normal org behavior, and also more visually appealing.

With the END notation it would still be unambiguous.

I'm aware that this change would have an impact on existing documents. But
worth a simple migration command the improvement would be worth the little


Am Do., 13. Mai 2021 um 15:08 Uhr schrieb Bastien <bzg@gnu.org>:

> Hi Christian,
> Bastien <bzg@gnu.org> writes:
> > Christian Hemminghaus <chrhemmi@gmail.com> writes:
> >
> >> I ran into an error message while composing structured text with
> >> org-mode using org-inline-tasks. The error appears when moving around
> >> inline tasks in my document.
> >
> > yes, I confirm this bug.
> Carsten proposed a patch that I adapted a little bit and pushed to the
> maint branch.  We now throw an error saying that dragging inline tasks
> is not supported.
> Thanks,
> --
>  Bastien
> --
> Confidentiality Notice:This email and any attachments it may contain are
> intended for the individual or entity above and may be confidential and
> protected by legal privilege. SmartPM Technologies, Inc. makes no
> warranties, express or implied, concerning the accuracy of the information
> contained herein, which is subject to change without notice. Unintended
> recipients should be aware that use of this e-mail or any of its
> attachments in any way is forbidden.

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

  reply	other threads:[~2021-05-14 18:28 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 [this message]
2021-05-15  9:02       ` Bastien
2021-05-15 16:20         ` Michael Dauer
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='CAP7OBx+bSYNe5kdPTDja-Fic2Gn5T4H17F3KG7Td=NwZVn0Z+g@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).